FS#10882 - Cannot sync ABS
Attached to Project:
Arch Linux
Opened by Andrej Podzimek (andrej) - Thursday, 10 July 2008, 18:54 GMT
Last edited by Greg (dolby) - Monday, 21 July 2008, 14:12 GMT
Opened by Andrej Podzimek (andrej) - Thursday, 10 July 2008, 18:54 GMT
Last edited by Greg (dolby) - Monday, 21 July 2008, 14:12 GMT
|
Details
Description:
ABS script fails with the following output. ==> Starting ABS sync... rsync: connection unexpectedly closed (0 bytes received so far) [receiver] rsync error: error in rsync protocol data stream (code 12) at io.c(635) [receiver=3.0.3] I am using rsync.archlinux.org (and the default config file). I run three ArchLinux machines. Two of them can use ABS with no problem at all. Perhaps one of my IP addresses is blocked. (But I haven't done anyting wrong to the server...) Additional info: * package version(s) [andrej@xandrej ~]$ pacman -Q pacman abs rsync pacman 3.1.4-1 abs 2.1-1 rsync 3.0.3-1 * config and/or log files etc. # # /etc/abs/abs.conf # # the top-level directory of all your PKGBUILDs [ "$ABSROOT" = "" ] && ABSROOT="/var/abs/" # # Server to sync from # SYNCSERVER="rsync.archlinux.org" # # The architecture to fetch abs for # Either i686 or x86_64 # ARCH="i686" # # REPOS to be parsed by abs (in this order) # (prefix a repo with a ! to disable it) # # Note: If a repo is removed, it is still fetched! # Repos must be preceded with a ! to prevent fetching # REPOS=(core extra !unstable community !testing) Steps to reproduce: abs |
This task depends upon
rsync -mrtv --no-motd --delete-after \
--include=/core --include=/core/bash \
--exclude=/core/* --exclude=/* \
rsync.archlinux.org::abs/i686/ /tmp/abs/
[root@xandrej abs]# rsync -mrtv --no-motd --delete-after \
> --include=/core --include=/core/bash \
> --exclude=/core/* --exclude=/* \
> rsync.archlinux.org::abs/i686/ /tmp/
rsync: connection unexpectedly closed (0 bytes received so far) [receiver]
rsync error: error in rsync protocol data stream (code 12) at io.c(635) [receiver=3.0.3]
Reverse mappings differ. (But this probably doesn't cause the problem...)
This is what I see on the machine that cannot connect:
64 bytes from rsync.archlinux.org (66.211.213.17): icmp_seq=1 ttl=47 time=142 ms
A machine where ABS works says:
64 bytes from 66-211-213-17.velocity.net (66.211.213.17): icmp_seq=1 ttl=51 time=123 ms
http://www.nabble.com/Non-clean-Rsync-3.0.3-exit-on-OSX-td18247610.html
But there's a significant difference: All my machines have Intel 32-bit CPUs (Core Duo, dual Pentium III, Pentium M). So this cannot be an endianness issue.
I'm attaching the output from strace.
Conclusions:
1) There is (probably) nothing wrong with my system.
2) The problem is IP-address-dependent.
3) ABS worked fine even in Prague just a couple of days ago.
This could happen if the rsync server was using a complex iptables configuration, possibly with a firewall daemon. For some reason or other, one of my IP addresses is now considered untrustworthy...