CE-2903: Stop IOCs from falling into restart loop
This switches to the latest deployment playbook which will change the mechamism used to restart IOCs so that procServ no longer handles restarts, but instead that systemd does. This will have several main impacts:
- Improved monitoring of IOC status
- Stop IOCs that restart indefinitely due to, e.g. missing dependencies
It will also change the behaviour of a user logged into conserver: previously,
if you were logged onto an IOC console via conserver, you could restart the
IOC by typing exit
; this would allow you to observe the IOC start in the same
console. Due to the change to systemd managing the restarts, this will no longer
work; the console that you are logged onto will be killed and you will need to
log on to a new console.
This information can still be obtained by (for example) watching the procServ log itself.