Back up errors What do they mean?

[Drax]

In doing back ups of the VMs I get the following errors. Not sure how to fix them. Please advise.

command 'qm set 101400 --lock backup' failed: exit code 25 This VM is shut down.
vma_co_write write error - Broken pipe This VM is running.
volume 'local_data:4145/vm-4145-disk-2.qcow2' does not exist The VM exists, I have never created the file it references. How is it created?

Any help is greatly appreciated.

 

[fireon]

What mode to you use for backup?

 

[Drax]

The backups are done to an expernal USB drive connected to the node. There has neve been an issue prior to now. What are these errors? What do they mean?

 

[fireon]

So again, what backupmode to you use? And what pveversion to you use? "pveversion -v" Post also the vmconfig from the affected vm. "qm config <vmid>".

 

[Drax]

where is that information located? in the GUI?

 

[fireon]

where is that information located? in the GUI?

Backupmode in the GUI, the rest via SSH.

 

[Drax]

PVE is

proxmox-ve-2.6.32: 3.1-114 (running kernel: 2.6.32-26-pve)
pve-manager: 3.1-21 (running version: 3.1-21/93bf03d4)
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-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.0-2
pve-cluster: 3.0-8
qemu-server: 3.1-8
pve-firmware: 1.0-23
libpve-common-perl: 3.0-8
libpve-access-control: 3.0-7
libpve-storage-perl: 3.0-17
pve-libspice-server1: 0.12.4-2
vncterm: 1.1-4
vzctl: 4.0-1pve4
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-17
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.1-1

Backup mode is snapshot Here is config for each VM

101400
~# qm config 101400
acpi: 1
boot: c
bootdisk: ide0
cores: 2
cpuunits: 1000
description: Network IP is
freeze: 0
ide0: local_data:101400/vm-101400-disk-1.raw,format=raw,size=69880M
ide1: local_data:101400/vm-13126-disk-2.raw,format=raw,size=32G
kvm: 1
lock: backup
memory: 4000
name:
net0: e1000........
ostype: w2k3
sockets: 1

136
bootdisk: virtio0
cores: 2
memory: 4000
name:
net0: virtio=1.....
ostype: l26
sockets: 2
virtio0: local_data:136/vm-136-disk-1.qcow2,format=qcow2,size=200G
virtio1: local_data:136/vm-136-disk-2.qcow2,format=qcow2,size=500G

 

[fireon]

Hui, PVE3 is really a long time ago and no supported anymore. But config look likes good. Hmm...

1. The Backuptarget is ok, tested copy files on?
2. ... have rebooted the server? If you have a long uptime.... for example: some years, maybe this would be the fasted solution.
3. Any special changes on the system?

Test this:

qm unlock <vmid>

Test the backup.

Or...
Shutdown a VM and test in stopmode manualy, or test in snapshotmode manualy. If all failing post the syslogs from the process.

 

[Drax]

How can I find the IP addresses assigned to a VM?

 

[fireon]

How can I find the IP addresses assigned to a VM?

Why ipadresses? ... don't know... dhcp, static, that what you gave.

 

[Drax]

I am looking to find the public IP for each VM.

 

[RobFantini]

for each VM log in at PVE console.

then use the virtual machine operating system screen or command line tools to find IP.

for linux:

ip a

for older linux use ' ifconfig -a '

for windows , and i almost never use it so this is from memory:
search and run the command line program and run "ipconfig"