Am Sonntag, dem 05.05.2024 um 11:12 +0200 schrieb Andreas Beckmann: > Usually the solution is to specify 'missingok' in the logrotate > configuration.
There is already a missingok in the configuration. So this is not causing it. > From the attached log (scroll to the bottom...): > > 0m27.6s DEBUG: Starting command: ['nsenter', > '--net=/run/netns/piuparts-netns-4', > '--uts=/srv/piuparts/tmp/tmprFiuJ6/ns-uts', 'chroot', > '/srv/piuparts/tmp/tmprFiuJ6/chroot', '/usr/sbin/logrotate', > '/etc/logrotate.d/vzlogger'] > 0m27.6s DUMP: > error: /etc/logrotate.d/vzlogger:7 unknown user 'vzlogger' > error: found error in /var/log/vzlogger.log , skipping > 0m27.6s ERROR: Command failed (status=1): ['nsenter', > '--net=/run/netns/piuparts-netns-4', > '--uts=/srv/piuparts/tmp/tmprFiuJ6/ns-uts', 'chroot', > '/srv/piuparts/tmp/tmprFiuJ6/chroot', '/usr/sbin/logrotate', > '/etc/logrotate.d/vzlogger'] Unfortunately the logrotate configuration had not been adapted when the service users name had been changed from vzlogger to _vzlogger. This will be fixed with the next upload. Thanks for the report, Joachim -- Papier ist gebundenes CO2. Bitte drucken Sie diese EMail aus und archivieren Sie sie.
