HA resource agent: Unable to open /dev/vzctl

A

aTan

Renowned Member
Mar 22, 2013
44
5
73
Hi. I've set up HA managed CTs, but after reboot it can't start CTs with this error.

task started by HA resource agent
Unable to open /dev/vzctl: No such file or directory
Please check that vzdev kernel module is loaded and you have sufficient permissions to access the file.
TASK ERROR: command 'vzctl start 1000' failed: exit code 5


pve-manager: 2.3-13 (pve-manager/2.3/7946f1f1)
running kernel: 2.6.32-19-pve
proxmox-ve-2.6.32: 2.3-93
pve-kernel-2.6.32-19-pve: 2.6.32-93
pve-kernel-2.6.32-18-pve: 2.6.32-88
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.4-4
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.93-2
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.9-1
pve-cluster: 1.0-36
qemu-server: 2.3-18
pve-firmware: 1.0-21
libpve-common-perl: 1.0-49
libpve-access-control: 1.0-26
libpve-storage-perl: 2.3-6
vncterm: 1.0-3
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.4-8
ksm-control-daemon: 1.1-1
 
Yes, sure. I can start it manually. But then HA doesn't work. When I stop rgmanager, CTs don't move to another node. It seems like after booting it tries to start CTs before VZ is up.
 
aTan said:
Yes, sure. I can start it manually. But then HA doesn't work. When I stop rgmanager, CTs don't move to another node. It seems like after booting it tries to start CTs before VZ is up.
Click to expand...

Oh, that can cause the issue. Please can you file a bug at bugzilla.proxmox.com?
 
You must log in or register to reply here.
Top Bottom