Project

General

Profile

Actions
Copy link

Bug #21032

closed

logrotate conflict: foreman-proxy and tfm-rubygem-smart_proxy_dynflow_core

Added by Radosław Piliszek about 7 years ago. Updated about 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
RPMs
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Foreman - 1.15.2
Red Hat JIRA:

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).

Related issues 1 (0 open — 1 closed)

Related to foreman-tasks - Bug #19224: smart_proxy_dynflow_core.log not reopened during logrotateClosedAdam Ruzicka04/07/2017Actions
Actions
Copy link

Also available in: Atom PDF