This is the second server with this issue now.
I mentioned it here before:
https://forum.proxmox.com/threads/pct-list-not-working.59820/#post-281223
when I 'pct enter' the lxc, there's no /proc, this causes a lot of problems. It seems a customer sshing as a user then su'ing to root also saw this problem. However when I ssh in I dont have this problem, /proc is there.
This debian 10.2 container hasnt been changed or restarted since 2019 when the host was setup. I've seen similar weirdness happen with cpanel servers (redhat not debian) as well, where systemctl starts reporting issues because various things arent available and processes cant be restarted. (see the above thread.)
In this case, the user couldnt restart apache because "apache2: can't initialize random number generator: no such file or directory".
This has happened on at least 4-5 servers, all on pve 5.4 or newer.
Restarting the lxc container seems to fix the problem.
version info:
proxmox-ve: 5.4-2 (running kernel: 4.15.18-21-pve)
pve-manager: 5.4-13 (running version: 5.4-13/aee6f0ec)
pve-kernel-4.15: 5.4-9
pve-kernel-4.15.18-21-pve: 4.15.18-48
pve-kernel-4.15.18-12-pve: 4.15.18-36
corosync: 2.4.4-pve1
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.1-12
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-55
libpve-guest-common-perl: 2.0-20
libpve-http-server-perl: 2.0-14
libpve-storage-perl: 5.0-44
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.1.0-7
lxcfs: 3.0.3-pve1
novnc-pve: 1.0.0-3
proxmox-widget-toolkit: 1.0-28
pve-cluster: 5.0-38
pve-container: 2.0-40
pve-docs: 5.4-2
pve-edk2-firmware: 1.20190312-1
pve-firewall: 3.0-22
pve-firmware: 2.0-7
pve-ha-manager: 2.0-9
pve-i18n: 1.1-4
pve-libspice-server1: 0.14.1-2
pve-qemu-kvm: 3.0.1-4
pve-xtermjs: 3.12.0-1
qemu-server: 5.0-54
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.13-pve1~bpo2
arch: amd64
cores: 6
features: nesting=1
hostname: foo
memory: 16384
net0: name=eth0,bridge=vmbr0,firewall=1,gw=192.168.0.254,hwaddr=76:5B:23:E3:93:21,ip=192.168.0.236/24,type=veth
ostype: debian
rootfs: local-zfs:subvol-552-disk-0,size=200G
swap: 0
I mentioned it here before:
https://forum.proxmox.com/threads/pct-list-not-working.59820/#post-281223
when I 'pct enter' the lxc, there's no /proc, this causes a lot of problems. It seems a customer sshing as a user then su'ing to root also saw this problem. However when I ssh in I dont have this problem, /proc is there.
This debian 10.2 container hasnt been changed or restarted since 2019 when the host was setup. I've seen similar weirdness happen with cpanel servers (redhat not debian) as well, where systemctl starts reporting issues because various things arent available and processes cant be restarted. (see the above thread.)
In this case, the user couldnt restart apache because "apache2: can't initialize random number generator: no such file or directory".
This has happened on at least 4-5 servers, all on pve 5.4 or newer.
Restarting the lxc container seems to fix the problem.
version info:
proxmox-ve: 5.4-2 (running kernel: 4.15.18-21-pve)
pve-manager: 5.4-13 (running version: 5.4-13/aee6f0ec)
pve-kernel-4.15: 5.4-9
pve-kernel-4.15.18-21-pve: 4.15.18-48
pve-kernel-4.15.18-12-pve: 4.15.18-36
corosync: 2.4.4-pve1
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.1-12
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-55
libpve-guest-common-perl: 2.0-20
libpve-http-server-perl: 2.0-14
libpve-storage-perl: 5.0-44
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.1.0-7
lxcfs: 3.0.3-pve1
novnc-pve: 1.0.0-3
proxmox-widget-toolkit: 1.0-28
pve-cluster: 5.0-38
pve-container: 2.0-40
pve-docs: 5.4-2
pve-edk2-firmware: 1.20190312-1
pve-firewall: 3.0-22
pve-firmware: 2.0-7
pve-ha-manager: 2.0-9
pve-i18n: 1.1-4
pve-libspice-server1: 0.14.1-2
pve-qemu-kvm: 3.0.1-4
pve-xtermjs: 3.12.0-1
qemu-server: 5.0-54
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.13-pve1~bpo2
arch: amd64
cores: 6
features: nesting=1
hostname: foo
memory: 16384
net0: name=eth0,bridge=vmbr0,firewall=1,gw=192.168.0.254,hwaddr=76:5B:23:E3:93:21,ip=192.168.0.236/24,type=veth
ostype: debian
rootfs: local-zfs:subvol-552-disk-0,size=200G
swap: 0