Dear all,
I have a privileged ctn debian11 based that is a LAMP web server with a single web app developed by myself that worked for years without any issues. This app needs to access some windows shared folders on the operator's PC that uses the app, for making this the most reliable possible I'm using autofs.
From ten days happens that randomly I cannot access the webserver anymore, if I inspect the container in that moment(this is 4th time) it is still accessible from the proxmox webgui but not from ssh. Apache seems to be ok, so what I tried to do is simply to restart the container, but crashes and I have no more console and container is still up but unresponsive. After that I kill -9 the ctn process and if try to restart the container with
I'm getting this error
so at this point I have to reboot the proxmox host and everything works ok. I didn't found another solution except rebooting the host for now, and I cannot replicate the issue by myself but the feeling is that happens when I loose connectivity with the shared folders, obviously I tried to replicate the issue disconnecting the lan cable from the operator's pc but seems to works, so must be something related to autofs but I'm not sure how this happens. After the issue I installed all proxmox 7 updates and debian 11 updates inside the ctn but problem happened again. I will not update to proxmox 8 for now because it's a ceph cluster and we are i heavy production now so I will update in next months.
ctn info
proxmox info
I have a privileged ctn debian11 based that is a LAMP web server with a single web app developed by myself that worked for years without any issues. This app needs to access some windows shared folders on the operator's PC that uses the app, for making this the most reliable possible I'm using autofs.
From ten days happens that randomly I cannot access the webserver anymore, if I inspect the container in that moment(this is 4th time) it is still accessible from the proxmox webgui but not from ssh. Apache seems to be ok, so what I tried to do is simply to restart the container, but crashes and I have no more console and container is still up but unresponsive. After that I kill -9 the ctn process and if try to restart the container with
Bash:
pct start 105 --debugI'm getting this error
Bash:
failed to remove directory '/sys/fs/cgroup/lxc/105/ns/system.slice/autofs.service': Device or resource busyso at this point I have to reboot the proxmox host and everything works ok. I didn't found another solution except rebooting the host for now, and I cannot replicate the issue by myself but the feeling is that happens when I loose connectivity with the shared folders, obviously I tried to replicate the issue disconnecting the lan cable from the operator's pc but seems to works, so must be something related to autofs but I'm not sure how this happens. After the issue I installed all proxmox 7 updates and debian 11 updates inside the ctn but problem happened again. I will not update to proxmox 8 for now because it's a ceph cluster and we are i heavy production now so I will update in next months.
ctn info
Bash:
root@nodo1:~# pct config 105
arch: amd64
cores: 4
features: fuse=1,mount=nfs;cifs,nesting=1
hostname: dirittimarittimi.example.com
memory: 2048
net0: name=eth0,bridge=vmbr0,firewall=1,gw=192.168.25.62,hwaddr=06:B1:1F:9C:17:EB,ip=192.168.25.213/24,type=veth
onboot: 1
ostype: debian
rootfs: ceph_ct:vm-105-disk-0,size=20G
swap: 512
tags: debianproxmox info
Bash:
root@nodo1:~# pveversion -v
proxmox-ve: 7.4-1 (running kernel: 5.15.108-1-pve)
pve-manager: 7.4-16 (running version: 7.4-16/0f39f621)
pve-kernel-5.15: 7.4-4
pve-kernel-5.13: 7.1-9
pve-kernel-5.15.108-1-pve: 5.15.108-2
pve-kernel-5.15.107-2-pve: 5.15.107-2
pve-kernel-5.15.107-1-pve: 5.15.107-1
pve-kernel-5.15.104-1-pve: 5.15.104-2
pve-kernel-5.15.102-1-pve: 5.15.102-1
pve-kernel-5.15.85-1-pve: 5.15.85-1
pve-kernel-5.15.83-1-pve: 5.15.83-1
pve-kernel-5.15.64-1-pve: 5.15.64-1
pve-kernel-5.15.53-1-pve: 5.15.53-1
pve-kernel-5.15.35-1-pve: 5.15.35-3
pve-kernel-5.13.19-6-pve: 5.13.19-15
pve-kernel-5.13.19-4-pve: 5.13.19-9
pve-kernel-5.13.19-2-pve: 5.13.19-4
pve-kernel-5.13.19-1-pve: 5.13.19-3
ceph: 16.2.13-pve1
ceph-fuse: 16.2.13-pve1
corosync: 3.1.7-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: residual config
ifupdown2: 3.1.0-1+pmx4
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve2
libproxmox-acme-perl: 1.4.4
libproxmox-backup-qemu0: 1.3.1-1
libproxmox-rs-perl: 0.2.1
libpve-access-control: 7.4.1
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.4-2
libpve-guest-common-perl: 4.2-4
libpve-http-server-perl: 4.2-3
libpve-rs-perl: 0.7.7
libpve-storage-perl: 7.4-3
libqb0: 1.0.5-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.2-2
lxcfs: 5.0.3-pve1
novnc-pve: 1.4.0-1
proxmox-backup-client: 2.4.3-1
proxmox-backup-file-restore: 2.4.3-1
proxmox-kernel-helper: 7.4-1
proxmox-mail-forward: 0.1.1-1
proxmox-mini-journalreader: 1.3-1
proxmox-offline-mirror-helper: 0.5.2
proxmox-widget-toolkit: 3.7.3
pve-cluster: 7.3-3
pve-container: 4.4-6
pve-docs: 7.4-2
pve-edk2-firmware: 3.20230228-4~bpo11+1
pve-firewall: 4.3-5
pve-firmware: 3.6-5
pve-ha-manager: 3.6.1
pve-i18n: 2.12-1
pve-qemu-kvm: 7.2.0-8
pve-xtermjs: 4.16.0-2
qemu-server: 7.4-4
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+3
vncterm: 1.7-1
zfsutils-linux: 2.1.11-pve1