Re: [389-users] Problem with ds setup

2012-01-04 Thread Rich Megginson
On 01/03/2012 10:52 PM, Israel Nelken wrote: I tried to install the directory server on a machine with a clean installation of Fedora 16, fully updated. the setup script failed at the state of starting the admin server. I fully removed the installation (remove-ds-admin.pl

Re: [389-users] Problem with ds setup

2012-01-05 Thread Guillaume Chanaud
Hi, same here, there is a segfault in http.worker. It's the mod_nss fault (like always..). So here is the solution to get it working : In /etc/dirsrv/admin-serv/httpd.conf Comment lines : LoadModule nss_module /usr/lib64/httpd/modules/libmodnss.so Include /etc/dirsrv/admin-serv/nss.co

Re: [389-users] Problem with ds setup

2012-01-05 Thread Rich Megginson
On 01/05/2012 04:49 AM, Israel Nelken wrote: tried the packages from the testing repos. Still doesn't work. The relevant lines from the log file: Starting admin server . . . output: Job failed. See system logs and 'systemctl status' for details. Could not start the admin server. Error: 256 Faile

Re: [389-users] Problem with ds setup

2012-01-05 Thread Rich Megginson
On 01/05/2012 10:57 AM, Guillaume Chanaud wrote: Hi, same here, there is a segfault in http.worker. It's the mod_nss fault (like always..). This has happened before? Are there any bugs opened for this issue? Is this SELinux related? So here is the solution to get it working : In /etc/dirsr

Re: [389-users] Problem with ds setup

2012-01-05 Thread Guillaume Chanaud
Le 05/01/2012 18:58, Rich Megginson a écrit : On 01/05/2012 10:57 AM, Guillaume Chanaud wrote: Hi, same here, there is a segfault in http.worker. It's the mod_nss fault (like always..). This has happened before? Are there any bugs opened for this issue? Is this SELinux related? No it's no

Re: [389-users] Problem with ds setup

2012-01-06 Thread Rich Megginson
On 01/06/2012 12:57 AM, Israel Nelken wrote: Update: Guillaume's suggestion to comment out the nss-related lines works - thanks! However, it seems that there is a bug? Yes. Sounds like a bug in mod_nss. I'm currently replacing a number of computers in my lab with new ones, and the issue com