Initial start up of zammad-railsserver takes longer than systemd wants to wait #18

New issue

Open

opened 2026-01-30 12:02:40 +00:00 by irl · 1 comment

irl commented

2026-01-30 12:02:40 +00:00

Owner

fatal: [redacted]: FAILED! => {"changed": false, "msg": "Unable to start service zammad-railsserver.service: Job for zammad-railsserver.service failed because a timeout was exceeded.\nSee \"systemctl --user status zammad-railsserver.service\" and \"journalctl --user -xeu zammad-railsserver.service\" for details.\n"}

``` fatal: [redacted]: FAILED! => {"changed": false, "msg": "Unable to start service zammad-railsserver.service: Job for zammad-railsserver.service failed because a timeout was exceeded.\nSee \"systemctl --user status zammad-railsserver.service\" and \"journalctl --user -xeu zammad-railsserver.service\" for details.\n"} ```

irl added the

bug

label 2026-01-30 12:02:40 +00:00

irl commented

2026-01-30 12:04:44 +00:00

Author

Owner

There's the pull of the image, and then I think it might be waiting for zammad-init to complete before systemd reports the service ready, which would be nice because it's not ready until then but bad because timeout.

There's the pull of the image, and then I think it **might** be waiting for zammad-init to complete before systemd reports the service ready, which would be nice because it's not ready until then but bad because timeout.