Scheduled firewall reboot broke keepalive service

A planned reboot of one of the science firewalls at 10:30 should normally have been unnoticable, however, after the firewall came back online, the keepalived service failed to start, which prevented the firewall’s virtual IP from being advertised. As a result, traffic to several internal services appeared to hang.

The issue was resolved by manually starting the keepalived daemon at 10:51.