Bug 1600350

Summary:	xinetd[21866]: unexpected signal: 18 (Continued) in signal pipe
Product:	Red Hat Enterprise Linux 7	Reporter:	Zeng Yiquan <yzeng>
Component:	xinetd	Assignee:	Jan Synacek <jsynacek>
Status:	CLOSED NOTABUG	QA Contact:	qe-baseos-daemons
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	7.4	CC:	jsynacek, kwalker
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-06-24 07:05:52 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 Zeng Yiquan 2018-07-12 04:26:38 UTC

Description of problem:

After installed xinetd on RHEL7, stop| restart| xined the following error message will output , Does it an excepted message?

===
Jul 12 12:10:07 R74Router xinetd[21866]: unexpected signal: 18 (Continued) in signal pipe
Jul 12 12:10:07 R74Router systemd: Stopping Xinetd A Powerful Replacement For Inetd...
Jul 12 12:10:07 R74Router xinetd[21866]: Exiting...
===
Version-Release number of selected component (if applicable):

I have reproduced it on RHEL7.1~7.5

How reproducible:

Steps to Reproduce:
1. # yum install xinetd -y
2. # systemctl stop xinetd
3. # systemctl restart xinetd


Actual results:

error message output.

Expected results:

no error message output.

Additional info:

Comment 2 Jan Synacek 2018-07-17 09:16:43 UTC

This is harmless. Xinetd merely informs that it got a SIGCONT from systemd. This behaviour is currently not documented, but I'm planning on fixing that soon (see https://bugzilla.redhat.com/show_bug.cgi?id=1601794). Since this is (will be...) a well documented case, I could patch xinetd to simply not log anything if it gets a SIGCONT.

Also, I strongly recommend to use native systemd units instead of xinetd. I can help with the translation if you want.

Comment 6 Jan Synacek 2019-06-24 07:05:52 UTC

See https://bugzilla.redhat.com/show_bug.cgi?id=1601794.