Bug 480502 – sys-auth/keystone - start-stop-daemon: fopen `/var/run/keystone/keystone.pid': No such file or directory

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description Davide Rebeccani 2013-08-10 14:51:03 UTC]

sys-auth/keystone-2013.1.2.r2 and sys-auth/keystone-2013.1.9999 can't start because of missing /var/run/keystone directory to hold pid file

Reproducible: Always

Steps to Reproduce:
1.emerge =sys-auth/keystone-2013.1.2.r2 or 1.emerge =sys-auth/keystone-2013.1.9999
2./etc/init.d/keystone
3.
Actual Results:  
start-stop-daemon: fopen `/var/run/keystone/keystone.pid': No such file or directory

Expected Results:  
keystone is present as a running process into the process table os the system

[Comment 1 Davide Rebeccani 2013-08-10 14:58:41 UTC]

Created attachment 355622 [details]
keystone.initd

In attachment there is a modified keystone init file that check for the existence of /var/run/keystone directory before invoking start-stop daemon.
If the directory is missing it creates it and the start keystone, else it only starts the daemon.

[Comment 2 Jeroen Roovers (RETIRED) 2013-08-11 13:37:21 UTC]

Comment on attachment 355622 [details]
keystone.initd

--- files/keystone.initd        2012-12-09 22:57:11.000000000 +0100
+++ -   2013-08-11 15:37:12.599626245 +0200
@@ -30,7 +30,9 @@
        . /etc/conf.d/$BASENAME
        
        ebegin "Starting ${SVCNAME}"
-       
+       if [ ! -d ${PID_PATH} ]; then   
+               mkdir ${PID_PATH}       
+       fi
        start-stop-daemon --start --quiet --make-pidfile --pidfile "${PID_PATH}/${SVCNAME}.pid" \
                                          --exec /usr/bin/${SVCNAME}-all --background -- --config-file=${CONFIG_FILE}

[Comment 3 Matthew Thode ( prometheanfire ) 2013-08-13 16:36:28 UTC]

fixed in tree (in place, so remerge your stuff if you are having issues after you get the update)