Hide Forgot
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.
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