Bug 10304 - safe_read failed to read 1 bytes
Summary: safe_read failed to read 1 bytes
Alias: None
Product: rsync
Classification: Unclassified
Component: core (show other bugs)
Version: 3.1.0
Hardware: x86 FreeBSD
: P5 normal (vote)
Target Milestone: ---
Assignee: Wayne Davison
QA Contact: Rsync QA Contact
Depends on:
Reported: 2013-12-02 12:20 UTC by Pol Hallen
Modified: 2013-12-04 06:41 UTC (History)
0 users

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Pol Hallen 2013-12-02 12:20:38 UTC
Hello! I've a rsync server on debian 6 (v3.0.7-2). this linux command executed from other linux clients runs perfectly:

rsync --password-file=/usr/home/user/.rsync.pass --log-file=/var/log/docs.log -avvvr user@ /usr/home/user/docs

same line executed from FreeBSD 9.2-RELEASE (rsync rsync-3.1.0_1) show this:

opening tcp connection to port 873
Connected to (
rsync: safe_read failed to read 1 bytes [Receiver]: Connection reset by peer (54)
rsync error: error in rsync protocol data stream (code 12) at io.c(251) [Receiver=3.1.0]
[Receiver] _exit_cleanup(code=12, file=io.c, line=251): about to call exit(12)

on rsync server I don't see any error log and wasted many many hours to check this problem

any idea?


Comment 1 Pol Hallen 2013-12-02 12:26:33 UTC
On rsync (debian 7) no problems.
Comment 2 Wayne Davison 2013-12-04 06:41:04 UTC
The "Connection reset by peer" error is just telling you that the remote side went away.  Since it is a daemon, you'll need to find out why the daemon side is exiting.  If the daemon log doesn't have any info, you may be able to run something like "strace -f -o /tmp/output -p $DAEMON_PID" and see if that tells you what is going wrong.