Mirror seems to be missing syncs, is an hour behind.
Monitoring server, cc'ing contact. Zane, Any information on the server?
I've been out of town for a few days, so sorry for the late response. There was a post to the mirror list about another mirror having the same issue. I do not believe there to be a "problem" with my server yet, but I am monitoring it. The cron has been running, but the sync's may not have finished. Sep 14 23:00:00 fire CRON[26665]: (root) CMD (/opt/gentoo-rsync/rsync-gentoo-portage.sh) Sep 14 23:30:00 fire CRON[16664]: (root) CMD (/opt/gentoo-rsync/rsync-gentoo-portage.sh) Sep 15 00:00:00 fire CRON[29411]: (root) CMD (/opt/gentoo-rsync/rsync-gentoo-portage.sh) Unfortunately through a falt of my own I only have a few minutes of actual rsync log available so I can't prove it as of yet, but I suspect that there will be a few entries such as Nicolai received: >rsync: connection unexpectedly closed (1364547 bytes read so far) >rsync error: error in rsync protocol data stream (code 12) at io.c(165) >rsync: connection unexpectedly closed (1364547 bytes read so far) >rsync error: error in rsync protocol data stream (code 12) at io.c(165) I suppose that I can come up with some kind of modification to the script to keep trying as he did, but while that may work I think it may make the core problem worse. Any thoughts? This all hinges on there not being a problem on my end of course. I'll update this again tomorrow and let you know if I find anything.
Unfortunately its probably a problem on our end. rsync1.us is being overloaded. You could try ofsetting the cron jobs by 1 minute (:01/:31 or :59/:29), but I wouldn't do more than that. We're working on updating/migrating rsync1.us, but that could take several weeks yet. If the 1 minute offset doesn't work, we'll have to temporarily take this mirror offline until we fix rsync1.us.
Well, I offset the cron, and then actually tried to force an update at 21:09 since I saw the last one did not finish. It errored out as well. For what's it's worth I am getting the same entries that I pasted below, in my logs. Taking the mirror temporarily offline would be perfect, as I need to replace a drive in it anyway. I've just been putting it off.
OK, we'll consider this one offline until you get the disk upgraded and we fix rsync1.us' problem. Let us know when you've upgraded the disk, and I'll post back here when we've fixed rsync1.us.
Ok, the disk has been replaced, and that was a nightmare in and of itself. I currently have the cron disabled and rsyncd has been turned off. I noticed a couple people still trying to sync with me, and that's just not good.
The server is still available as rsync17.us, so they have to be specifically referring to it instead of .us, .namerica or rsync.gentoo.
rsync16, not 17. It was under .namerica and rsync.gentoo. Removed now, so once DNS updates, you shouldn't see any more traffic unless they try specific servers.
Just wanted to give a heads up. I haven't done it yet, but in the next couple of days I'll be changing the IP of the rsync mirror. I figured it would be good to let you know now since, I am currently out of the rotation. I'll be switching from 12.96.164.239 to 69.56.171.69. The hostname and all of that will not change, I just haven't updated my DNS as of yet since the move won't happen untill this weekend.
We've fixed rsync1.us' load problem, so that should be OK now. The server seems to be in sync. If you still have the cron sync time offset from :00 and :30, you can switch it back. I can monitor it at any time and add it back to the rotations whenever you are ready. I notice that the old IP is still working.
Ok, I've changed the cron back to 00,30, and you're right, it's still on the old IP. I've had all kinds of crap pop up at work and haven't had a chance to get back to this yet. The ip is up in the air right now. It may still have to change, but for the time being it is going to stay at the current ip. I should have a couple days notice before I have to change any ips, so I want to leave this open for now. If I do have to change it, that will happen within the next week or so most likely.
Looks like it is syncing OK, so I added it back to the .us rotation. The IP change shouldn't be a big issue.
Just checking back to see if the IP change is still a possibility.
Actually, I had just found out last week that I will probably be able to keep the same IP that I have now. If I do have to move it, it will be some time before I even have to think about it. Right now the only thing that is going to effect this machine will be the changing of the hardware. That too is going to take a while to pull off though. I suppose we can go ahead and close this for now. I'll post to the mirror list when I am going to be switching out the machine, but it will be some time before I can afford the dell hardware that I want. Thanks!
Thanks.
