Search results

This did the trick! Thank you so much. But this obviously is a bug that needs to be looked at. I'm 99% sure that somewhere in the web interface code that all that needs to be added are brackets [] around any and all ipv6 addresses Eg https://2001:470:abcd:ef::1/ becomes...

Any word on this? This isn't necessarily a major issue but it is rather annoying to have to have a browser tab open for each physical host.

Version information for both hosts: proxmox-ve: 4.1-39 (running kernel: 4.2.8-1-pve) pve-manager: 4.1-15 (running version: 4.1-15/8cd55b52) pve-kernel-4.2.6-1-pve: 4.2.6-36 pve-kernel-4.2.8-1-pve: 4.2.8-39 lvm2: 2.02.116-pve2 corosync-pve: 2.3.5-2 libqb0: 1.0-1 pve-cluster: 4.0-33 qemu-server...

I can also confirm this is happening to me with a freshly installed and updated proxmox ve 4.1 joined as a second node. Seems to be happening on both machines.

You mentioning the BIOS got me to thinking. It turns out there was a second watchdog being loaded! I'm not sure how or what it was, but these Dell Optiplex 755s have the Intel Active Managment BIOS extension. This apparently has a sort of hardware watchdog. As soon as I disabled Intel AMT...

No, these are three Dell optiplex 755s. They have no hardware watchdog to speak of is my understanding.

I am also having this issue with watchdog-mux. It's causing the pve-ha-crm service to fail.Oct 21 01:38:59 pinkie watchdog-mux[1744]: watchdog set timeout: Invalid argumentOct 21 01:38:59 pinkie systemd[1]: watchdog-mux.service: main process exited, code=exited, status=1/FAILUREOct 21 01:38:59...