Zammad-web-1.service not starting any more after VM had crashed [SOLVED]

Technical assistance
1

Infos:

  • Used Zammad version: zammad-3.6.0-1606831527.a34a42ba.centos7.x86_64
  • Used Zammad installation source: YUM from repository
  • Operating system: CentOS 7.9.2009
  • Browser + version: Firefox 78.6.0esr

Problem Description:

The hypervisor where the VM with Zammad was running had crashed over the weekend. After a reboot and after restarting the VM, zammad-web-1.service is not startung up any more. In /var/log/messages I see the following message loop:

Jan  4 13:12:39 odcf-vm118 systemd: Started zammad-web-1.service.
Jan  4 13:12:41 odcf-vm118 zammad-web-1.service: A server is already running. Check /opt/zammad/tmp/pids/server.pid.
Jan  4 13:12:41 odcf-vm118 zammad-web-1.service: => Booting Puma
Jan  4 13:12:41 odcf-vm118 zammad-web-1.service: => Rails 5.2.4.4 application starting in production
Jan  4 13:12:41 odcf-vm118 zammad-web-1.service: => Run `rails server -h` for more startup options
Jan  4 13:12:41 odcf-vm118 zammad-web-1.service: Exiting
Jan  4 13:12:41 odcf-vm118 systemd: zammad-web-1.service: main process exited, code=exited, status=1/FAILURE
Jan  4 13:12:41 odcf-vm118 systemd: Unit zammad-web-1.service entered failed state.
Jan  4 13:12:41 odcf-vm118 systemd: zammad-web-1.service failed.
Jan  4 13:12:42 odcf-vm118 systemd: zammad-web-1.service holdoff time over, scheduling restart.
Jan  4 13:12:42 odcf-vm118 systemd: Stopped zammad-web-1.service.

systemctl also falsely reports all ok for zammad-web-1.service:

$ systemctl status zammad-web-1.service
● zammad-web-1.service
   Loaded: loaded (/etc/systemd/system/zammad-web-1.service; enabled; vendor preset: disabled)
   Active: active (running) since Mon 2021-01-04 13:15:20 CET; 3ms ago
 Main PID: 16157 (zammad)
   CGroup: /system.slice/zammad-web-1.service
           ├─16157 /bin/bash /usr/bin/zammad run web
           └─16159 /bin/bash /usr/bin/zammad run web

Jan 04 13:15:20 odcf-vm118 systemd[1]: Started zammad-web-1.service.
$

There is no problem with full filesystems, other services (MariaDB, Elasticsearch, nginx proxy) are working fine and the Zammad core seems to be working, too. I can see in /car/log/zammad/production.log that it fetches the support mailbox successfully.

Any idea on how to further debug (or fix) this problem? We are currently cut out from Zammad :frowning:. I’m happy with the commandline but I don’t have any working experience with ruby.

2

Problem solved by systemctl stop zammad; systemctl start zammad instead of the previous systemctl restart zammad-web and systemctl restart zammad-web-1. The fix holds through reboots.

1 Like
3

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