The person responsible for sheep-dogging the switch reboots this morning arrived to find that the cluster was already down. It wasn't a split-brain down, no servers were at that special screen. The cluster was just... down. By the time we got the chance to look at the cluster event-log, the events detailing why this special circumstance occured had scrolled off the back of the log.
That log needs to be longer. This isn't the first time I've had key data fall off the back of the log this way. So far I haven't found a way to extend it.
In other news, everything else went fine.
That log needs to be longer. This isn't the first time I've had key data fall off the back of the log this way. So far I haven't found a way to extend it.
In other news, everything else went fine.