Proxmox 5.4, fully updated.
I am prototyping three Debian 10 containers.
In two of the systems I see the log spew noted in the thread title. In one system I don't.
Poking around the web indicates the solution is PrivateTmp=false. I configured all three systems with that parameter and performed systemctl daemon-reload. After invoking that change the one system stopped with the log spew while the other two continue.
The three containers are configured similarly. Likewise with the Proxmox hosts.
The log spew is triggered by logrotate.timer.
I could disable the systemd timer and rotate logs through cron.
Regardless of any work-arounds, I want to understand why two systems exhibit the error and one does not.
Thank you.
I am prototyping three Debian 10 containers.
In two of the systems I see the log spew noted in the thread title. In one system I don't.
Poking around the web indicates the solution is PrivateTmp=false. I configured all three systems with that parameter and performed systemctl daemon-reload. After invoking that change the one system stopped with the log spew while the other two continue.
The three containers are configured similarly. Likewise with the Proxmox hosts.
The log spew is triggered by logrotate.timer.
I could disable the systemd timer and rotate logs through cron.
Regardless of any work-arounds, I want to understand why two systems exhibit the error and one does not.
Thank you.