Really strange problem.
I have a Intel modular server with proxmox on two blade.
This night backup errors:
After that, access to web was not possibile. SSH inside servers and /etc/init.d/pve-cluster restart and /etc/init/pve-manager restart fixed the login problem.
But inside the web page I can't see other server status.
I run /etc/init.d/cman restart but errors appeared
How can i restart cman service which seem to be the answer for my problem?
On proxmox 1 infos are:
root@proxmox1:/etc/pve/qemu-server# pveversion -v
pve-manager: 2.3-13 (pve-manager/2.3/7946f1f1)
running kernel: 2.6.32-19-pve
proxmox-ve-2.6.32: 2.3-96
pve-kernel-2.6.32-13-pve: 2.6.32-72
pve-kernel-2.6.32-19-pve: 2.6.32-96
pve-kernel-2.6.32-14-pve: 2.6.32-74
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-20
pve-firmware: 1.0-21
libpve-common-perl: 1.0-49
libpve-access-control: 1.0-26
libpve-storage-perl: 2.3-7
vncterm: 1.0-4
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.4-10
ksm-control-daemon: 1.1-1
and on proxmox2
root@proxmox2:/etc/pve/qemu-server# pveversion -v
proxmox-ve-2.6.32: 3.2-126 (running kernel: 2.6.32-29-pve)
pve-manager: 3.2-4 (running version: 3.2-4/e24a91c1)
pve-kernel-2.6.32-19-pve: 2.6.32-96
pve-kernel-2.6.32-16-pve: 2.6.32-82
pve-kernel-2.6.32-29-pve: 2.6.32-126
pve-kernel-2.6.32-14-pve: 2.6.32-74
pve-kernel-2.6.32-26-pve: 2.6.32-114
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-16
pve-firmware: 1.1-3
libpve-common-perl: 3.0-18
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-8
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.2-1
(yeah yeah I know are different versions but they worked without problems for a long time)
Thanks for any hints
I have a Intel modular server with proxmox on two blade.
This night backup errors:
Code:
[COLOR=#000000][FONT=Times New Roman]Detailed backup logs:[/FONT][/COLOR]
vzdump [COLOR=#336699][URL="callto:104 111 105 101"]104 111 105 101[/URL][/COLOR] --quiet 1 --mailto [COLOR=#336699]backup@comune.ledro.tn.it[/COLOR] --mode snapshot --compress lzo --storage QNAP
101: Jun 26 23:01:02 INFO: Starting Backup of VM 101 (qemu)
101: Jun 26 23:01:02 INFO: status = running
101: Jun 26 23:02:42 INFO: unable to open file '/etc/pve/nodes/proxmox2/qemu-server/101.conf.tmp.459261' - Device or resource busy
101: Jun 26 23:02:42 INFO: update VM 101: -lock backup
101: [COLOR=red]Jun 26 23:02:42 ERROR: Backup of VM 101 failed - command 'qm [COLOR=#336699]set 101[/COLOR] --lock backup' failed: exit code 2
[/COLOR] 105: Jun 26 23:02:42 INFO: Starting Backup of VM 105 (qemu) 105: Jun 26 23:02:42 INFO: status = running
105: Jun 26 23:03:12 INFO: update VM 105: -lock backup
105: Jun 26 23:03:12 INFO: unable to open file '/etc/pve/nodes/proxmox2/qemu-server/105.conf.tmp.459348' - Device or resource busy
105: [COLOR=red]Jun 26 23:03:12 ERROR: Backup of VM 105 failed - command 'qm [COLOR=#336699]set 105[/COLOR] --lock backup' failed: exit code 2
[/COLOR] 111: Jun 26 23:03:12 INFO: Starting Backup of VM 111 (qemu)
111: Jun 26 23:03:12 INFO: status = running
111: Jun 26 23:04:22 INFO: VM is locked (backup)
111: [COLOR=red]Jun 26 23:04:22 ERROR: Backup of VM 111 failed - command 'qm [COLOR=#336699]set 111[/COLOR] --lock backup' failed: exit code 110 [/COLOR][COLOR=red]
[/COLOR]
But inside the web page I can't see other server status.
I run /etc/init.d/cman restart but errors appeared
Code:
Stopping cluster:
Stopping dlm_controld...
[FAILED]
How can i restart cman service which seem to be the answer for my problem?
On proxmox 1 infos are:
root@proxmox1:/etc/pve/qemu-server# pveversion -v
pve-manager: 2.3-13 (pve-manager/2.3/7946f1f1)
running kernel: 2.6.32-19-pve
proxmox-ve-2.6.32: 2.3-96
pve-kernel-2.6.32-13-pve: 2.6.32-72
pve-kernel-2.6.32-19-pve: 2.6.32-96
pve-kernel-2.6.32-14-pve: 2.6.32-74
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-20
pve-firmware: 1.0-21
libpve-common-perl: 1.0-49
libpve-access-control: 1.0-26
libpve-storage-perl: 2.3-7
vncterm: 1.0-4
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.4-10
ksm-control-daemon: 1.1-1
and on proxmox2
root@proxmox2:/etc/pve/qemu-server# pveversion -v
proxmox-ve-2.6.32: 3.2-126 (running kernel: 2.6.32-29-pve)
pve-manager: 3.2-4 (running version: 3.2-4/e24a91c1)
pve-kernel-2.6.32-19-pve: 2.6.32-96
pve-kernel-2.6.32-16-pve: 2.6.32-82
pve-kernel-2.6.32-29-pve: 2.6.32-126
pve-kernel-2.6.32-14-pve: 2.6.32-74
pve-kernel-2.6.32-26-pve: 2.6.32-114
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-16
pve-firmware: 1.1-3
libpve-common-perl: 3.0-18
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-8
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.2-1
(yeah yeah I know are different versions but they worked without problems for a long time)
Thanks for any hints