possibe selinux issue on 1.2.6

[Smlacc1]

Hi There,

I just installed 1.2.6 from the epel repository onto a freshly
installed and updated RHEL 5.5.

When I use "service dirsrv-admin start", it starts, but then refuses
to receive connections.  the /var/log/dirsrv/admin-serv/error log
shows the process in an endless segfault/startup loop.

If i stop the service and then run "start-ds-admin", it works fine -
no segfaults and I can log into the 389-console fine.

I also tried disabling selinux, and when I do that, i can then run
"service dirsrv-admin start" and it comes up fine.  So the issue seems
linked to selinux and the init startup script.  I can use the
start-ds-admin to get it going, but if the server ever reboots it int
going to come back up properly.

Selinux is on enforcing targeted if that helps.

Thanks,
Smlacc.

[Nathan Kinder]

On 09/22/2010 05:48 AM, smlacc1 leador wrote:
> Hi There,
>
> I just installed 1.2.6 from the epel repository onto a freshly
> installed and updated RHEL 5.5.
>
> When I use "service dirsrv-admin start", it starts, but then refuses
> to receive connections.  the /var/log/dirsrv/admin-serv/error log
> shows the process in an endless segfault/startup loop.

We need to see the AVC messages from /var/log/audit/audit when this occurs.

-NGK
> If i stop the service and then run "start-ds-admin", it works fine -
> no segfaults and I can log into the 389-console fine.
>
> I also tried disabling selinux, and when I do that, i can then run
> "service dirsrv-admin start" and it comes up fine.  So the issue seems
> linked to selinux and the init startup script.  I can use the
> start-ds-admin to get it going, but if the server ever reboots it int
> going to come back up properly.
>
> Selinux is on enforcing targeted if that helps.
>
> Thanks,
> Smlacc.
> --
> 389 users mailing list
> [e-mail]
> https://admin.fedoraproject.org/mailman/listinfo/389-users