after some switch issues i now get failed exit code 1 when trying to start VMs

O

offerlam

Renowned Member
Dec 30, 2012
218
0
81
Denmark
Hi all,

I have three proxmox servers in a cluster...

After i changed the switch backend where i have two switches running in stack mode AT-8000GS i have had some problems with the routing so now i only run with one switch and the other turned off. That being said LACP bond and all that is still configured.. but my proxmox servers can ping eachother and storage aswell as backup nas so all is well network wise i would assume...

it was after i turned off the second switch and everything started connecting again i noticed that i can't start VMs on node 1 and 2 ... but i can do so on node 0

the error i get is failed exit code 1
also RGmanager seems to be running on node 1 and 2 where i can't start vms but not on node0 .. when i try to start it on node 0 it says ok and goes back to stopped...

here is PCEVM status PCVEM NODE and PVEVERSION for node 0

root@proxmox00:~# pvecm status
Version: 6.2.0
Config Version: 50
Cluster Name: DingITCluster
Cluster Id: 44340
Cluster Member: Yes
Cluster Generation: 175468
Membership state: Cluster-Member
Nodes: 3
Expected votes: 3
Total votes: 3
Node votes: 1
Quorum: 2
Active subsystems: 1
Flags:
Ports Bound: 0
Node name: proxmox00
Node ID: 1
Multicast addresses: 239.192.173.225
Node addresses: 10.10.99.20
root@proxmox00:~# pvecm nodes
Node Sts Inc Joined Name
1 M 175444 2014-10-21 00:24:36 proxmox00
2 M 175468 2014-10-21 00:26:43 proxmox01
3 M 175468 2014-10-21 00:26:43 proxmox02
root@proxmox00:~# /etc/init.d/pve-cluster restart
Restarting pve cluster filesystem: pve-cluster.
root@proxmox00:~# cls
-bash: cls: command not found
root@proxmox00:~# clear
root@proxmox00:~# pvecm status
Version: 6.2.0
Config Version: 50
Cluster Name: DingITCluster
Cluster Id: 44340
Cluster Member: Yes
Cluster Generation: 175468
Membership state: Cluster-Member
Nodes: 3
Expected votes: 3
Total votes: 3
Node votes: 1
Quorum: 2
Active subsystems: 1
Flags:
Ports Bound: 0
Node name: proxmox00
Node ID: 1
Multicast addresses: 239.192.173.225
Node addresses: 10.10.99.20
root@proxmox00:~# pvecm nodes
Node Sts Inc Joined Name
1 M 175444 2014-10-21 00:24:36 proxmox00
2 M 175468 2014-10-21 00:26:43 proxmox01
3 M 175468 2014-10-21 00:26:43 proxmox02
root@proxmox00:~# pveversion -v
proxmox-ve-2.6.32: 3.2-124 (running kernel: 2.6.32-28-pve)
pve-manager: 3.2-2 (running version: 3.2-2/82599a65)
pve-kernel-2.6.32-28-pve: 2.6.32-124
pve-kernel-2.6.32-23-pve: 2.6.32-109
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.5-1
pve-cluster: 3.0-12
qemu-server: 3.1-15
pve-firmware: 1.1-2
libpve-common-perl: 3.0-14
libpve-access-control: 3.0-11
libpve-storage-perl: 3.0-19
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-6
vzctl: 4.0-1pve5
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.7-6
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.2-1
root@proxmox00:~#
Click to expand...

and node 1

root@proxmox01:~# pvecm status
Version: 6.2.0
Config Version: 50
Cluster Name: DingITCluster
Cluster Id: 44340
Cluster Member: Yes
Cluster Generation: 175468
Membership state: Cluster-Member
Nodes: 3
Expected votes: 3
Total votes: 3
Node votes: 1
Quorum: 2
Active subsystems: 6
Flags:
Ports Bound: 0
Node name: proxmox01
Node ID: 2
Multicast addresses: 239.192.173.225
Node addresses: 10.10.99.21
root@proxmox01:~# pvecm nodes
Node Sts Inc Joined Name
1 M 175468 2014-10-21 00:26:43 proxmox00
2 M 175440 2014-10-21 00:24:19 proxmox01
3 M 175444 2014-10-21 00:24:56 proxmox02
root@proxmox01:~# /etc/init.d/pve-cluster restart
Restarting pve cluster filesystem: pve-cluster.
root@proxmox01:~# clear
root@proxmox01:~# pvecm status
Version: 6.2.0
Config Version: 50
Cluster Name: DingITCluster
Cluster Id: 44340
Cluster Member: Yes
Cluster Generation: 175468
Membership state: Cluster-Member
Nodes: 3
Expected votes: 3
Total votes: 3
Node votes: 1
Quorum: 2
Active subsystems: 6
Flags:
Ports Bound: 0
Node name: proxmox01
Node ID: 2
Multicast addresses: 239.192.173.225
Node addresses: 10.10.99.21
root@proxmox01:~# pvecm nodes
Node Sts Inc Joined Name
1 M 175468 2014-10-21 00:26:43 proxmox00
2 M 175440 2014-10-21 00:24:19 proxmox01
3 M 175444 2014-10-21 00:24:56 proxmox02
root@proxmox01:~# pveversion -v
proxmox-ve-2.6.32: 3.2-124 (running kernel: 2.6.32-28-pve)
pve-manager: 3.2-2 (running version: 3.2-2/82599a65)
pve-kernel-2.6.32-28-pve: 2.6.32-124
pve-kernel-2.6.32-23-pve: 2.6.32-109
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.5-1
pve-cluster: 3.0-12
qemu-server: 3.1-15
pve-firmware: 1.1-2
libpve-common-perl: 3.0-14
libpve-access-control: 3.0-11
libpve-storage-perl: 3.0-19
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-6
vzctl: 4.0-1pve5
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.7-6
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.2-1
root@proxmox01:~#
Click to expand...

and node 2

root@proxmox02:~# pvecm status
Version: 6.2.0
Config Version: 50
Cluster Name: DingITCluster
Cluster Id: 44340
Cluster Member: Yes
Cluster Generation: 175468
Membership state: Cluster-Member
Nodes: 3
Expected votes: 3
Total votes: 3
Node votes: 1
Quorum: 2
Active subsystems: 6
Flags:
Ports Bound: 0
Node name: proxmox02
Node ID: 3
Multicast addresses: 239.192.173.225
Node addresses: 10.10.99.22
root@proxmox02:~# pvecm nodes
Node Sts Inc Joined Name
1 M 175468 2014-10-21 00:26:43 proxmox00
2 M 175444 2014-10-21 00:24:56 proxmox01
3 M 175436 2014-10-21 00:24:09 proxmox02
root@proxmox02:~# /etc/init.d/pve-cluster restart
Restarting pve cluster filesystem: pve-cluster.
root@proxmox02:~# clear
root@proxmox02:~# pvecm status
Version: 6.2.0
Config Version: 50
Cluster Name: DingITCluster
Cluster Id: 44340
Cluster Member: Yes
Cluster Generation: 175468
Membership state: Cluster-Member
Nodes: 3
Expected votes: 3
Total votes: 3
Node votes: 1
Quorum: 2
Active subsystems: 6
Flags:
Ports Bound: 0
Node name: proxmox02
Node ID: 3
Multicast addresses: 239.192.173.225
Node addresses: 10.10.99.22
root@proxmox02:~# pvevm nodes
-bash: pvevm: command not found
root@proxmox02:~# clear
root@proxmox02:~# pvecm status
Version: 6.2.0
Config Version: 50
Cluster Name: DingITCluster
Cluster Id: 44340
Cluster Member: Yes
Cluster Generation: 175468
Membership state: Cluster-Member
Nodes: 3
Expected votes: 3
Total votes: 3
Node votes: 1
Quorum: 2
Active subsystems: 6
Flags:
Ports Bound: 0
Node name: proxmox02
Node ID: 3
Multicast addresses: 239.192.173.225
Node addresses: 10.10.99.22
root@proxmox02:~# pvecm node
Node Sts Inc Joined Name
1 M 175468 2014-10-21 00:26:43 proxmox00
2 M 175444 2014-10-21 00:24:56 proxmox01
3 M 175436 2014-10-21 00:24:09 proxmox02
root@proxmox02:~# pveversion -v
proxmox-ve-2.6.32: 3.2-124 (running kernel: 2.6.32-28-pve)
pve-manager: 3.2-2 (running version: 3.2-2/82599a65)
pve-kernel-2.6.32-28-pve: 2.6.32-124
pve-kernel-2.6.32-23-pve: 2.6.32-109
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.5-1
pve-cluster: 3.0-12
qemu-server: 3.1-15
pve-firmware: 1.1-2
libpve-common-perl: 3.0-14
libpve-access-control: 3.0-11
libpve-storage-perl: 3.0-19
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-6
vzctl: 4.0-1pve5
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.7-6
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.2-1
root@proxmox02:~#
Click to expand...

I have tried to run /etc/init.d/pve-cluster restart on all nodes but didn't help!!

I need help ASAP! :)
 
offerlam said:
Hi all,

I have three proxmox servers in a cluster...

After i changed the switch backend where i have two switches running in stack mode AT-8000GS i have had some problems with the routing so now i only run with one switch and the other turned off. That being said LACP bond and all that is still configured.. but my proxmox servers can ping eachother and storage aswell as backup nas so all is well network wise i would assume...

it was after i turned off the second switch and everything started connecting again i noticed that i can't start VMs on node 1 and 2 ... but i can do so on node 0

the error i get is failed exit code 1
also RGmanager seems to be running on node 1 and 2 where i can't start vms but not on node0 .. when i try to start it on node 0 it says ok and goes back to stopped...

here is PCEVM status PCVEM NODE and PVEVERSION for node 0



and node 1



and node 2



I have tried to run /etc/init.d/pve-cluster restart on all nodes but didn't help!!

I need help ASAP! :)
Click to expand...

Crisis averded :)

after doing a restart og both CMAN and PVE Cluster service it all came up well and fine
 
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back