Bug 234522 - rsync error at io.c(604) on every operation
rsync error at io.c(604) on every operation
Product: Fedora
Classification: Fedora
Component: rsync (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Simo Sorce
Depends On:
  Show dependency treegraph
Reported: 2007-03-29 16:00 EDT by Steve Friedman
Modified: 2007-11-30 17:12 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-04-02 11:21:28 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
tshark packet capture (544 bytes, application/octet-stream)
2007-03-29 16:00 EDT, Steve Friedman
no flags Details

  None (edit)
Description Steve Friedman 2007-03-29 16:00:08 EDT
Description of problem:

Rsync generates an error on every attempted operation of an otherwise normal
looking config file.

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

How reproducible:
Every time

Steps to Reproduce:
1. Install per rsyncd.conf below
2. /sbin/chkconfig rsync on
3. rsync localhost::
Actual results:
[steve@BETHGS xinetd.d]# rsync localhost::
rsync: read error: Connection reset by peer (104)
rsync error: error in rsync protocol data stream (code 12) at io.c(604)

Expected results:
A list of the available modules.

Additional info:
See attached packet capture (captured with /usr/sbin/tshark -i lo -w rsync.cap
"tcp port 873").

Here is the rsyncd.conf:

        path = /home
        comment = home
        hosts allow =,

        path = /etc
        comment = config files
        hosts allow =
Comment 1 Steve Friedman 2007-03-29 16:00:09 EDT
Created attachment 151231 [details]
tshark packet capture
Comment 2 Simo Sorce 2007-03-30 08:49:38 EDT
The cap file shows just an immediate TCP reset, do you have any log file on the
server side that shows what's going on?
Comment 3 Steve Friedman 2007-03-30 10:24:51 EDT
This was rsync localhost::, so the capture includes both sides of the operation.

The /var/log/messages just had:

START: rsync pid=3863 from=
EXIT: rsync status=1 pid=3863 duration=0(sec)
Comment 4 Simo Sorce 2007-03-30 14:03:59 EDT
Sorry but I can't reproduce this, are you sure you don;t have any firewall
rules, host allow/deny or anything else blocking?

I used exactly your rsyncd.conf on a fresh install.

And I get back what I should.

$ rsync localhost::
home            home
config          config files
Comment 5 Steve Friedman 2007-03-30 14:47:56 EDT
Grr..  I rather expected that (surely I couldn't have been the first to notice a
problem with rsync).  However, my firewall allows all packets to/from -i lo
(which is confirmed by the packet capture that shows the tcp session
connecting).  /etc/hosts.allow and /etc/hosts.deny contain only comments.  `rpm
-qV rsync` shows that the only file modified is /etc/xinetd.d/rsync (and I did
that via /sbin/chkconfig so I couldn't have screwed up the config file).

Just to add to the confusion, I have a four boxes that are configured via a set
of scripts (so the configurations are managed and differences are
well-contained).  Three boxes return this error, while the fourth works as
expected.  I'll report back when/if I discover any differences.  If you have any
other ideas on where to look, I'd appreciate them.
Comment 6 Simo Sorce 2007-03-30 15:26:49 EDT
you could run rsync (the server) under strace and see if there ... wait, have
you selinux enabled by chance? :-)
Comment 7 Steve Friedman 2007-03-30 15:42:28 EDT
I have selinux enabled on all four boxes.  I'll try strace and/or disabling
selinux next week.
Comment 8 Steve Friedman 2007-04-02 11:07:52 EDT
Indeed, for some reason, /etc/rsyncd.conf was labeled correctly on one box and
incorrectly (as etc_runtime_t rather than etc_t) on three of the boxes.  Doing
`/sbin/chkconfig /etc/rsyncd.conf` resolved the problem.  How I hate the
inability to synchronize the labeling of files and selinux policies, let me
count the ways...  Sorry for the noise.
Comment 9 Steve Friedman 2007-04-02 11:14:26 EDT
A feature request:  log the failure to open /etc/rsyncd.conf.  /var/log/messages
contained the startup/exit of rsyncd and I didn't think to look at
/var/log/audit/audit.log.  (Unfortunately, I forgot that the avc doesn't show up
in /var/log/messages anymore.)
Comment 10 Simo Sorce 2007-04-02 11:21:28 EDT
Ok I am closing this bug, please open a new one for the feature request eventually.

Note You need to log in before you can comment on or make changes to this bug.