> >crit: get_timet_now: Defaulting to 'now'
> > What does this message mean?
>
> It means some idiot (me) forgot to downgrade a debug message before
> committing.
> You can safely ignore it.
critical important debug message ignored. Thanks for owning up to it.
> Were there any other issues
On 19/04/2013, at 11:02 AM, Daniel Black wrote:
> Hi,
>
> I had an incident this morning (16:22) where each node lost corosync
> connection to the cluster and when offline in minute intervals. Once quorum
> was lot each server disabled its managed IPs. Servers were rebooted around
> 17:52:23
Found the same VPSs were loosing network connections due to xen kernel things.
Response could of been as programmed. The last shutdown of all IP resources
once there was no DC looked scary. I'll re-read the docs to see what can be
done here.
Sorry for wrongly attributing corosync/pacemaker.
-
Hi,
I had an incident this morning (16:22) where each node lost corosync connection
to the cluster and when offline in minute intervals. Once quorum was lot each
server disabled its managed IPs. Servers were rebooted around 17:52:23.
Its a fairly simple resource of 5 IPv4 address and 5 IPv6 add
