Gentoo Archives: gentoo-mirrors

From: Llarian <llarian@×××××××.net>
To: gentoo-mirrors@l.g.o
Subject: Re: [gentoo-mirrors] Gentoo rsync mirror alert RFC
Date: Tue, 14 Feb 2006 22:43:52
Message-Id: Pine.LNX.4.64.0602141442540.31681@llarian.net
In Reply to: [gentoo-mirrors] Gentoo rsync mirror alert RFC by Jeffrey Forman
1 LKAMS has been pretty good with sending these out daily to the admins of
2 the servers with issues. This obviously fails when there's no admin
3 contact, but it seems like a good SOP.
4
5 -Dylan Vanderhoof
6
7 On Tue, 14 Feb 2006, Jeffrey Forman wrote:
8
9 > Hello once again Gentoo mirror admins,
10 >
11 > Your friendly gentoo infrastructure monkey. I have finally finished a
12 > work I started many weeks ago and wanted to gague your interest in it.
13 > It is related to the automated rsync mirror checker running at
14 > http://mirrorstats.gentoo.org/rsync/
15 >
16 > The script can now send out alerts as forwarded below.
17 >
18 > Currently the report tallies "bad" mirrors in one of three conditions:
19 > 1. no response, yet in a dns rotation
20 > 2. responds, but no timestamp
21 > 3. responds, but is over 1 hour old.
22 >
23 > I'd like to get your opinions on how often you would like this sent out
24 > to the list, or if you would rather it sent out to individual admins?
25 > (To send it out to individual admins would require a bit of retooling on
26 > my part, but still possible.) Every few hours, once a day, once a week,
27 > etc? Because it is an rsync mirror check, a longer time frame, in my
28 > opinion, becomes less timely, as opposed to sending it out once a day.
29 >
30 > Comments, queries, etc welcome.
31 >
32 > -Jeffrey
33 >
34 > -------- Forwarded Message --------
35 >> From: Gentoo Mirror Admins <mirror-admin@g.o>
36 >> To: jforman@g.o
37 >> Subject: Rsync new test
38 >> Date: Tue, 14 Feb 2006 14:31:07 -0800 (PST)
39 >>
40 >> Gentoo RSYNC Mirror Report
41 >> These mirrors were found to have issues outstanding.
42 >>
43 >> Timestamp: Tue, 14 Feb 2006 22:30:39 +0000
44 >>
45 >>
46 >> 130.89.175.34 no admin contact timestamp missing
47 >> 147.83.91.30 Fracesc Genove no response
48 >> 193.4.195.6 Johann Helgi no response
49 >> 194.185.88.30 Mino Bernardi no response
50 >> 196.25.230.147 no admin contact no response
51 >> 203.17.15.14 no admin contact no response
52 >> 210.224.164.100 no admin contact timestamp missing
53 >> 210.59.107.10 Ming-Han Liu no response
54 >> 211.58.255.224 no admin contact timestamp missing
55 >> 213.204.195.9 no admin contact 0d 1h 10m
56 >> rsync.asia.gentoo.or no admin contact timestamp missing
57 >> rsync1.es.gentoo.org timestamp missing
58 >> rsync1.no Benjamin Leitet timestamp missing
59 >> rsync1.pl Marcin Jurczuk 0d 3h 10m
60 >> rsync1.ru Andrew B. Panphiloff 0d 1h 10m
61 >> rsync1.th Ott Pattara timestamp missing
62 >> rsync1.tw Chou Yeh-Jyi 0d 1h 10m
63 >> rsync1.uk Tim Haynes 0d 1h 40m
64 >> rsync1.uk Tim Haynes timestamp missing
65 >> rsync10.de Patrick Kursawe 0d 1h 10m
66 >> rsync2.fr Ludovic Bellier 0d 1h 10m
67 >> rsync2.jp MATSUDA Kazuo 0d 1h 10m
68 >> rsync2.pl Jaroslaw Swierad 0d 1h 40m
69 >> rsync2.tw Benny Chang timestamp missing
70 >> rsync3.be 0d 1h 10m
71 >> rsync3.pl Krzysztof Raczkowski 0d 5h 40m
72 >> rsync4.nl Renald Buter timestamp missing
73 >>
74 >>
75 >> This report and script created by Jeffrey Forman
76 >> Please /join #gentoo-mirrors on irc.freenode.org if you have further concerns.
77 >> Thanks for your continued support of Gentoo Linux.
78 >>
79 >
80 --
81 gentoo-mirrors@g.o mailing list