Bug 1297878 - Parallel install of rsyslog and syslog-ng broken
Parallel install of rsyslog and syslog-ng broken
Product: Fedora
Classification: Fedora
Component: rsyslog (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Radovan Sroka
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2016-01-12 11:57 EST by Tomas Heinrich
Modified: 2016-12-20 12:48 EST (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-12-20 12:48:56 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Tomas Heinrich 2016-01-12 11:57:38 EST
Splitting of from bug 1224972.

(In reply to Terje Røsten from comment #18)
> Hi Tomas,
> this change breaks parallel install of rsyslog and syslog-ng.
> rsyslog and syslog-ng both uses /var/run/syslogd.pid as pidfile,
> as an side effect they can both install identical versions of
> /etc/logrotate.d/syslog and both can be installed at the same time.
> When adding rsyslog specific calls into /etc/logrotate.d/syslog you break
> this design.
> rsyslog as of rsyslog-8.10.0-1.fc23.x86_64 uses pidfile /var/run/syslogd.pid
> and the previous line of 
> /bin/kill -HUP `cat /var/run/syslogd.pid 2> /dev/null` 2> /dev/null || true
> still works.
> { If you refuse to revert this change, at least mark syslog-ng as conflict 
>   rsyslog, this way dnf can remove rsyslog when installing syslog-ng. }
Comment 1 Tomas Heinrich 2016-01-12 12:12:35 EST
In my opinion, this whole setup has, cumulatively, created more confusion than good.
I think it would be better to somehow split the preconceptions of rsyslog and syslog-ng about the file layout and content. Such a change should be appropriate for rawhide.

In f23, I guess I'll just revert the logrotate file to the f22 version so that it doesn't cause any more confusion.
Comment 2 Terje Røsten 2016-01-22 18:33:18 EST
Hi Tomas!

This sounds good to me.

I don't care much how this is fixed, the old concept is not that novel.
However it's important that a solution is found soon.

Btw: The problem is present in RHEL7/EPEL also I think.
Comment 5 Fedora End Of Life 2016-11-24 09:52:40 EST
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 6 Fedora End Of Life 2016-12-20 12:48:56 EST
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.