Loading kernel modules... ERROR: could not insert 'configfs': Exec format error

Sakis

Active Member
Aug 14, 2013
121
6
38
I tried to start cman in 2 nodes of a non-Ha proxmox cluster (5 nodes) and i got the following error during start:

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

All nodes have many days uptime and there is not a recent kernel update to anyone. All running 2.6.32-37 that is the last installed (not update happened and restart is pending)
conifgfs.ko exists in all nodes and has the same mdsum

pveversion -v in all nodes is the same

proxmox-ve-2.6.32: 3.4-150 (running kernel: 2.6.32-37.pve)
pve-manager: 3.4-3 (running version: 3.4-3/2fc72fee)
pve-kernel-2.6.32-32-pve: 2.6.32.-136
pve-kernel-2.6.32-37-pve: 2.6.32.-150
pve-kernel-2.6.32-29-pve: 2.6.32.-126
pve-kernel-2.6.32-31-pve: 2.6.32.-132


I tried to modprobe configfs and got same error

Can somebody help? Rebooting is the last option.
 
I suggest you update to latest available kernel first (2.6.32-40-pve), then reboot the node
 
I have same problem, but my cluster (with 16 nodes) has broken and i must restart nodes with 2.6.32-37 kernel. After reboot broken nodes i must restart cman and corosync on all nodes. That is problematic when cluster have 300+ virtuals.
This problem becomes very often, when i running on kernel eg. 2.6.32-40 and proxmox team deploy kernel update with same number.
 
I lost quorum in cluster (without touch). I dont know why, because only 3 nodes from 16 are affected with this problem, and after reboot affected nodes, cluster goes to hell. Corosync processes growing in memory to full utilization of available ram (64gb ram on server, and corosync process have approximately 39GB allocated ram on nodes). I saw on switches huge multicast but nodes still not connected, because lost quorum and processes still trying to connect (in loop). pvecm status print lost quorum, clustat report only single node cluster.
This is second time, when i must use full restart cluster with this procedure (clusterssh and kill processes in same time and start in same time on all servers). Cluster starts without problems, errors and running smooth.

(one mistake from previous post, restart cman and pve-cluster, no cman and corosync)
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!