The init.d script for the glideinwms frontend occasionally fails when restart or start is run because the glideinwms frontend is still running. The shutdown of the gwms fe takes some time but the init.d script returns fairly quickly so on occasion when doing a restart or running the service with start soon after running stop, the startup fails with a process already running error:
Traceback (most recent call last):
File "/usr/sbin/glideinFrontend", line 334, in ?
File "/usr/sbin/glideinFrontend", line 309, in main
File "/usr/lib/python2.4/site-packages/glideinwms/lib/pidSupport.py", line 73, in register
raise AlreadyRunning, "Another process already running"
glideinwms.lib.pidSupport.AlreadyRunning: Another process already running
As a fix, I'd suggest putting a sleep 10 or something similar in the stop function so that the glideinwms processes have time to shutdown.
Sure, I can let you know by tomorrow.
Whenever you get the chance. This is certainly lower priority than any acceptance testing that you have.
, you were going to look at this ticket in late 2014… Could you do so soon?
Looks like this is fixed, there are checks in the stop function and running stop appears to wait properly until the frontend is stopped. I couldn't trigger this.