Bug 619358 - rsyslog service behaves strangely in stopped state when another third-party syslog daemon is running.
Summary: rsyslog service behaves strangely in stopped state when another third-party s...
Alias: None
Product: Fedora
Classification: Fedora
Component: rsyslog   
(Show other bugs)
Version: 13
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Tomas Heinrich
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2010-07-29 11:21 UTC by Denys Vlasenko
Modified: 2016-09-20 04:49 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2011-06-29 12:49:25 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Denys Vlasenko 2010-07-29 11:21:46 UTC
I want to run third-party syslog daemon on my machine.
Therefore I want standard Fedora syslog daemon, rsyslogd, to not run.

I went to System->Administration-Services and stopped and disabled rsyslog service.

Then I set up third-party syslog daemon. It works ok.

After reboot, rsyslog service is mightly confused by /var/run/syslogd.pid created by _other_ syslog daemon:

# cat /var/run/syslogd.pid
# pidof rsyslogd
# service rsyslog status
rsyslogd (pid  1375) is running...

So it thinks that rsyslogd is running, while in reality it does not.

Thus, system falsely thinks that rsyslog service is running.

This causes System->Administration-Services GUI to also show it as running, which is confusing. Attempts to stop or (re)start it will not work and generally will look broken:

# service rsyslog stop
Shutting down system logger:                               [FAILED]

# service rsyslog start
Starting system logger:

Seeing this, user is confused. Did "start" work or did it fail?

# service rsyslog restart
Shutting down system logger:                               [FAILED]
Starting system logger: 


I propose to stop relying on /var/run/syslogd.pid and use `pidof rsyslogd` instead to find rsyslogd pid.
This would be my first choice: pidof works, why bother messing with pid files which are not reliable anyway? For example, stale ones will remain on unclean shutdown...

Alternatively, use rsyslogd-specific pid file, say, /var/run/rsyslogd.pid (note added letter 'r').

Comment 1 Bug Zapper 2011-06-01 12:34:39 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  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 WONTFIX if it remains open with a Fedora 
'version' of '13'.

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 prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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.

The process we are following is described here: 

Comment 2 Bug Zapper 2011-06-29 12:49:25 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.

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.