logrotate config uses syslog group
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
logrotate (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Confirmed
|
Undecided
|
Unassigned | ||
Cosmic |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
The default logrotate config uses the "syslog" group.
> # use the syslog group by default, since this is the owning group
> # of /var/log/syslog.
> su root syslog
This is not correct anymore since 16.04, because:
1. "syslog" group doesn't exist on a stock Ubuntu 16.04 system, it only gets installed via rsyslog
2. The owning group is actually "adm".
This results in logrotate terminating with the following error during cron.daily run:
run-parts -v /etc/cron.daily
run-parts: executing /etc/cron.
error: /etc/logrotate.
And can be fixed by changing syslog to adm group.
This is not present when rsyslog is installed, but only because that package creates the syslog group. This is a common bug in lighter environments, like Docker, where syslog-ng is a common choice instead of rsyslog, like in this issue:
https:/
tags: | added: rls-bb-incoming |
tags: | removed: rls-bb-incoming |
tags: | added: rls-bb-notfixing rls-cc-notfixing |
Status changed to 'Confirmed' because the bug affects multiple users.