Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-1597

init script fails to start xrootd after crash

    Details

    • Type: Story
    • Status: To Do
    • Resolution: Unresolved
    • Fix Version/s: None
    • Component/s: Qserv
    • Labels:
      None

      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

            Activity

              People

              • Assignee:
                fritzm Fritz Mueller
                Reporter:
                salnikov Andy Salnikov
                Watchers:
                Andy Salnikov, Fritz Mueller, Wil O'Mullane
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:

                  Summary Panel