On 30/11/15 17:27, Thomas Lamprecht wrote:
If you prefer to use journalctl execute `mkdir /var/log/journal` to
make those logs persistent, then you can browse the last boot with
journalctl -b-1
where -1 denotes the previous boot
I'll do that, thanks.
Can HA cause a host to reboot? I thought it was just around
restarting VM's
Yes it is around (re)starting VMs when there is a failure, but to
secure that the VM only runs once in the cluster (to avoid race
conditions/ multiple access to shared resources) we need fencing.
Proxmox VE 4 uses self fencing which restarts the node via the
watchdog if it lost quorum for more than 60 seconds AND a HA resource
is configured on this node to secure that all shared resources are
free for the rest of the cluster.
Ahhhhh ... that sounds a distinct possibility then, I'll remove all HA
resources for now and monitor the quorum via the logs. Didn't think I
had quorum issues, but best to be sure.
Thanks - Lindsay
_______________________________________________
pve-user mailing list
[email protected]
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
