Details
-
Type:
Story
-
Status: Invalid
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: Qserv
-
Labels:None
-
Story Points:1
-
Epic Link:
-
Team:Data Access and Database
Description
I think we saw this issue in the past, not sure it was actually fixed back then or just was to reintroduced one more time.
After crash of xrootd the regular etc/init.d/xrootd start fails to start it:
[salnikov@lsst-dbdev2 dm-621]$ ~/qserv-run/dm-621/etc/init.d/xrootd status
|
xrootd is dead but PID file exists [FAILED]
|
see /usr/local/home/salnikov/qserv-run/dm-621/var/run/worker/xrootd.pid
|
[salnikov@lsst-dbdev2 dm-621]$ ~/qserv-run/dm-621/etc/init.d/xrootd start
|
Starting xrootd: (already up) [ OK ]
|
[salnikov@lsst-dbdev2 dm-621]$ ~/qserv-run/dm-621/etc/init.d/xrootd status
|
xrootd is dead but PID file exists [FAILED]
|
see /usr/local/home/salnikov/qserv-run/dm-621/var/run/worker/xrootd.pid
|
I can start it with restart but I think that start should detect that xrootd is dead (status does that) and start service correctly.
This issue may exist for other services but I did not check.
Attachments
Issue Links
- mentioned in
-
Page Loading...
Activity
This is still a valid issue, but is a very low impact bug with low priority to fix.
obsolete since init.d scripts retired in "lite"
Fabrice Jammes Fritz Mueller Andy Salnikov is this still valid ? I assume its superceeded and should be closed.