Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1324754

Summary:	rsyncd unit enters failed state on exit
Product:	Red Hat Enterprise Linux 7	Reporter:	Harald Klein <hklein>
Component:	rsync	Assignee:	Michal Ruprich <mruprich>
Status:	CLOSED ERRATA	QA Contact:	Karel Srot <ksrot>
Severity:	medium	Docs Contact:
Priority:	high
Version:	7.2	CC:	sreber, thozza
Target Milestone:	rc	Keywords:	Patch
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	rsync-3.0.9-18.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-01 12:44:57 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:
Bug Depends On:
Bug Blocks:	1298243, 1380362, 1393869

Description Harald Klein 2016-04-07 08:05:07 UTC

Description of problem:

When stopping the "rsyncd" service, the unit enters failed state

Version-Release number of selected component (if applicable):

RHEL 7.2

How reproducible:

Stop the rsyncd unit

Actual results:

Mar 22 10:41:20 vmlxrhel7 systemd: Stopping fast remote file copy program daemon...
Mar 22 10:41:21 vmlxrhel7 rsyncd[1583]: rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(551) [Receiver=3.0.9]
Mar 22 10:41:21 vmlxrhel7 systemd: rsyncd.service: main process exited, code=exited, status=20/n/a
Mar 22 10:41:21 vmlxrhel7 systemd: Stopped fast remote file copy program daemon.
Mar 22 10:41:21 vmlxrhel7 systemd: Unit rsyncd.service entered failed state.
Mar 22 10:41:21 vmlxrhel7 systemd: rsyncd.service failed.

Expected results:

Unit should not enter "failed state"

Additional info:

It seems that when rsync is started as daemon (rsync --daemon --no-detach) and is terminated by a SIGTERM signal, the exit code is always 20. If this is intended behaviour, the unit file could be extended with a "SuccessExitStatus=20" option.

Comment 10 errata-xmlrpc 2017-08-01 12:44:57 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2214