Search results

I've tested multicasting from several different nodes, everything looks good to me. It's always like that: # asmping 224.0.2.1 192.168.200.71 asmping joined (S,G) = (*,224.0.2.234) pinging 192.168.200.71 from 192.168.200.66 unicast from 192.168.200.71, seq=1 dist=0 time=0.220 ms multicast...

Well, I have loads of those lines in syslog: May 29 13:05:54 proxmox-21 pmxcfs[366472]: [status] crit: cpg_send_message failed: 9 May 29 13:05:54 proxmox-21 pmxcfs[366472]: [status] crit: cpg_send_message failed: 9 May 29 13:05:54 proxmox-21 pmxcfs[366472]: [status] crit: cpg_send_message...

Well, all nodes except of one are on 2.3, and one node is already upgraded to 3.0. That worked perfect until I tried to upgrade the second one. The nodes in the Webui are marked red, so I guess the cluster has a Problem, but I can't figure out what. A "ps aux |grep pve" on the node I'm trying...

Hello Tom, thanks for the fast reply, but this doesn't solve the problem. It still says "unable to copy ssh ID". Here is the output of pvecm status: Version: 6.2.0 Config Version: 39 Cluster Name: Balanstrasse Cluster Id: 15487 Cluster Member: Yes Cluster Generation: 556 Membership state...

Hello, I've upgraded one node of the cluster (delete node from cluster, fresh install of 3.0), and now I'm unable to add it to the cluster again. And the Webgui also broke! in Detail: - I did a pvecm delnode - I rebooted the node and made a fresh installation of pve 3.0 - When trying to do...

Well, first of all I also don't get the reason to reboot on a regular base. We reboot the hosts maybe every one or two years for any reason. But if you want to do it for performance, just reboot one after another. The guests will come up automatically, and in my opinion those are the machines...

After the reinstallation everything works fine. Best regards

I checked multicasting as described, and everything is fine. But the problem persists. As it it a fresh installation, I'll now reinstall it. This should be the better way. Thanks for your support, I hope the reinstallation does the trick. If not I'll post here again. Best regards

I just tried it again, and before the pvestatd error ps aux |grep cman showed me those three tasks: root 6222 0.0 0.0 10884 1740 pts/0 S+ 16:59 0:00 /bin/bash /etc/init.d/cman start root 6242 0.0 0.0 10884 892 pts/0 S+ 16:59 0:00 /bin/bash /etc/init.d/cman...

Believe me, I did. Maybe it didn't reach the point where something would be written? I think this log entries: Aug 30 12:01:51 proxmox-14 pmxcfs[1429]: [main] notice: teardown filesystem belong to that line in the shell output: Stopping pve cluster filesystem: pve-cluster. then the cman...

Well, ok, so here is directly after the startup two attempts to join, a pvedaemon restart, and another attempt to join: Aug 30 12:01:51 proxmox-14 pmxcfs[1429]: [main] notice: teardown filesystem Aug 30 12:01:52 proxmox-14 pmxcfs[1429]: [main] notice: exit proxmox configuration filesystem (0)...

Hi, I have a Proxmox 2.1 cluster up and running for 2 Months. The last days I added a few nodes, and now the last one (the 11th) is not able to join the cluster. Network is fine, system clocks match, the other ten are running flawless. They're all blades devided up in 2 bladecenters which...

Thanks, life can be so easy :-)

Hi, is there a possibility to make pveca aware of vlans? I have to use vlans, so I don`t have an eth0, but an eth0.300, which is not recognised. Can I enter the IP Adress somewhere, so that I am able to create a cluster? Here is my network config: auto lo iface lo inet loopback auto...