On 1/27/08, Gerhard Brauer wrote:

Gruesse! * eliott schrieb am [27.01.08 23:22]:

...

On 1/27/08, Gerhard Brauer wrote:

...

So is there a server (ftp or http) from where i could get the mtime, size and the repository db file as a reference?

no. there is not a publicly accessible location of the repo db file other than mirror servers. ftp.archlinux.org is the best candidate. the two servers (round robin dns for ftp.archlinux.org) synchronize approximately every hour.

Thank you. Then i must see if there are realy so many mirrors out of sync or if i have beasty little things in my script ;-) Maybe something with the UTC times on the mirrors...

could be. When viewing with command line ftp i get.. ftp> modtime core.db.tar.gz core.db.tar.gz 01/27/2008 22:03:55 GMT apache shows me the following when viewing in firefox File: core.db.tar.gz 24 KB 27/01/08 10:03:00 PM So while the ftp says "GMT", it is really PST, as the times are very close, and it is clearly within the 10PM house where I am (PST timezone). Not sure why the time is being reported as GMT in ftp.

On 1/28/08, Gerhard Brauer wrote:

Hello!

Ok, i'am 99% ready with the script (mostly output and "internally cleaning"). I put the output as txt attachement in this mail.

Short: Overall Status -------------------------------------- Mirrors tested..................... : 49 Mirrors with connection problems... : 2 Mirror with data collection problems: 5

Mirrors OUT of sync................ : 25

Legend for txt file: size means *.db.tar.gz size reported by either FTP or HTTP mirror mtime also taken from protocols, converted to UTC if needed md5sum after doenlaod db file.

Some mirrors seams to have the correct file size, but mtime and/or md5sum differs. I've checked some of them and there seams to bee slightly corrupted files on there.

Next i will version pumping on the script (it's a ruby script) from now 0.1 to 1.0 ;-) and then we could see if this is something usefull for us.

I think it would be a very nice thing to have someone run periodically, and maybe send reports to the dev team...so that we can know which mirrors are not syncing properly. As of right now, we mostly have to rely on end user reports of problems (reactive instead of proactive).

On 1/28/08, Gerhard Brauer wrote:

Hello! * eliott schrieb am [28.01.08 17:19]:

...

I think it would be a very nice thing to have someone run periodically, and maybe send reports to the dev team

I think we on archlinux.de could do this. I'll talk with Pierre next time about that.

Another question , i assume that that you could say "something about mirroring": I also talked with Pierre about some more mirrors for germany. I have a list with some potential candidates. Our question is: what is the right way to get them as ArchLinux mirrors? We could contact their ftpmaster, but when they say: yes, we've waited for you ;-) whom must i/we contact on archlinux.org for rsync and so far?

The best course of action is probably to: 1) Contact the mirror admin, requesting mirroring. 2a) If they want to mirror from the arch main server: Open a bug ticket. This way the pacman packager, as well as the arch server admin, can both have a reference point for addition of the new mirror. Include relevant text, contact information, etc in the bug ticket. 2b) Alternately, some of the servers that already mirror have rsync access, and new mirrors could be "teir2" by syncing off of them. In such cases, make sure to qualify in the bug ticket such information, as well as any additional relevant text, contact information, etc.

Is there a "FAQ" or some document anywhere?

Not yet.