Maybe something interesting, the only survived node was node7, and it was the
crm master
I'm also seein crm disabling watchdog, and also some "loop take too long"
messages
(some migration logs from node2 to node1 before the maintenance)
Sep 3 10:36:29 m6kvm7 pve-ha-crm[16196]: service 'vm:99
> Sep 3 10:40:51 m6kvm7 pve-ha-lrm[16140]: loop take too long (87 seconds)
> Sep 3 10:40:51 m6kvm7 pve-ha-crm[16196]: loop take too long (92 seconds)
Indeed, this should not happen. Do you use a spearate network for corosync? Or
was there high traffic on the network? What kind of maintenance was
> On 09/06/2020 2:14 PM dietmar wrote:
>
>
> > Sep 3 10:40:51 m6kvm7 pve-ha-lrm[16140]: loop take too long (87 seconds)
> > Sep 3 10:40:51 m6kvm7 pve-ha-crm[16196]: loop take too long (92 seconds)
>
> Indeed, this should not happen. Do you use a spearate network for corosync? Or
> was there
Hi,
I know that Proxmox has it's own inbuilt InfluxDB client:
https://pve.proxmox.com/wiki/External_Metric_Server
However, Telegraf recently added first-party support for Proxmox:
https://github.com/influxdata/telegraf/tree/master/plugins/inputs/proxmox
Telegraf lets you output to InfluxDB, Gr
Hi,
On 07.09.20 03:42, Victor Hooi wrote:
> I know that Proxmox has it's own inbuilt InfluxDB client:
>
> https://pve.proxmox.com/wiki/External_Metric_Server
>
> However, Telegraf recently added first-party support for Proxmox:
>
> https://github.com/influxdata/telegraf/tree/master/plugins/inpu
