Search results

This one may be a hack but when I was proving this out I set up an iptables rule to increase the TTL for corosync communication which in my case was multicast but I was also able to prove it out by increasing the TTL on unicast as well. You could also try playing with sending traffic on...

Hello Shim, I investigated the issue and isolated it to a possible bug within corosync itself. The root cause in my case was identified by using a combination of strace and tcpdump to find out exactly what was causing the issue. The issue was a bit of a pita to isolate and eventually led us...

Hello Dietmar, I accidentally included the old cluster.conf and correct one only has 3 members. I wasn't sure if the messages from corosync were normal or not, but your comment leads me to believe this isn't normal behavior. It's unclear to me why they would join/leave the cluster, but this...

Hello All, We've been using proxmox in standalone mode for awhile and recently moved to the clustered setup per various guides on website. The setup went without any problems and unified management looks good. The problem we started having after setup were due to OOM and OOM-killer randomly...

We've been running proxmox non-clustered for awhile and clustering up a number of machines and clustering went fairly smoothly until we started noticing a number of OOM and oom-killer taking down host systems. After some digging we've isolated the issue to corosync running a system completely...