Description of problem: auth2-master service doesn't finish start-up from systemctl 'start auth2-master.service' as the PID file is not constructed properly. The file /vice/auth2/pid is written, but auth2-master expects /vice/auth2/master.pid. If you 'mv pid master.pid' the start-up completes OK Version-Release number of selected component (if applicable): coda-server-6.9.5-11.fc20.x86_64 How reproducible: Enable and start auth2-master using original package files. Steps to Reproduce: 1. Enable auth2-master service with 'systemctl enable auth2-master.service' 2. Using original package file run "systemctl start auth2-master.service" 3. Actual results: 'systemctl status auth2-master.service' shows service starting, but hung due to /vice/auth2/master.pid not readable (yet?) after start. [root@server auth2]# systemctl status auth2-master.service auth2-master.service - Coda Master Authentication Server (SCM) Loaded: loaded (/usr/lib/systemd/system/auth2-master.service; enabled) Active: activating (start) since Sun 2014-03-09 18:33:03 GMT; 11s ago Process: 31772 ExecStart=/usr/sbin/auth2 (code=exited, status=0/SUCCESS) Main PID: 31399 (code=exited, status=0/SUCCESS) CGroup: /system.slice/auth2-master.service └─31773 auth2 Mar 09 18:33:03 server.wasielewski systemd[1]: PID file /vice/auth2/master.pid not readable (yet?) after start. Expected results: Normal startup with events logged to /vice/auth2/AuthLog [root@server auth2]# systemctl status auth2-master.service auth2-master.service - Coda Master Authentication Server (SCM) Loaded: loaded (/usr/lib/systemd/system/auth2-master.service; enabled) Active: active (running) since Sun 2014-03-09 18:36:06 GMT; 1s ago Process: 31787 ExecStart=/usr/sbin/auth2 (code=exited, status=0/SUCCESS) Main PID: 31788 (auth2) CGroup: /system.slice/auth2-master.service └─31788 auth2 Mar 09 18:36:02 server.wasielewski systemd[1]: PID file /vice/auth2/master.pid not readable (yet?) after start. Mar 09 18:36:06 server.wasielewski systemd[1]: Started Coda Master Authentication Server (SCM). Additional info: 1) The 'pid' file contains the correct PID; it is just the filename that causes the problem. 2) If I bypass systemd and start auth2 directly using '/usr/sbin/auth2 &' the same /vice/auth2/pid file is created, but auth2 runs OK in the background. 3) No SELinux messages. 4) I haven't tested auth2-slave service, but presume it will have the same issue.
yes, it appears that auth2-slave will have the same problem, but we can fix them at the same time by changing the service files. The only caveat is that auth2-master and auth2-slave can't run on the same physical system (which is the case regardless of what the pid file is named).
coda-6.9.5-1i3.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/coda-6.9.5-1i3.fc20
Package coda-6.9.5-1i3.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing coda-6.9.5-1i3.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-3777/coda-6.9.5-1i3.fc20 then log in and leave karma (feedback).
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.