Bug#944243: logrotate fails with "Permission denied" on LXC guest

journalctl -u logrotate: Nov 06 17:12:22 syslog systemd[1]: Starting Rotate log files... Nov 06 17:12:22 syslog systemd[381]: logrotate.service: Failed to set up mount namespacing: Permission denied Nov 06 17:12:22 syslog systemd[381]: logrotate.service: Failed at step NAMESPACE spawning /usr/sb

Bug#944243: logrotate fails with "Permission denied" on LXC guest

All of these directories are present and are regular directories (not symbolic links). Deleting the specified line has no effect and the problem persists. > Can you please check whether the following directories exist and if > they are symbolic links what target they have: > /var > /var/log > /t

Bug#944243: logrotate fails with "Permission denied" on LXC guest

AppArmor is used and aa-status on the LXC host gives the following output: apparmor module is loaded. 23 profiles are loaded. 21 profiles are in enforce mode.    /usr/bin/evince    /usr/bin/evince-previewer    /usr/bin/evince-previewer//sanitized_helper    /usr/bin/evince-thumbnailer    /us

Bug#944243: logrotate fails with "Permission denied" on LXC guest

s). > Le mercredi 06 novembre 2019 à 17:27:28+0100, Lukáš Jelínek a écrit : >> journalctl -u logrotate: >> >> Nov 06 17:12:22 syslog systemd[1]: Starting Rotate log files... >> Nov 06 17:12:22 syslog systemd[381]: logrotate.service: Failed to set up >> mount namesp

Bug#858595: nginx logrotate doesn't properly switch to new logfiles

I can confirm the bug. I can observe it on many servers - but not only on Debian ones, but on Ubuntu servers too. There is nginx 1.10.3 everywhere.

Bug#949366: bacula-fd: bacula-rd crashes if can't bind to port

Hi Carsten, it was conflicting with another instance of bacula-fd which accidentally persisted running (I didn't report it because it was not reproducible). Regards, Lukas > Control: forwarded -1 https://bugs.bacula.org/view.php?id=2528 > > Hi Lukas, > >> bacula-fd crashes with SIGSEGV if it c