Bug #21032
closed
logrotate conflict: foreman-proxy and tfm-rubygem-smart_proxy_dynflow_core
Description
Foreman 1.15.4 (1.15.2 was the latest selectable as "found in")
/etc/logrotate.d/foreman-proxy controls /var/log/foreman-proxy/*log and foreman-proxy service is signaled when rotation happens./etc/logrotate.d/tfm-rubygem-smart_proxy_dynflow_core controls /var/log/foreman-proxy/smart_proxy_dynflow_core.log and smart_proxy_dynflow_core service is signaled when rotation happens.
There is a conflict that logrotate catches:
error: tfm-rubygem-smart_proxy_dynflow_core:1 duplicate log entry for /var/log/foreman-proxy/smart_proxy_dynflow_core.log
and ignores the
/etc/logrotate.d/tfm-rubygem-smart_proxy_dynflow_core configuration (smart_proxy_dynflow_core service is never signaled and foreman-proxy service is signaled for its log instead).
Updated by Radosław Piliszek about 7 years ago
Related to Issue #19223, fixing this will cause the same symptoms as in that issue but for smart_proxy_dynflow_core service. Both have to be fixed to restore proper smart_proxy_dynflow_core logging.
Updated by Radosław Piliszek about 7 years ago
Also it looks like Issue #19224 was supposed to be the one where this was fixed but it had been closed prematurely (the behaviour was not corrected then).
Updated by Lukas Zapletal about 7 years ago
For the record, the team is dicussing if SIGHUP is a good signal to support or not. Otherwise the only change is to rewrite policy:
https://github.com/theforeman/smart-proxy/pull/544
If this is accepted, lets move this to dynflow project and make the very same change there. Here:
And here:
Updated by Lukas Zapletal about 7 years ago
- Related to Bug #19224: smart_proxy_dynflow_core.log not reopened during logrotate added
Updated by Radosław Piliszek about 7 years ago
You are right about that, Lukas, but you missed the fact that there is yet another layer of problems: the conflict between files in the same directory. Dynflow's log must be placed somewhere else.
Updated by Radosław Piliszek about 7 years ago
... or foreman-proxy logrotate config must watch less files.
Updated by Ewoud Kohl van Wijngaarden over 3 years ago
- Status changed from New to Closed
The smart_proxy_dynflow_core package has been obsoleted and is no longer shipped.