rsync server. (if this is double post of server i'm sorry.) 5 user max; fast connection.
I've added 130.237.152.204 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 and then add it to the rotation. Also, I'd like to verify a few details. Is the server running ntp? What is the upstream connection? Also, the CPU and RAM. Thanks.
Thanks, will start monitoring the server. From: Henrik Holst <henrik_holst@home.se> To: pjp@gentoo.org Subject: Re: [Bug 21711] new rsync server. news.sigma.su.se I noticed that my network administrator had blocked the rsync (and more) ports on my machine so that rsync did not work. It's fixed now. I also increased the number of simultaneous connections to the (new) minimum of 10. -- Henrik Holst <henrik_holst@home.se>
I had some connectivity issues during June and most of July. I'm monitoring the server again.
There seem to be some pretty major syncing problems. I started with Wed, 06 Aug 2003 04:03:00 +0000 (times in date -uR format), which was fine. After that, there were a couple more missed syncs, then they seem to have stopped, with Wed, 06 Aug 2003 11:03:00 +0000 being the last good sync. Now, the server seems to be refusing connections. Can you see if there are any errors on your end? Thanks
As far as I know, mail can't be sent directly to the bugzilla-daemon. Posting replies directly to the bugzilla web page is the most helpful to us for tracking purposes. I'll start monitoring the server again. Henrik Holst <henrik_holst@home.se> wrote: >Tried to send this but only get it back from "reply" address. >Here it comes (again) > >-----Forwarded Message----- > >> From: Henrik Holst <henrik_holst@home.se> >> To: bugzilla-daemon@wwwjr.cws.oregonstate.edu >> Subject: Re: [Bug 21711] new rsync server. news.sigma.su.se >> Date: 08 Aug 2003 20:05:49 +0200 >> >> Hi! >> >> There seems to have occurred some kind of strange error with the rsync >> daemon. (restarted server and now works OK). What was very strange was >> that emerge rsync worked (!) against localhost - but not from the >> Internet host (news.sigma.su.se) - weird... >> >> <errorlog> >> >> bash-2.05b# SYNC=rsync://news.sigma.su.se/gentoo-portage/ emerge sync >> >>> starting rsync with rsync://news.sigma.su.se/gentoo-portage/... >> ------------------------------------------------------------------ >> This is [ rsync ... ] >> >> * name {rsync,news}.sigma.su.se >> * ip 130.237.152.204 >> * location stockholm / sweden >> * contact *person* holst at sigma.su.se >> >> ------------------------------------------------------------------ >> >> rsync: connection unexpectedly closed (348 bytes read so far) >> rsync error: error in rsync protocol data stream (code 12) at io.c(165) >> >> >> >>> Starting retry 1 of 3 >> Killed >> >> </errorlog> >> >> Sorry for the inconvenience. >> >> Sincerely, >> Henrik Holst
The server was syncing fine from Wed 13th (date -uR format). Recently though, a couple of syncs have missed. Can you see if there are any errors on your end? Checked (UTC) Timestamp ================================================ 23:20:11 Wed, 13 Aug 2003 23:02:00 +0000 (good) ... 22:20:08 Fri, 15 Aug 2003 21:32:00 +0000 (expected 22:00) 10:20:07 Sat, 16 Aug 2003 09:32:00 +0000 (expected 10:00) 19:20:07 Sat, 16 Aug 2003 18:32:00 +0000 (expected 19:00)
I looked in the /opt/gentoo-rsync/rsync-gentoo-portage.sh.log after some error but could not find anything that would point to a 20 minute delay. Here is the grep:ed log: http://news.sigma.su.se/rsync.16aug.txt The only thing I can think of is that the ntp server I'm sync:ing against (NTPDATE_OPTS="-b ntp1.su.se") is faulty sometimes(?) - as the time is 100% correct now. (17 aug. 23:37 local time) If the problems continue I'm afraid that I have run out of ideas what can be wrong... maybe the machine is in need of a good old "uptime reset"? :)
The rsync server logs look good for the past 24 hours. I've added this rsync mirror to the monitoring page at http://monitor.gentoo.org/mirmon/rsync_index.html under the "testing, probationary, or experimental" section. Will watch it here for the next 24 hours and then you should be good to go. Thanks for your patience and willingness to help out!
Wrong IP detected for RSYNC server!!! News.sigma.su.se = 130.237.152.204 nslookup rsync.gentoo.org -sil | grep 130.237.152.20 Server: 130.237.152.207 Address: 130.237.152.207#53 Do you see the problem? :)
Sorry. My misstake. That was the ip of the nameserver in use. I did a nslookup at home and there I use another nameserver. (nslookup does not return any ip related to news.sigma.su.se then when filtered trough grep as show in previous "bug" post.) Sorry for excessive lameness :-)
I think the problem may be related to rsync1.us being overworked. We're working on removing some load from the server, but that is still a ways off yet. Once we make some progress with that, I'll post back here to indicate we're ready to start testing again. Unless of course someone figures out that its a different problem.
We've resolved the problem with rsync1.us. Timestamp looks good, will monitor again and post back in a couple of days.
The syncs are looking good except for one minor consistant miss. The midnight (UTC) sync isn't working. Do you have something else running at that time that could be causing a problem?
/usr/sbin/gentoo-stats --update Runs every midnight at 00:00 (UTC) Moved to 00:10 doing a "emerge -uD world" to catch up on some packages so may be a bit of a day or so from now.
This server is now rsync4.se.gentoo.org. Please update the motd file to include that information. I've subscribed <henrik_holst@home.se> to our gentoo-mirrors mailing list (low volume). This list is used to discuss mirror-related issues. Thanks for supporting Gentoo Linux.
