Red Hat Bugzilla – Bug 855990
stickshift-proxy is failed after reload on Fedora 17 and later
Last modified: 2015-05-14 18:59:18 EDT
Description of problem:
After updating the proxy configuration, a service reload on stickshift-proxy causes the service to show as failed and systemd to terminate the haproxy daemon.
The underlying issue is that systemd is confused by the daemon changing PIDs on reload.
Version-Release number of selected component (if applicable):
Fedora 17 and later.
Always on affected Fedoras
Steps to Reproduce:
1. systemctl status stickshift-proxy.service
2. systemctl reload stickshift-proxy.service
3. systemctl status stickshift-proxy.service
Service shows up as failed and is terminated
Service properly reloads and is not terminated.
See Bug 721375 ; A similar issue was discovered with sshd and the resolution was to treat sshd as a "simple" service that does not fork into the background.
The PID file is no longer updated when haproxy is not run in daemon mode. Our procedures assuming it should change appropriately.
The following pull request creates a wrapper script for LSB compliance.
Pull request accepted.