Bug 984651

Summary:	rsync error: received SIGINT, SIGTERM, or SIGHUP
Product:	[Fedora] Fedora	Reporter:	David Highley <david.m.highley>
Component:	rsync	Assignee:	Michal Luscon <mluscon>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	19	CC:	agk, akkaran046, mluscon, ssorce, vvitek
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-07-17 05:31:06 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 David Highley 2013-07-15 15:48:53 UTC

Description of problem:
Rsync fails to work after kernel update

Version-Release number of selected component (if applicable):
rsync-3.0.9-8.fc19.x86_64

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
2013/07/15 08:06:07 [7439] rsyncd version 3.0.9 starting, listening on port 873
2013/07/15 08:10:21 [7439] rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(551) [Receiver=3.0.9]

Expected results:


Additional info:
We are guessing that this is related to the kernel update kernel-headers-3.9.9-302.fc19.x86_64. We see know selinux avc and have tried in Permissive mode as well.

Was working until this update on July 14, 2013. Have not found any other information logged to indicate what the issue is.

Comment 1 David Highley 2013-07-17 05:31:06 UTC

Solved issue. Had disabled firewalld and enabled iptables. Somehow firewalld got reenabled and was blocking rsync.