← Back to team overview

ubuntu-389-directory-server team mailing list archive

Re: Problems installing 389 on Precise


On 25.02.2012 19:51, Justin Chudgar wrote:
> At Timo's suggestion, I upgraded my experimental server to Precise.
> (Amazingly smooth upgrade, BTW. :) I've had several issues with 389:
> First is a problem with the "user: nobody\ngroup:nobody" line in
> /etc/dirsrv/admin-serv/console.conf. This causes apache2 to complain
> about "apache2: bad group name nobody". Commenting out those lines in
> console.conf fixes that issue, though what problems it may cause besides
> limiting security I don't know.

Probably an issue due to upgrading from an earlier set of packages. The
default user/group is dirsrv/dirsrv and that's what my console.conf has..

> Second is a missing log file. Specifically this is what I see:
>     Starting dirsrv-admin:
>     (2)No such file or directory: apache2: could not open error log file
> /var/log/dirsrv/admin-serv/error.
>     Unable to open logs
>     Server failed to start !!! Please check errors log for problems
>     /etc/init.d/dirsrv-admin: 126: /etc/init.d/dirsrv-admin: failure:
> not found
> Manually creating /var/log/dirsrv/admin-serv and chowning it to dirsrv
> seems to fix that.

Hmm, couldn't reproduce that either.

> Third, and critically, is a segfault.
>     Starting dirsrv-admin:
>     Segmentation fault (core dumped)
>     Server failed to start !!! Please check errors log for problems
>     /etc/init.d/dirsrv-admin: 126: /etc/init.d/dirsrv-admin: failure:
> not found
>     ---
>     # following from /var/log/dirsrv/admin-serv/error
>     [Sat Feb 25 09:19:28 2012] [crit] do_admserv_post_config(): unable
> to create AdmldapInfo
>     Configuration Failed
>     ---
>     # from /var/log/syslog
>     kernel: [ 3378.642501] apache2[4319]: segfault at 10 ip
> 00007f255d1e9e84 sp 00007fff73edf310 error 4 in
> libpthread-2.15.so[7f255d1e0000+18000]

Yeah, I've pushed a new nss with a patch from Fedora to the ppa. Make
sure you get libnss3 3.13.1-1ubuntu5.1 and try again. I've reproduced
the crash here, but haven't actually tried the patch yet, waiting for it
to build.


Follow ups