The RAID controller for rsync5.us.gentoo.org is failing, I'm going to replace it ASAP tomorrow, in a window between 1800 and 2400 GMT. You may want to remove the server from DNS rotation during this period. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Removed from rotation. Let me know when its OK, and I'll add it back. Thanks.
The RAID controller has been replaced. rsync5.us.gentoo.org can get put back in rotation. Thanks, Matt
The current timestamp is several hours behind. Is the cron set up correctly? Times in UTC: Timestamp: Wed, 17 Dec 2003 16:33:00 +0000 Current time: Wed, 17 Dec 2003 23:50:39 +0000
contents of crontab: 0,30 * * * * /opt/gentoo-rsync/rsync-gentoo-portage.sh latest syslog entry: Dec 17 18:00:00 [CRON] (root) CMD (/opt/gentoo-rsync/rsync-gentoo-portage.sh)_ Dec 17 18:00:00 [rsync] re-rsyncing the gentoo-portage tree The last errors in rsync-gentoo-portage.sh.log from early this morning: Started update at Wed Dec 17 01:00:00 CST 2003 io timeout after 600 seconds - exiting rsync error: timeout in data send/receive (code 30) at io.c(103) End: Wed Dec 17 01:12:52 CST 2003 Started update at Wed Dec 17 01:30:00 CST 2003 io timeout after 600 seconds - exiting rsync error: timeout in data send/receive (code 30) at io.c(103) All the rest of the entries are normal since then. Is there something else I should check?
It is looking good now, I'll go ahead and add it back to rotation. You were already put back in to rsync.g.o, I've now added you back to rsync.us.g.o and rsync.namerica.g.o Cheers!
