lxc /proc/kmsg read failed

jms1000

Well-Known Member
Oct 25, 2016
150
4
58
58
Germany, Schkeuditz
www.sv-forensik.de
Hallo,

nachdem ich einen LXC (Debian) von einem 5.x Proxmox-Cluster auf einen 6.1-5 Cluster geschoben habe, läuft der LXC wunber weiter - aber einem Problem:

/proc/kmsg gehört jetzt nobody.nogroup und der syslog kann es nicht mehr lesen :(

habe ich irgendwas übersehen ? hat jemand passende Tips auf lager?

/proc ist RW gemountet, aber chmod und chown (meine erste Idee) bringen permission denied ...

PS: Es scheint nicht am Container zu liegen, bei einem neuem LXC aus dem Template passiert das gleiche.
 
und das backup läuft auch nicht mehr:

[...
]INFO: creating archive '/mnt/pve/backup/dump/vzdump-lxc-2010-2020_01_11-09_58_27.tar.lzo'
INFO: tar: ./root/.lesshst: Cannot open: Permission denied
INFO: tar: ./var/lib/apt/lists/partial: Cannot open: Permission denied
INFO: tar: ./var/lib/syslog-ng/syslog-ng.persist: Cannot open: Permission denied
INFO: tar: ./var/log/checksecurity/sockets.today: Cannot open: Permission denied
INFO: tar: ./var/log/setuid/setuid.today: Cannot open: Permission denied
INFO: tar: ./var/log/btmp: Cannot open: Permission denied
INFO: Total bytes written: 7268218880 (6.8GiB, 199MiB/s)
INFO: tar: Exiting with failure status due to previous errors
[...]
 

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!