Permission denied error for vzdump command

[IT_Infra_Support]

root@Node2:/RAID-5-Storage/images/162# vzdump 162 --dumpdir /dev/pve/dump-ccf --mode stop --compress lzo
INFO: starting new backup job: vzdump 162 --compress lzo --mode stop --dumpdir /dev/pve/dump-ccf
INFO: Starting Backup of VM 162 (qemu)
INFO: status = running
INFO: unable to open file '/etc/pve/nodes/Node2/qemu-server/162.conf.tmp.58895' - Permission denied
INFO: update VM 162: -lock backup
ERROR: Backup of VM 162 failed - command 'qm set 162 --lock backup' failed: exit code 2
INFO: Backup job finished with errors
job errors
root@Node2:/RAID-5-Storage/images/162#

 

[fiona]

Hi,
please post the output of

pveversion -v
systemctl status pve-cluster.service
pvecm status
stat /etc/pve/nodes/Node2/qemu-server

 

[IT_Infra_Support]

root@Node2:/RAID-5-Storage/images/162# pveversion -v
proxmox-ve: 5.1-32 (running kernel: 4.13.13-2-pve)
pve-manager: 5.1-41 (running version: 5.1-41/0b958203)
pve-kernel-4.13.13-2-pve: 4.13.13-32
libpve-http-server-perl: 2.0-8
lvm2: 2.02.168-pve6
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-19
qemu-server: 5.0-18
pve-firmware: 2.0-3
libpve-common-perl: 5.0-25
libpve-guest-common-perl: 2.0-14
libpve-access-control: 5.0-7
libpve-storage-perl: 5.0-17
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-3
pve-docs: 5.1-12
pve-qemu-kvm: 2.9.1-5
pve-container: 2.0-18
pve-firewall: 3.0-5
pve-ha-manager: 2.0-4
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.1.1-2
lxcfs: 2.0.8-1
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.7.3-pve1~bpo9


root@Node2:/RAID-5-Storage/images/162# systemctl status pve-cluster.service
● pve-cluster.service - The Proxmox VE cluster filesystem
Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2021-05-26 16:48:42 IST; 2 years 1 months ago
Process: 1994 ExecStartPost=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS)
Process: 1914 ExecStart=/usr/bin/pmxcfs (code=exited, status=0/SUCCESS)
Main PID: 1989 (pmxcfs)
Tasks: 12 (limit: 9830)
Memory: 67.3M
CPU: 1d 15h 8min 25.866s
CGroup: /system.slice/pve-cluster.service
└─1989 /usr/bin/pmxcfs
Jul 20 02:48:52 Node2 pmxcfs[1989]: [dcdb] notice: data verification successful
Jul 20 03:48:52 Node2 pmxcfs[1989]: [dcdb] notice: data verification successful
Jul 20 04:48:52 Node2 pmxcfs[1989]: [dcdb] notice: data verification successful
Jul 20 05:48:52 Node2 pmxcfs[1989]: [dcdb] notice: data verification successful
Jul 20 06:48:52 Node2 pmxcfs[1989]: [dcdb] notice: data verification successful
Jul 20 07:48:52 Node2 pmxcfs[1989]: [dcdb] notice: data verification successful
Jul 20 08:48:52 Node2 pmxcfs[1989]: [dcdb] notice: data verification successful
Jul 20 09:48:52 Node2 pmxcfs[1989]: [dcdb] notice: data verification successful
Jul 20 10:48:52 Node2 pmxcfs[1989]: [dcdb] notice: data verification successful
Jul 20 11:48:52 Node2 pmxcfs[1989]: [dcdb] notice: data verification successful




oot@Node2:/RAID-5-Storage/images/162# pvecm status
Quorum information
------------------
Date: Thu Jul 20 12:21:33 2023
Quorum provider: corosync_votequorum
Nodes: 1
Node ID: 0x00000002
Ring ID: 2/3740
Quorate: No

Votequorum information
----------------------
Expected votes: 2
Highest expected: 2
Total votes: 1
Quorum: 2 Activity blocked
Flags:

Membership information
----------------------
Nodeid Votes Name
0x00000002 1 172.18.61.63 (local)





root@Node2:/RAID-5-Storage/images/162# stat /etc/pve/nodes/Node2/qemu-server
File: /etc/pve/nodes/Node2/qemu-server
Size: 0 Blocks: 0 IO Block: 4096 directory
Device: 2fh/47d Inode: 6 Links: 2
Access: (0555/dr-xr-xr-x) Uid: ( 0/ root) Gid: ( 33/www-data)
Access: 2018-05-22 17:12:18.000000000 +0530
Modify: 2018-05-22 17:12:18.000000000 +0530
Change: 2018-05-22 17:12:18.000000000 +0530
Birth: -

 

[fiona]

root@Node2:/RAID-5-Storage/images/162# pveversion -v
proxmox-ve: 5.1-32 (running kernel: 4.13.13-2-pve)

Please upgrade, this version is unsupported since a long time and running it is a security risk.
https://pve.proxmox.com/wiki/Upgrade_from_5.x_to_6.0

oot@Node2:/RAID-5-Storage/images/162# pvecm status
Quorum information
------------------
Date: Thu Jul 20 12:21:33 2023
Quorum provider: corosync_votequorum
Nodes: 1
Node ID: 0x00000002
Ring ID: 2/3740
Quorate: No

Your cluster is not quorate, so you cannot write to the shared cluster file system /etc/pve: https://pve.proxmox.com/pve-docs/chapter-pvecm.html#_quorum

 

[IT_Infra_Support]

Yes, we have a cluster but from 2 weeks there is problem that if i login in node A then node B VM's are not visible and same with if i login in node B then node A VMs are not visible.


root@Node2:/RAID-5-Storage/images/162# ls -lh /etc/pve
total 4.0K
-r--r----- 1 root www-data 451 Apr 26 2018 authkey.pub
-r--r----- 1 root www-data 450 May 22 2018 corosync.conf
-r--r----- 1 root www-data 16 Apr 26 2018 datacenter.cfg
lr-xr-xr-x 1 root www-data 0 Jan 1 1970 local -> nodes/Node2
lr-xr-xr-x 1 root www-data 0 Jan 1 1970 lxc -> nodes/Node2/lxc
dr-xr-xr-x 2 root www-data 0 Apr 26 2018 nodes
lr-xr-xr-x 1 root www-data 0 Jan 1 1970 openvz -> nodes/Node2/openvz
dr-x------ 2 root www-data 0 Apr 26 2018 priv
-r--r----- 1 root www-data 2.1K Apr 26 2018 pve-root-ca.pem
-r--r----- 1 root www-data 1.7K Apr 26 2018 pve-www.key
lr-xr-xr-x 1 root www-data 0 Jan 1 1970 qemu-server -> nodes/Node2/qemu-server
-r--r----- 1 root www-data 211 Apr 30 2018 storage.cfg
-r--r----- 1 root www-data 256 Apr 25 2022 user.cfg
-r--r----- 1 root www-data 119 Apr 26 2018 vzdump.cron
root@Node2:/RAID-5-Storage/images/162#

 

[fiona]

Check your configuration in /etc/pve/corosync.conf and /etc/hosts to make sure the IPs and host names are correct. If you need to edit the configuration, see https://pve.proxmox.com/pve-docs/chapter-pvecm.html#_corosync_configuration
Can you ping the nodes from each other?