Backup Promox

ofa

Member
Oct 25, 2019
5
0
6
28
Hello
I have this error when i try to save my VM :
INFO: unable to open file '/etc/pve/nodes/sawato/qemu-server/111.conf.tmp.41114' - Permission denied
Please Help ,I'm just starting with proxmox.
 
Hi Chis,Thanks for reponse ,but it's not resolve my problem.so now i Want to try something.i'll copy my vm directories to another nodes.
But i dont know where is locate vm-disk.
 
This depends on the storage backend you use for your disks. By default they reside as logical volume on the volume group named 'pve'.
See the output of lvs.
If you have a cluster, you can migrate the VMs including the disks to the other node, there is no need to copy the disk images manually.
But regarding your problem, please post the full output of the backup log as well as the output of
Code:
cat /etc/pve/storage.cfg
pvecm status
pvesm status
 
ok.
backup log message :
Code:
2019-10-25 12:15:31 INFO: Starting Backup of VM 111 (qemu)
2019-10-25 12:15:31 INFO: status = stopped
2019-10-25 12:15:33 INFO: unable to open file '/etc/pve/nodes/sawato/qemu-server/111.conf.tmp.23183' - Permission denied
2019-10-25 12:15:33 INFO: update VM 111: -lock backup
2019-10-25 12:15:33 ERROR: Backup of VM 111 failed - command 'qm set 111 --lock backup' failed: exit code 2
-----------------------------------------------------------------------------------------------------------------------
root@awa:/var/lib/vz/dump# pvecm status
Cannot initialize CMAP service
-------------------------------------------------------------------------------------------------------------------------
root@awa:/var/lib/vz/dump# pvesm status
Name Type Status Total Used Available %
local dir disabled 0 0 0 N/A
local-lvm lvmthin disabled 0 0 0 N/A
zfs-backups dir active 526110592 330540928 195569664 62.83%
zfs-containers zfspool active 562884608 367314922 195569685 65.26%
zfs-templates dir active 526110592 330540928 195569664 62.83%
zfs-vm-disks zfspool active 205255162 9685476 195569685 4.72%

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
root@awa:/var/lib/vz/dump# cat /etc/pve/storage.cfg
dir: local
disable
path /var/lib/vz
content vztmpl,iso,backup
maxfiles 1
shared 0

lvmthin: local-lvm
disable
thinpool data
vgname pve
content rootdir,images

zfspool: zfs-vm-disks
pool vm-zfs-pool/vm-disks
content images
sparse 1

dir: zfs-backups
path /vm-zfs-pool
content backup
maxfiles 1
shared 0

zfspool: zfs-containers
pool vm-zfs-pool
content rootdir
sparse 0

dir: zfs-templates
path /vm-zfs-pool
content vztmpl,iso
shared 0
 
Hmm, there seems to be a problem with pmxcfs. Try to restart the services by running
Code:
systemctl restart corosync
systemctl restart pve-cluster
journalctl -u pvecorosync -u pve-cluster
Please post the output in coding brackets, this keeps the formatting and makes output easier to read, thx.
Also, according to your output the VM disks are volumes on vm-zfs-pool/vm-disks.
 
root@sawato:/var/lib/vz/template# systemctl restart corosync
Job for corosync.service failed because the control process exited with error code.
See "systemctl status corosync.service" and "journalctl -xe" for details.
----------------------------------------------------------------------------------------------------------------------------------------------------------------

root@sawato:/var/lib/vz/template# journalctl -u pvecorosync -u pve-cluster
-- Logs begin at Thu 2019-10-24 18:08:53 GMT, end at Wed 2019-10-30 09:48:23 GMT. --
Oct 30 09:47:43 sawato systemd[1]: Stopping The Proxmox VE cluster filesystem...
Oct 30 09:47:43 sawato pmxcfs[2659]: [main] notice: teardown filesystem
Oct 30 09:47:53 sawato systemd[1]: pve-cluster.service: State 'stop-sigterm' timed out. Killing
Oct 30 09:47:53 sawato systemd[1]: pve-cluster.service: Killing process 2659 (pmxcfs) with sign
Oct 30 09:47:53 sawato systemd[1]: pve-cluster.service: Main process exited, code=killed, statu
Oct 30 09:47:53 sawato systemd[1]: Stopped The Proxmox VE cluster filesystem.
Oct 30 09:47:53 sawato systemd[1]: pve-cluster.service: Unit entered failed state.
Oct 30 09:47:53 sawato systemd[1]: pve-cluster.service: Failed with result 'timeout'.
Oct 30 09:47:53 sawato systemd[1]: Starting The Proxmox VE cluster filesystem...
Oct 30 09:47:53 sawato pmxcfs[5557]: [dcdb] notice: wrote new corosync config '/etc/corosync/co
Oct 30 09:47:53 sawato pmxcfs[5557]: [dcdb] notice: wrote new corosync config '/etc/corosync/co
Oct 30 09:47:53 sawato pmxcfs[5557]: [dcdb] crit: corosync-cfgtool -R failed with exit code 1#0
Oct 30 09:47:53 sawato pmxcfs[5557]: [dcdb] crit: corosync-cfgtool -R failed with exit code 1#0
Oct 30 09:47:53 sawato pmxcfs[5575]: [quorum] crit: quorum_initialize failed: 2
Oct 30 09:47:53 sawato pmxcfs[5575]: [quorum] crit: can't initialize service
Oct 30 09:47:53 sawato pmxcfs[5575]: [confdb] crit: cmap_initialize failed: 2
Oct 30 09:47:53 sawato pmxcfs[5575]: [confdb] crit: can't initialize service
Oct 30 09:47:53 sawato pmxcfs[5575]: [dcdb] crit: cpg_initialize failed: 2
Oct 30 09:47:53 sawato pmxcfs[5575]: [dcdb] crit: can't initialize service
Oct 30 09:47:53 sawato pmxcfs[5575]: [status] crit: cpg_initialize failed: 2
Oct 30 09:47:53 sawato pmxcfs[5575]: [status] crit: can't initialize service
---------------------------------------------------------------------------------------------------------------------------------------------------------

After trying to start the corosync in vain, I dissociated the nodes. Currently there is only one node that is autonomous. I would just like to recover some data which is in the vm.
 

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!