A startup problem was found on baobab-demo1.sanbi.ac.za and baobab-demo2.sanbi.ac.za. This was related to a problem caused by an Alias line having the same name as the unit name, as described in this stackoverflow question. Commenting out the Alias line allows systemctl enable supervisord.service to work and thus the LIMS to start on boot.
I could not find the source describing this systemd configuration, but here is a working config:
[Unit]
Description=Supervisor daemon
Documentation=http://supervisord.org
After=network.target
[Service]
ExecStart=/usr/local/bin/supervisord -n -c /etc/supervisor/supervisord.conf
ExecStop=/usr/local/bin/supervisorctl $OPTIONS shutdown
ExecReload=/usr/local/bin/supervisorctl $OPTIONS reload
KillMode=process
Restart=on-failure
RestartSec=42s
[Install]
WantedBy=multi-user.target
#Alias=supervisord.service
A startup problem was found on baobab-demo1.sanbi.ac.za and baobab-demo2.sanbi.ac.za. This was related to a problem caused by an
Aliasline having the same name as the unit name, as described in this stackoverflow question. Commenting out theAliasline allowssystemctl enable supervisord.serviceto work and thus the LIMS to start on boot.I could not find the source describing this systemd configuration, but here is a working config: