[Freeipa-users] heads up on dirsrv failure to start on fedora19

James Hogarth james.hogarth at gmail.com
Wed Jul 10 12:40:16 UTC 2013


Hi all,

A heads up in case someone else bumps into this when doing any
389-ds/freeipa work on F19.

The /etc/tmpfiles.d/dirsrv-EXAMPLE-COM.conf file is configured to create
the lockfiles in /var/lock/dirsrv/slapd-EXAMPLE-COM but on F19 /var/lock is
a symlink to /var/run/lock...

As a result after a reboot the directory does not exist and dirsrv fails to
start.

Appending (or amending) the lines to read /var/run/lock instead of
/var/lock (ie manually dereference the symlink in the conf file) allows
dirsrv to start after a reboot.

I've opened https://bugzilla.redhat.com/show_bug.cgi?id=983073 for this to
get it amended... but at least it's a simple workaround to 'fix' for now.

Cheers,

James
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/freeipa-users/attachments/20130710/47adca1f/attachment.htm>


More information about the Freeipa-users mailing list