Bug 983073

Summary:	dirsrv fails to start due to incorrect /var/run/lock lines in tmpfiles.d
Product:	[Fedora] Fedora	Reporter:	James Hogarth <james.hogarth>
Component:	389-ds-base	Assignee:	Rich Megginson <rmeggins>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	19	CC:	amessina, awilliam, edewata, mreynolds, nhosoi, nkinder, rmeggins
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-07-11 14:57:57 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description James Hogarth 2013-07-10 12:35:38 UTC

Description of problem:
The lock directory is now symlinked to /var/run which is on tmpfs. The tmpfiles.d configuration that dirsrv puts in place (see a similar bug #857939 but that was for /var/run/dirsrv and not /var/lock being moved to /var/run/lock) specifies the old location of /var/lock/dirsrv and /var/lock/dirsrv/slapd-EXAMPLE-COM but systemd-tmpfiles does not follow the symlink so the directory never gets created and has to be created by hand. 

Version-Release number of selected component (if applicable):
389-ds-base-1.3.1.3-1.fc19.x86_64

How reproducible:
Every time

Steps to Reproduce:
1. Clean install of F19
2. Install 389-ds (I used freeIPA to speed up the process and developing against freeIPA is where I bumped into this).
3. Observe dirsrv starts fine.
4. Reboot system
5. Observe dirsrv fails to start
6. Add lines to /etc/tmpfiles.d/dirsrv-EXAMPLE-COM.conf to create /var/run/lock/* instead of /var/lock/*
7. Reboot system
8. Observe right directories are created and dirsrv instance runs

Actual results:
dirsrv fails to start after a reboot

Expected results:
dirsrv starts with no manual intervention

Comment 1 Rich Megginson 2013-07-10 13:18:46 UTC

Upstream ticket:
https://fedorahosted.org/389/ticket/47429

Comment 2 Adam Williamson 2013-09-27 07:16:35 UTC

For the record, I am seeing this with a newly-deployed F19 freeipa server, happened to me at least five or six boots in a row, I never got a 'successful' boot. And 'ab' from #freeipa on freenode says he sees it on his deployment too.

Comment 3 Adam Williamson 2013-09-27 16:18:55 UTC


*** This bug has been marked as a duplicate of bug 996716 ***