503 Service Unavailable - zammad-web-1.service: Failed with result 'exit-code'

Infos:

  • Used Zammad version: 5.2
  • Used Zammad installation type: source
  • Operating system: ubuntu server 20.04
  • Browser + version: chrome

I’ve been greeted by a 503 - Service Unavailable today when I try to use zammad.
Checking my syslog, I see

Jan 25 07:59:26 zammad zammad-web-1.service[14051]: => Booting Puma
Jan 25 07:59:26 zammad zammad-web-1.service[14051]: => Rails 6.1.7.1 application starting in production
Jan 25 07:59:26 zammad zammad-web-1.service[14051]: => Run `bin/rails server --help` for more startup options
Jan 25 07:59:26 zammad zammad-web-1.service[14051]: A server is already running. Check /opt/zammad/tmp/pids/server.pid.
Jan 25 07:59:26 zammad zammad-web-1.service[14051]: Exiting
Jan 25 07:59:26 zammad systemd[1]: zammad-web-1.service: Main process exited, code=exited, status=1/FAILURE
Jan 25 07:59:26 zammad systemd[1]: zammad-web-1.service: Failed with result 'exit-code'.
Jan 25 07:59:27 zammad systemd[1]: zammad-web-1.service: Scheduled restart job, restart counter is at 306.

How would I go about troubleshooting this issue?

Reading the output of:

/opt/zammad/tmp/pids/server.pid

gives me 699.
If I kill the process with:

kill -9 699

I can restart zammad and everything starts working again.

The problem will intermittently reappear after a few reboots. How do I figure out which process 699 is?

I am sure there are more elegant ways, but I usually use “top” and then the “L”-command to locate a process (not only by ID). More information about a command that launched a process can be toggled via “c” within “top”, to show the exact command-line parameters for that process.

i found the info by using:

ps aux
zammad       699  0.2  4.3 480912 354580 ?       Ssl  09:02   0:50 puma 4.3.12 (tcp://127.0.0.1:3000) [zammad]

I guess it’s the same info as the error I original posted.

This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.