Hello
I am seeing some warning in syslog :
Nov 12 10:05:41 node1 corosync[25795]: alert [TOTEM ] Invalid packet data
Nov 12 10:05:41 node1 corosync[25795]: [TOTEM ] Digest does not match
Nov 12 10:05:41 node1 corosync[25795]: [TOTEM ] Received message has invalid digest... ignoring.
Nov...
I've got 2 proxmox clusters - one with hammer ceph cluster (bigger) and second one working as a ceph client with dedicated pool (smaller). I wanted to first upgrade smaller cluster before bigger one with data. After upgrading two nodes of smaller cluster to proxmox 5.1 they are working properly...
Dear All,
I am trying to achive a network with two hosts installed with Proxmox 5.1 and they are in cluster.
The connection between them is direct cable and will be the same later. The connection from Host OS using the vlan ports is working
Participants:
Host A vmbr1 -...
Hi,
4 HA Vms were not able to reboot properly this morning at 4:30 pm (reboot via cron).
These vms are running Centos 7 64 bits with qemu-guest-agent (hosted by different nodes).
Seems that my 3 nodes cluster is up to date :
proxmox-ve: 5.1-25 (running kernel: 4.13.4-1-pve)
pve-manager...
Migrating from Proxmox 3.1 to 5.1.
Successfully migrated couple of Ubuntu containers already.
Now stuck with Centos (6.x) container - migration went ok, but after container start, no access via console or network.
Using debug, looks like it hangs at:
lxc-start 102 20171029185125.850 NOTICE...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.