cannot edit or list /etc/pve/qemu-server

[polopolo92]

Hello
after removing some old unused snapshot (zfs destroy) I cannot acces into /etc/pve/qemu-server (to update the configuration file)

if I do "ls" in this directory the command never return

I reboot the server, same problem

any ideas how to "unblock" this ?

thanks

 

[Moayad]

Hi,

- have you any error in Syslog?
- could you post the VM config qm config <VMID>
- what is your Proxmox version pveversion -v
- what say the output of qm listsnapshot <VMID> command?
- have you tried to unlock the VM using (qm unlock <VMID>)

 

[polopolo92]

Hello

now after 2 days I have "Connection failure. Network error or Proxmox VE services not running?" or

"Connection error 401: permission denied - invalid PVE ticket" from another node

I can connect using ssh


So I reboot again the server

- have you any error in Syslog?
no error into syslog

- could you post the VM config qm config <VMID>
it is not link to a specific VM

qm config 112
bootdisk: scsi0
cores: 4
memory: 32768
name: osm03
net0: virtio=00:50:56:01:94:44,bridge=vmbr0,firewall=1
numa: 0
ostype: l26
parent: autohourly210110081321
scsi0: local-zfs:vm-112-disk-0,size=500G
scsihw: virtio-scsi-pci
smbios1: uuid=b1684d49-540f-4027-8ab3-1ea05a91de87
sockets: 1
startup: order=2,up=180
vmgenid: 327e350b-2516-4d67-8356-67b68174ab49


- what is your Proxmox version pveversion -v
[B]proxmox-ve: 6.3-1 (running kernel: 5.4.103-1-pve) pve-manager: 6.3-6 (running version: 6.3-6/2184247e) pve-kernel-5.4: 6.3-7 pve-kernel-helper: 6.3-7 pve-kernel-5.3: 6.1-6 pve-kernel-5.4.103-1-pve: 5.4.103-1 pve-kernel-5.4.78-2-pve: 5.4.78-2 pve-kernel-5.4.65-1-pve: 5.4.65-1 pve-kernel-5.3.18-3-pve: 5.3.18-3 pve-kernel-5.3.10-1-pve: 5.3.10-1 ceph-fuse: 12.2.11+dfsg1-2.1+b1 corosync: 3.1.0-pve1 criu: 3.11-3 glusterfs-client: 5.5-3 ifupdown: residual config ifupdown2: 3.0.0-1+pve3 ksm-control-daemon: 1.3-1 libjs-extjs: 6.0.1-10 libknet1: 1.20-pve1 libproxmox-acme-perl: 1.0.7 libproxmox-backup-qemu0: 1.0.3-1 libpve-access-control: 6.1-3 libpve-apiclient-perl: 3.1-3 libpve-common-perl: 6.3-5 libpve-guest-common-perl: 3.1-5 libpve-http-server-perl: 3.1-1 libpve-storage-perl: 6.3-7 libqb0: 1.0.5-1 libspice-server1: 0.14.2-4~pve6+1 lvm2: 2.03.02-pve4 lxc-pve: 4.0.6-2 lxcfs: 4.0.6-pve1 novnc-pve: 1.1.0-1 openvswitch-switch: 2.12.3-1 proxmox-backup-client: 1.0.9-1 proxmox-mini-journalreader: 1.1-1 proxmox-widget-toolkit: 2.4-6 pve-cluster: 6.2-1 pve-container: 3.3-4 pve-docs: 6.3-1 pve-edk2-firmware: 2.20200531-1 pve-firewall: 4.1-3 pve-firmware: 3.2-2 pve-ha-manager: 3.1-1 pve-i18n: 2.2-2 pve-qemu-kvm: 5.2.0-3 pve-xtermjs: 4.7.0-3 pve-zsync: 2.0-4 qemu-server: 6.3-7 smartmontools: 7.2-pve2 spiceterm: 3.1-1 vncterm: 1.6-2 zfsutils-linux: 0.8.5-pve1[/B]

- what say the output of qm listsnapshot <VMID> command?
qm listsnapshot 112
`-> OSRM_BACK 2020-05-25 21:50:54 no-description
`-> OSRM_FRONT 2020-05-25 22:33:04 working
`-> current You are here!


- have you tried to unlock the VM using (qm unlock <VMID>)
no VM are locked when the problem occurs

 

[polopolo92]

Now after one day reboot I cannot again connect to Proxmox except by ssh (but VM are running )




How could I fix using ssh , as after reboot it is stable only a couple of hours ?

 

[Moayad]

Thanks for the output.

Please send us your network configuration cat /etc/network/interfaces

 

[polopolo92]

hello
I hidded the public adresses


# network interface settings; autogenerated # Please do NOT modify this file directly, unless you know what # you're doing. # # If you want to manage parts of the network configuration manually, # please utilize the 'source' or 'source-directory' directives to do # so. # PVE will preserve these directives, but will NOT read its network # configuration from sourced files, so do not attempt to move any of # the PVE managed interfaces into external files! auto lo iface lo inet loopback auto enp1s0f0 iface enp1s0f0 inet manual auto enp1s0f1 iface enp1s0f1 inet dhcp mtu 9000 auto vmbr0 iface vmbr0 inet static address x.x.x.x/24 gateway x.x.x.1 bridge-ports enp1s0f0 bridge-stp off bridge-fd 0 auto vmbr1 iface vmbr1 inet manual ovs_type OVSBridge ovs_mtu 9000 post-up ovs-vsctl add-port vmbr1 gre0 -- set interface gre0 type=gre options:remote_ip=''10.95.251.139'' #ovs_ports eno2 #Proxmox01 post-up ovs-vsctl add-port vmbr1 gre1 -- set interface gre1 type=gre options:remote_ip=''10.91.145.14'' post-up ovs-vsctl add-port vmbr1 gre2 -- set interface gre2 type=gre options:remote_ip=''10.90.160.139''

 

[polopolo92]

Hello

no solution ?

Thanks

 

[AngryAdm]

I cant access those files either anymore and it is tremendously anoying. They are also write protected when booting normally.
this in effect causes a situation where a vm boots at startup and crashes the system...

Attemting to boot into safe mode just gives me an empty directory. It did not use to be this way. What has changed?