Search results

bradmc, I bet that cisco is the issue...it's my exact problem....if you can, do the test I did....connect the servers to an unmanaged switch, or try other switch...I think it could be something related to broadcast storm control or some other feature of the cisco....I'll continue studing the...

I did a fresh install from the proxmox 3.3 ISO...the network card is detected automatically Update: connecting the IBM chassis SCM to an unmanaged switch (old 10/100 dlink) solves the problem, so the problem lies in the cisco 3750...i'll keep looking monday. Thanks, Javier

I had the exact same problem...3 nodes clustered in version 3.2...upgraded to 3.3 and the cluster failed after 5 minutes or so. Since the servers are (still) not in production, I've reinstalled the three of them with version 3.3....result: exact same behavior (5 minutes with the cluster ok, then...

dietmar, thank you very much for your help....we've found the culprit...it was a previous node that was removed (proxmox2-2) and wasn't turned off

I really whipped...fresh debian install, repartitioned and reinstalled with new IP.

Very sorry for the duplicate posts....wasn't reading the message after posting

The /etc/pve/nodes directory, in the 3 nodes of the cluster, contains the same: root@proxmox2-0:/etc/pve/nodes# ls -lh total 0 drwxr-x--- 2 root www-data 0 oct 9 2012 proxmox2-0 drwxr-x--- 2 root www-data 0 oct 9 2012 proxmox2-1 drwxr-x--- 2 root www-data 0 oct 9 2012 proxmox2-3...

Hello, We have 3 servers in cluster. We had a problem adding a 4th server (it stayed in the "Waiting for quorum" status)...after rebooting all servers and disconnecting the last server we could gain access to the cluster again. The problem now is that we have a ghost node with the "Estranged"...