Bug 908690

Summary: rsyslog stop and info about 'syslog.socket' appears randomly
Product: Red Hat Enterprise Linux 7 Reporter: Petr Sklenar <psklenar>
Component: systemdAssignee: Michal Sekletar <msekleta>
Status: CLOSED WONTFIX QA Contact: qe-baseos-daemons
Severity: medium Docs Contact:
Priority: high    
Version: 7.0CC: jscotka, lnykryn, systemd-maint-list
Target Milestone: beta   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-10 12:08:14 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Petr Sklenar 2013-02-07 10:47:07 UTC
Description of problem:
info about 'syslog.socket' appears randomly

Version-Release number of selected component (if applicable):
systemd-197-1.el7.1.1.x86_64

How reproducible:
always with my machine

Steps to Reproduce:
Redirecting to /bin/systemctl status  syslog.service
rsyslog.service - System Logging Service
	  Loaded: loaded (/usr/lib/systemd/system/rsyslog.service; enabled)
	  Active: active (running) since Thu 2013-02-07 05:37:46 EST; 5min ago
	Main PID: 23521 (rsyslogd)
	  CGroup: name=systemd:/system/rsyslog.service
		  └─23521 /sbin/rsyslogd -n -c 5

Feb 07 05:37:46 pes-guest-67.lab.eng.brq.redhat.com systemd[1]: Starting System Logging Service...
Feb 07 05:37:46 pes-guest-67.lab.eng.brq.redhat.com systemd[1]: Started System Logging Service.

[root@pes-guest-67 ~]# service rsyslog status
Redirecting to /bin/systemctl status  rsyslog.service
rsyslog.service - System Logging Service
	  Loaded: loaded (/usr/lib/systemd/system/rsyslog.service; enabled)
	  Active: active (running) since Thu 2013-02-07 05:37:46 EST; 5min ago
	Main PID: 23521 (rsyslogd)
	  CGroup: name=systemd:/system/rsyslog.service
		  └─23521 /sbin/rsyslogd -n -c 5

Feb 07 05:37:46 pes-guest-67.lab.eng.brq.redhat.com systemd[1]: Starting System Logging Service...
Feb 07 05:37:46 pes-guest-67.lab.eng.brq.redhat.com systemd[1]: Started System Logging Service.

[root@pes-guest-67 ~]# service rsyslog stop
Redirecting to /bin/systemctl stop  rsyslog.service
Job for rsyslog.service canceled.

[root@pes-guest-67 ~]# service rsyslog stop
Redirecting to /bin/systemctl stop  rsyslog.service
Job for rsyslog.service canceled.

[root@pes-guest-67 ~]# service rsyslog stop
Redirecting to /bin/systemctl stop  rsyslog.service
Warning: Stopping rsyslog.service, but it can still be activated by:
  syslog.socket

[root@pes-guest-67 ~]# service rsyslog stop
Redirecting to /bin/systemctl stop  rsyslog.service
Job for rsyslog.service canceled.


  
Actual results:
info about 'syslog.socket' appears randomly

Expected results:
there is all the time info about 'syslog.socket'

Additional info:

Comment 2 Michal Sekletar 2013-12-10 12:08:14 UTC
Some changes has been proposed upstream to mitigate this behavior but we agreed that we are not going to patch over the fact that user is doing something inherently racy here (applies to stopping to all services activated by rather busy sockets). But afaik stopping rsyslog via service command shouldn't make noise anymore because of changes in rsyslog. Closing as WONTFIX.