- Used Zammad version: 2.9
- Used Zammad installation source: from source
- Operating system: Debian 9 / Apache 2.4.25 / MySQL version 10.1.37 / Webmin 1.9 / Virtualmin 6.06-2
- Browser + version: Any browser
Expected behavior:
- Continue running after closing terminal window.
Actual behavior:
- Puma stops running after closing terminal window, causing Zammag to be unavailable and 503 error.
Steps to reproduce the behavior:
- Followed installation guide from sources, installed environnement with virtualhost user, deployed latest, configure and start Zammad manually with command given in documentation :
rails s -p 3000 # application web server script/websocket-server.rb start # non blocking websocket server script/scheduler.rb start # generate overviews on demand, just send changed data to browser
Then :
cd scripts/systemd sudo ./install-zammad-systemd-services.sh
But after reboot, 503 error until starting Zammag manually. If I close terminal window, it stops Zammad.