Hello, It looks like your mirror has been inaccessible to us for about 25 days. When trying to connect to your rsync mirror I get a connection refused. Could you please check on your end and ensure everything is up and running? Thanks, Mark
Can you show me some more information? What host/ip do you connect from, what message do you get?
xinetd seems to randomly drop services. It should be working now. We also installed monitoring on the services. Thanks for reporting. Unfortunately I cannot change the status at this point. I can only leave it as new.
I'm unable to connect again: rsync rsync2.nl.gentoo.org::gentoo-portage/metadata/timestamp.chk . rsync: failed to connect to rsync2.nl.gentoo.org: Connection refused (111)
Argh, you're right. It seems that sometimes it refuses the connection, and without any fixing it starts working after a while. Will investigate. Maybe you can check if rsync://ftp.snt.utwente.nl/ has the same problem? It's the same machine, but different IP.
Both are accessible now. I'm going to leave this open as a reminder to keep checking it for the next few days.
It appears I have some notorious rsyncers (up to 200 times a day), which occasionally causes xinetd to loose a service. I'm going to block (and email) these people and see if the situation improves. Monitoring is working properly now, so downtime should not be too long.
Roel, Looks like you went down again. http://mirrorstats.gentoo.org/rsync/#nl rsync: failed to connect to rsync2.nl.gentoo.org: Connection refused (111)
I noticed: every hour, on the hour, I check if it's available. I do not have root access, so I have to ask people to restart xinetd. On the problem: It appears xinetd bugs when it applies limiting (rate/cpu). I will do my best to get rsync out of xinetd or otherwise fix the problem. Getting fed up with this :)
I haven't noticed any problems in the past few days. I'm going to close it for now. Thanks for your help in tracking down the issue and addressing it. Thanks, Mark
Sometimes the service still fails, but proper monitoring is in place now. We can restart it within a few hours. Thanks for noticing!
It looks like its been down for about 3 hours again.
The xinetd limiting has been disabled, so it should not trigger the bug anymore.
Cool. Thanks for the response. It looks like things have been alright for awhile too, so I'm going to close this bug. Thanks, Mark
I will announce this separately, but for completeness I'm mentioning it in this bug too: There is scheduled downtime at 16th of April and 23rd of April from 19:00 local time. Expected downtime is going to be a few hours. The university is shutting down the power in the serverroom we're at. > Cool. Thanks for the response. It looks like things have been alright for > awhile too, so I'm going to close this bug. > > Thanks, > > Mark >
