From: Aaron Lauterer <a.lauterer@proxmox.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] HA VMs - and timeout
Date: Fri, 4 Dec 2020 08:56:05 +0100 [thread overview]
Message-ID: <54788183-7b87-e65a-a97a-8a607e1161e8@proxmox.com> (raw)
In-Reply-To: <mailman.123.1607016026.440.pve-user@lists.proxmox.com>
On 12/3/20 6:20 PM, Alejandro Bonilla via pve-user wrote:
> Hello -
>
> I’ve just implemented an HA Group and then added my VMs as resources to be managed across my 3-node group. After struggling with ha-manager to disable/enable and unlocking VMs due to stuck migrations at first, I feel I can clear the usual issues as VMs get stuck.
>
> My question comes from the fact that I use Proxmox for my Lab, therefore I script a few things and start my servers in the morning but the HA VMs always come up in an error state - likely due to Ceph or the cluster not being fully ready. I have implemented a delay start of 60 seconds which used to be enough. Is this delay also respected when the HA resources/VMs are managed by HA?
You mean the delay when you configure the guests to boot when the host is starting? I haven't tested it explicitly but HA should not take that delay into account.
>
> Which log can I see to identify why these VMs never started and errored?
In the task log you should see the start jobs for each VM and if there is a problem starting it, those would be the first place to look. Otherwise the syslog.
>
> A separate question - is there an easier way to test/simulate a dead/node failure besides actually killing my hosts?
Take down/disconnect the interface over which corosync communicates. The isolated node will fence itself after it lost connection to the quorum part of the cluster.
>
> Thanks
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
parent reply other threads:[~2020-12-04 7:56 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <mailman.123.1607016026.440.pve-user@lists.proxmox.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54788183-7b87-e65a-a97a-8a607e1161e8@proxmox.com \
--to=a.lauterer@proxmox.com \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal