Networking Issues – Server Node/Master Synchronization& Authentication Failure(s) – E

[Server.Experts]

Networking Issues – Server Node/Master Synchronization& Authentication Failure(s) – ERROR 500...

Additionally it has been found that the host network fails intermittently, as well as well as NODE to MASTER and MASTER to NODE authentication / synchronization fails
# screenshot 1 shows the nodes, error codes and cluster uptime, issue #1
# screenshot 2 shows the nodes, error codes and cluster uptime, issue #2

Additionally, several different test setups were tried and similar problem was recreated

All nodes/servers running latest Proxmox VE distribution" proxmox-ve_1.5-4627-3.iso"

 

[Server.Experts]

Re: Networking Issues – Server Node/Master Synchronization& Authentication Failure(s)

Networking Issues – Server Node/Master Synchronization& Authentication Failure(s) – ERROR 500...

Additionally it has been found that the host network fails intermittently, as well as well as NODE to MASTER and MASTER to NODE authentication / synchronization fails
# screenshot 1 shows the nodes, error codes and cluster uptime, issue #1
# screenshot 2 shows the nodes, error codes and cluster uptime, issue #2

Additionally, several different test setups were tried and similar problem was recreated

All nodes/servers running latest Proxmox VE distribution" proxmox-ve_1.5-4627-3.iso"

Please see attachments

 

[Server.Experts]

Re: Networking Issues – Server Node/Master Synchronization& Authentication Failure(s)

Please see attachments

It has also been noted that within this state (i.e. non-synchronized & non-authorized)
# (OpenVZ containers) can be MIGRATED between MASTER to NODE, but remain un-operatable, and can be transferred back
# Although containers can be migrated between Node to Node, it becomes a one way operation, they become unrecoverable and inaccessible after migration

#video exist to show this issue, but due to size restricted to upload it…

 

[Server.Experts]

Re: Networking Issues – Server Node/Master Synchronization& Authentication Failure(s)

Please check if you have duplicate IP or MAC addresses somewhere.

If notheing helps, maybe you can test with another NIC. Also check your network equipement (switch).

Dietmar you are SuperStar!!! Please remind me to buy you a bear !!!

for everyone else who experiences similar issue...
• for mass duplication and deployment of OpenVZ containers
• please ensure your script contains necessary parameters for incrementally omitting/changing MAC address(es) inside containers ( applicable to bridged [VETH]connections)
• it can also be done manually but would be tedious for larger deployment
• if the above instructions are not practiced/implemented, you are likely to experience networking issues later on, which may include random connection issues, disconnections, packet transmission failures etc
• additionally system clocks need to be accurately and precisely set in all the clusters, even down to correct time-zones, I believe, this is to prevent sync failures/timeouts


Thank You to all the developers, contributorsand sponsorsof this project, we sincerely appreciate your efforts, hard-work and continued support


Additionally, Dietmar could you update us on the integration status of LXC into the new version of ProxMox and how we can assist. As you might be aware the OpenVZ developers have indicated it is likely to supersede their project, due to it being part of the mainline kernel.