I
I´ve set up a new rsync (portage) server. Its name is sulu.cc.fh-lippe.de. Syncing since 10 days with rsync6.de.gentoo.org. Admin contact is: hostmaster@fh-luh.de or mad@cc.fh-lippe.de
On attempting to grab the metadata/timestamp info from this server, the rsync session hangs: receiving file list ... 1 file to consider timestamp.x [infinite pause here] It seems to be OK if you use -z (compression) on the client, after which subsequent sessions from the same IP# also work without -z. (Weird, huh?) Makes me wonder - is the server configured to use --compress or with some compression option in rsyncd.conf?
just a comment here -- we forcibly disable all compression on rsync1.us.gentoo.org by placing: dont compress = * in rsyncd.conf. That may be part of the problem. All connections to rsync1.us.gentoo.org, however, should be done without compression. I will update the rsync.xml file to reflect this.
The server uses --compress .
Can you stop using compression?
all --compress options have been removed. Am using: OPTIONS="--daemon --safe-links --bwlimit=700 --timeout=1800 --config=/var/gentoo/etc/rsyncd.conf" for rsync daemon and OPTS="--quiet --recursive --links --perms --times --devices --delete --timeout=600" for rsync cron script. regards mad
Seems to be working OK now. Would it be possible to increase the max connections from 10 to 15? I've added 193.16.118.119 to the access list for rsync1.us.gentoo.org. Please update your rsync cron jobs to point to rsync1.us.gentoo.org and post back here when you've done so. We'll monitor the server for a couple days to make sure things are working fine. Thanks.
syncing with rsync1 since "Started update at Wed Jul 30 07:30:00 MET DST 2003" max connections was up to 20, only motd was wrong, sorry. regards m
I've noticed a couple of glitches so far. Can you see if anything might be causing some problems? Times are in date -uR format. The first column is when I checked, the second column was the timestamp from the server's last sync. Checked (UTC) Timestamp ================================================ 21:22:04 Wed, 30 Jul 2003 20:31:01 +0000 (expected 21:00) 00:20:43 Wed, 30 Jul 2003 23:31:02 +0000 (expected 00:00) 13:50:19 Thu, 31 Jul 2003 13:01:02 +0000 (expected 13:30)
dont know much about rsync, so ... I took a look in the log and got this around the time you checked the server: Started update at Wed Jul 30 20:00:01 MET DST 2003 End: Wed Jul 30 20:01:38 MET DST 2003 Started update at Wed Jul 30 20:30:00 MET DST 2003 End: Wed Jul 30 20:31:27 MET DST 2003 Started update at Wed Jul 30 21:00:00 MET DST 2003 End: Wed Jul 30 21:01:23 MET DST 2003 Started update at Wed Jul 30 21:30:00 MET DST 2003 End: Wed Jul 30 21:31:25 MET DST 2003 Started update at Wed Jul 30 22:00:00 MET DST 2003 End: Wed Jul 30 22:01:24 MET DST 2003 Started update at Wed Jul 30 22:30:00 MET DST 2003 End: Wed Jul 30 22:31:21 MET DST 2003 Started update at Wed Jul 30 23:00:00 MET DST 2003 rsync: connection unexpectedly closed (1234380 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(150) rsync: connection unexpectedly closed (1234380 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(150) End: Wed Jul 30 23:04:56 MET DST 2003 Started update at Wed Jul 30 23:30:01 MET DST 2003 End: Wed Jul 30 23:32:53 MET DST 2003 Started update at Thu Jul 31 00:00:00 MET DST 2003 End: Thu Jul 31 00:01:44 MET DST 2003 Started update at Thu Jul 31 00:30:00 MET DST 2003 End: Thu Jul 31 00:32:38 MET DST 2003 Started update at Thu Jul 31 01:00:00 MET DST 2003 End: Thu Jul 31 01:01:24 MET DST 2003 Started update at Thu Jul 31 01:30:00 MET DST 2003 End: Thu Jul 31 01:31:24 MET DST 2003 Started update at Thu Jul 31 02:00:00 MET DST 2003 rsync: read error: Connection timed out rsync error: error in rsync protocol data stream (code 12) at io.c(162) End: Thu Jul 31 02:00:51 MET DST 2003 Started update at Thu Jul 31 02:30:00 MET DST 2003 End: Thu Jul 31 02:31:37 MET DST 2003 Started update at Thu Jul 31 03:00:00 MET DST 2003 End: Thu Jul 31 03:01:49 MET DST 2003 i greped through the log and found that it ocures every day arout 23:00 MET Started update at Mon Jul 28 23:00:01 MET DST 2003 rsync: connection unexpectedly closed (1242218 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(150) rsync: connection unexpectedly closed (1242218 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(150) End: Mon Jul 28 23:05:51 MET DST 2003 Dont know about any network downtime at 23:oo but will check that. mad
Martin, Can you post the script or command you are using to rsync against rsync1.us? make sure that you have --timeout=600 in there somewhere, and that you are not using "--compress" Thanks
Created attachment 15458 [details] Rsync log
Created attachment 15459 [details] Rsync log
hi, script to sync: ---- #!/home/mad/bin/bash RSYNC="/opt/local/bin/rsync" #OPTS="--quiet --recursive --links --perms --times --devices --delete --timeout=600" OPTS="--verbose --recursive --links --perms --times --devices --delete --timeout=600" SRC="rsync://rsync1.us.gentoo.org/gentoo-portage" #SRC="rsync://rsync6.de.gentoo.org/gentoo-portage" DST="/var/gentoo/rsync/" echo "Started update at" `date` >> $0.log 2>&1 logger -t rsync "re-rsyncing the gentoo-portage tree" ${RSYNC} ${OPTS} ${SRC} ${DST} >> $0.log 2>&1 echo "End: "`date` >> $0.log 2>&1 ---- have made some research over the weekend, made pings every 15sec to: rsync1.us.gentoo.org : 187.14 rsync6.de.gentoo.org : 22.17 w3.hierling.de : 37.96 Fre Aug 1 19:31:14 CEST 2003 rsync6.de.gentoo.org : [0], 84 bytes, 22.7 ms (22.7 avg, 0% loss) w3.hierling.de : [0], 84 bytes, 37.6 ms (37.6 avg, 0% loss) rsync1.us.gentoo.org : [0], 84 bytes, 186 ms (186 avg, 0% loss) there is no network error over the whole time, no ping got lost. But there are a lot of rsync errors in the log, unfortunally not all at 23pm. ---- Started update at Fri Aug 1 03:30:01 MET DST 2003 rsync: read error: Connection timed out rsync error: error in rsync protocol data stream (code 12) at io.c(162) End: Fri Aug 1 03:30:51 MET DST 2003 Started update at Fri Aug 1 04:00:00 MET DST 2003 rsync: read error: Connection timed out rsync error: error in rsync protocol data stream (code 12) at io.c(162) End: Fri Aug 1 04:00:51 MET DST 2003 Started update at Fri Aug 1 04:30:01 MET DST 2003 receiving file list ... done deleting net-irc/epic4/files/digest-epic4-1.1.7-r1 deleting net-irc/epic4/files/digest-epic4-1.1.7 deleting net-irc/epic4/files/digest-epic4-1.0.1-r2 deleting net-irc/epic4/files/digest-epic4-1.0.1-r1 ---- they ocure mainly aound 23:00 pm, but also 04:00 am or 10:00 am.Would attach complete log but bugzilla wont let me ?? ---- something about my rsync version: rsync version 2.5.5 protocol version 26 Copyright (C) 1996-2002 by Andrew Tridgell and others <http://rsync.samba.org/> Capabilities: 64-bit files, socketpairs, hard links, symlinks, batchfiles, no IPv6, 64-bit system inums, 64-bit internal inums rsync comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. See the GNU General Public Licence for details. i have no clue. regards martin
Turns out that rsync1.us is being over worked. As a result, some servers aren't able to sync properly. We're trying to resolve the problem, but that will take some time. I'm going to do another test to see if the problem is still there. If it is, we'll put this one on hold until we fix rsync1.us. Will post an update in a couple of days.
The first 5 hours looked good, but after that, there were a bunch of missed syncs. I'm going to temporarily remove access from rsync1.us until we can fix it, which may be several weeks. Once we make progress with that, I'll reenable access to rsync1.us and post back here that we're ready to test again. Thanks for you patience.
We've resolved some load problems that rsync1.us was having. I've added the server back on the access list (should be able to sync again in about 30 minutes). Once you start syncing again, let me know and I'll start monitoring. Thanks.
Server is syncing angain since 20.Oct 2003 10.oo a clock.
This server is now rsync16.de.gentoo.org. Please update the motd file to include that information. I've subscribed <mad@cc.fh-lippe.de> to our gentoo-mirrors mailing list (low volume). This list is used to discuss mirror-related issues. Thanks for supporting Gentoo.
