Bug #19245
closed
Smart-proxy logrotates all files in /var/log/foreman-proxy
Description
Smart-proxy logrotates files matching the /var/log/foreman-proxy/*.log glob. This may cause issues for processes logging to the same directory which won't be notified about their logs being rotated (smart_proxy_dynflow_core for example). We need to make it logrotate only the files it produces.
Updated by Adam Ruzicka over 7 years ago
- Project changed from Smart Proxy to Packaging
- Category deleted (
Packaging)
Updated by Adam Ruzicka over 7 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman-packaging/pull/1610 added
Updated by Adam Ruzicka over 7 years ago
- Project changed from Packaging to Katello
Updated by Adam Ruzicka over 7 years ago
- Project changed from Katello to Packaging
Updated by Anonymous over 7 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset foreman-packaging|1d5c8f1eac7bfeb2bde7448dd63ae2f580e5748e.
Updated by The Foreman Bot over 7 years ago
- Pull request https://github.com/theforeman/foreman-packaging/pull/1612 added
Updated by Adam Ruzicka over 7 years ago
- Status changed from Closed to Ready For Testing
Reopening since the DEB PR is not yet merged.
Updated by Adam Ruzicka over 7 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset foreman-packaging|2f4d4b82c0007712a4f966ca4ecb98ebde6d9f9b.
Updated by Ivan Necas over 7 years ago
- Related to Bug #19521: Smart_proxy_dynflow_core doesn't deploy its logrotate config added
Updated by Ivan Necas over 7 years ago
We fixed this issue in smart_proxy_dynflow_core in #19521 and in 1.15, we're not getting
error: tfm-rubygem-smart_proxy_dynflow_core:1 duplicate log entry for /var/log/foreman-proxy/smart_proxy_dynflow_core.log
when running
logrorate /etc/logrotate.conf.
Therefore, I'm proposing this change to be backported to 1.15.1, as the logorate is not working properly in this combination
and I reverting this in remote execution would introduce the regression, that we tried to fix. It also spams the /var/spool/mail/root every night,
which is something we should keep clean if possible.