Open pierluca opened 3 months ago
Good scripts , to be included in ansible-config
[Path]
PathModified=/home/popdemo/dev/be1-go/pop
[Install]
WantedBy=multi-user.target
[Unit]
Description=pop-dev-be1-go-a restarter
After=network.target
[Service]
Type=oneshot
ExecStart=/usr/bin/systemctl restart pop-dev-be1-go-a.service
[Install]
WantedBy=multi-user.target
$ systemctl enable pop*restart.{path,service}
$ systemctl start pop*restart.{path,service}
Description (Actual behavior)
When a new release is made, the PoP backend software wasn't restarted. (a temporary fix is now in place for dev-be{1,2}-{a,b}.personhood.online)
Expected behavior
When a new release is made, the PoP backends should be restarted automatically with the new version.
How to reproduce
systemctl status pop-dev-be1-go.service
Version & Environment
This bug was reproduced on May 15, 2024 (github.com/dedis/ansible-config is the relevant repo)
Front-ends:
Back-ends:
Workaround
systemctl restart
of each service - not a valid option.Possible root cause
Most likely, since the Debian Bullseye update, the previous service descriptions don't work anymore.