On 12/14/2010 11:15 AM, brandon wrote: > On 12/14/2010 11:00 AM, Rich Megginson wrote: >> On 12/14/2010 10:58 AM, brandon wrote: >>> Okay, I have 389-admin-console-1.1.5-1 installed on RHEL5 with >>> httpd-2.2.3-43.el5_5.3 and SELinux enforcing. >> What are the other package versions you have e.g. >> rpm -qi 389-ds-base 389-admin 389-adminutil >> ? > 389-admin-console-1.1.5-1 > 389-ds-base-1.2.6.1-2 > 389-ds-1.2.1-1 > 389-adminutil-1.1.8-4 > 389-console-1.1.4-1 > 389-dsgw-1.1.5-1 > 389-admin-1.1.11-1 > 389-ds-console-1.2.3-1 I believe the problem is due to some selinux policy fixes made to more recent versions of 389. Try upgrading to the latest 389-ds-base-1.2.7 and 389-admin-1.1.13 (you will also have to upgrade 389-adminutil and 389-dsgw and idm-console-framework). >> Does it work if you disable SELinux? > I'm a step ahead. I switched it to permissive and rebooted. It came up > okay. > > About the only thing pertinent in sealerts is a File Label alert with a > target object of ./httpd.pid. There are other sealerts, but those are > known problems (we run rootsh shell wrapper and it causes a cascating > sealert but nothing that breaks anything). > > I'm rebooting back to enforcing mode to see if it still works. > > BTW, the http error (not very helpful): > > [Tue Dec 14 17:52:44 2010] [notice] Access Host filter is: *.infra > [Tue Dec 14 17:52:44 2010] [notice] Access Address filter is: * > [Tue Dec 14 17:52:45 2010] [notice] child pid 5706 exit signal > Segmentation fault (11) > > > It just loops/repeats this about once a second. > -- > 389 users mailing list > 389-users at lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/389-users
