StoRM Backend service enters failed state when stopped

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major
    • 1.11.21
    • Affects Version/s: 1.11.20
    • Component/s: backend
    • Security Level: Public (Visbile by non-authn users.)
    • None

      Starting the backend service works fine but when stopping, the service remains in a failed state:

      Apr 16 16:06:07 omii005-vm03.cnaf.infn.it systemd[1]: storm-backend-server.service: main process exited, code=exited, status=143/n/a
Apr 16 16:06:07 omii005-vm03.cnaf.infn.it systemd[1]: Stopped StoRM Backend service.
Apr 16 16:06:07 omii005-vm03.cnaf.infn.it systemd[1]: Unit storm-backend-server.service entered failed state.
Apr 16 16:06:07 omii005-vm03.cnaf.infn.it systemd[1]: storm-backend-server.service failed.
Apr 16 16:06:07 omii005-vm03.cnaf.infn.it systemd[1]: Started StoRM Backend service.

      Exit code 143 means that the program received a SIGTERM signal to instruct it to exit. The JVM catches the signal, does a clean shutdown, i.e. it runs all registered shutdown hooks (there's one for StoRM Backend which stops several threads and services), but still exits with an exit code of 143. That's just how Java works.

      We should be able to suppress this by adding the exit code into the unit file as a "success" exit status:

      [Service]
SuccessExitStatus=143

            Assignee:
            Enrico Vianello
            Reporter:
            Enrico Vianello
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: