Right now I cannot reboot no single node, because I can not migrate VMs..
On 14.04.15 12:05, Bart Lageweg | Bizway wrote:
Hi, Error is not lan, but kernel modules -> reboot node and its fixed Grtz *Van:*pve-user [mailto:[email protected]] *Namens *Sten Aus *Verzonden:* dinsdag 14 april 2015 11:02 *Aan:* Dietmar Maurer; [email protected] *CC:* [email protected] *Onderwerp:* Re: [PVE-User] Adding a cluster node breaks whole cluster 9000 MTU is based only on storage VLANs, which use 10G interfaces. All Proxmox cluster communication uses VLAN15, MTU1500.Rebooted Linksys switch, no good. Swapped to another dumb switch without VLANs - again no good.cman restart in one node *service cman restart* Stopping cluster: Stopping dlm_controld... [ OK ] Stopping fenced... [ OK ] Stopping cman... [ OK ] Unloading kernel modules... [ OK ] Unmounting configfs... [ OK ] Starting cluster: Checking if cluster has been disabled at boot... [ OK ] Checking Network Manager... [ OK ] Global setup... [ OK ]Loading kernel modules... ERROR: could not insert 'configfs': Exec format error[FAILED] On 14.04.15 11:58, Dietmar Maurer wrote: As I told you, we used dumb Linksys switch for cluster communication and it all worked for weekend and yesterday. And yesterday evening whole cluster is red againYesterday's log:http://pastebin.com/sLpnGgeS Pure corosync log:http://pastebin.com/TzyUdYaJMaybe a problem with packet fragmentation. Do you use special MTU sizes?
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ pve-user mailing list [email protected] http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
