Re: [CentOS-mirror] Flip-Floping contents at msync.centos.org::CentOS-incdvd [ Re: flip-flopping timestamp by pulling CentOS [Re: Wrong timestamp by pulling CentOS-incdvd
On Tue, May 19, 2009 at 07:07:07PM +0900, Takashi Ichihara wrote:
Hi Tru, and CentOS master mirror server Admin.
Hello ,
Our user notified that the contents of Centos 4 at our ftp server ftp.riken.jp is flip-flopping between new one and old one in these few days.
...
A part of the rsync log is shown below.
CentOS.log: 2.1/updates/headers/tzdata-0-2009f-1.el2_1.noarch.hdr CentOS.log.4 :deleting 2.1/updates/headers/tzdata-0-2009f-1.el2_1.noarch.hdr CentOS.log:8 2.1/updates/headers/tzdata-0-2009f-1.el2_1.noarch.hdr CentOS.log.17 :deleting 2.1/updates/headers/tzdata-0-2009f-1.el2_1.noarch.hdr
In the header of the rsync log, the hostname of the machine you are syncing from should appear, could you post them?
the only machine serving dvd and lagging is centosA3.centos.org but it has been removed from the pdns round robin list afaik.
Thanks
Tru
Hi Tru
The host centosa3 still remained at least untill Tue May 19 01:03:02 UTC 2009 and this host seems to be make problem.
Our rsync command (rsync version 3.0.5 protocol version 30) rsync -avzH --delete --exclude=timestamp.txt --exclude=TIME --exclude=".~tmp~/" msync.centos.org::CentOS-incdvd /ftp/Linux/centos
(Log 1) Sun May 17 23:03:01 UTC 2009 msync.CentOS.org rsync service (centosa3) deleting 2.1/updates/headers/tzdata-0-2009f-1.el2_1.noarch.hdr
(Log 3) Tue May 19 01:03:02 UTC 2009 msync.CentOS.org rsync service (centosa3) deleting 2.1/updates/headers/tzdata-0-2009f-1.el2_1.noarch.hdr
(Log 4) Tue May 19 09:15:57 UTC 2009 msync.CentOS.org rsync service (centosb3) 2.1/updates/headers/ 2.1/updates/headers/Canna-0-3.5b2-50.as21.1.i386.hdr : 2.1/updates/headers/tzdata-0-2009f-1.el2_1.noarch.hdr
(I have deleted one log by my mistake)
Regards, Takashi Ichihara
09.5.19 8:00 PM (JST), Tru Huynh wrote,
On Tue, May 19, 2009 at 07:07:07PM +0900, Takashi Ichihara wrote:
Hi Tru, and CentOS master mirror server Admin.
Hello ,
Our user notified that the contents of Centos 4 at our ftp server ftp.riken.jp is flip-flopping between new one and old one in these few days.
...
A part of the rsync log is shown below.
CentOS.log: 2.1/updates/headers/tzdata-0-2009f-1.el2_1.noarch.hdr CentOS.log.4 :deleting 2.1/updates/headers/tzdata-0-2009f-1.el2_1.noarch.hdr CentOS.log:8 2.1/updates/headers/tzdata-0-2009f-1.el2_1.noarch.hdr CentOS.log.17 :deleting 2.1/updates/headers/tzdata-0-2009f-1.el2_1.noarch.hdr
In the header of the rsync log, the hostname of the machine you are syncing from should appear, could you post them?
the only machine serving dvd and lagging is centosA3.centos.org but it has been removed from the pdns round robin list afaik.
Thanks
Tru
On Wed, May 20, 2009 at 12:08:59AM +0900, Ichihara Takashi wrote:
Hi Tru
The host centosa3 still remained at least untill Tue May 19 01:03:02 UTC 2009 and this host seems to be make problem.
... that's weird ...
according to the logs of the pdns backend, I have: 124.217.252.175 <- centosa3.centos.org # 2009/04/06 removing A3 124.217.252.175 (9 days late delaying other mirrors)
a3 being one of the pdns server, it might haven't caught the change and still serving the wrong entry. I am checking this now.
Best regards,
Tru
Hi Tru
Thanks. In the last rsync log in ftp.riken.jp, unfortunately we hit centosa3 again!. As a result, our contents of CentOS became absolute. I killed it and restarted new rsync. (Maybe I will create a simple script to kill rsync when we hit centosa3 ...)
Tue May 19 17:03:01 UTC 2009
msync.CentOS.org rsync service (centosa3) ---------------------------------------
This service is intended for the sole use of the CentOS worldwide mirror network to synchronize mirrors.
Unless you are running or intending to run a listed public CentOS mirror use a mirror listed at http://www.CentOS.org/modules/tinycontent/index.php?id=13
If you intend to populate a mirror for public use please read the notes at :- http://www.CentOS.org/modules/tinycontent/index.php?id=15
If you do use this service then it is implied that you are providing a mirror for public use and giving us authority to publicise such mirror.
receiving incremental file list deleting .rsync.log ./ deleting 2.1/updates/headers/tzdata-0-2009f-1.el2_1.noarch.hdr deleting 2.1/updates/headers/seamonkey-nss-devel-0-1.0.9-0.33.el2.c2.1.i386.hdr deleting 2.1/updates/headers/seamonkey-nss-0-1.0.9-0.33.el2.c2.1.i386.hdr deleting 2.1/updates/headers/seamonkey-nspr-devel-0-1.0.9-0.33.el2.c2.1.i386.hdr deleting 2.1/updates/headers/seamonkey-nspr-0-1.0.9-0.33.el2.c2.1.i386.hdr : 4.7/apt/i386/base/ deleting 4.7/centosplus/x86_64/headers/kernel-xenU-devel-0-2.6.9-78.0.22.plus.c4.x86_64.hdr deleting 4.7/centosplus/x86_64/headers/kernel-xenU-devel-0-2.6.9-78.0.17.plus.c4.x86_64.hdr deleting 4.7/centosplus/x86_64/headers/kernel-xenU-0-2.6.9-78.0.22.plus.c4.x86_64.hdr deleting 4.7/centosplus/x86_64/headers/kernel-xenU-0-2.6.9-78.0.17.plus.c4.x86_64.hdr deleting 4.7/centosplus/x86_64/headers/kernel-smp-devel-0-2.6.9-78.0.22.plus.c4.x86_64.hdr deleting 4.7/centosplus/x86_64/headers/kernel-smp-devel-0-2.6.9-78.0.17.plus.c4.x86_64.hdr deleting 4.7/centosplus/x86_64/headers/kernel-smp-0-2.6.9-78.0.22.plus.c4.x86_64.hdr deleting 4.7/centosplus/x86_64/headers/kernel-smp-0-2.6.9-78.0.17.plus.c4.x86_64.hdr deleting 4.7/centosplus/x86_64/headers/kernel-largesmp-devel-0-2.6.9-78.0.22.plus.c4.x86_64.hdr deleting 4.7/centosplus/x86_64/headers/kernel-largesmp-devel-0-2.6.9-78.0.17.plus.c4.x86_64.hdr deleting 4.7/centosplus/x86_64/headers/kernel-largesmp-0-2.6.9-78.0.22.plus.c4.x86_64.hdr deleting 4.7/centosplus/x86_64/headers/kernel-largesmp-0-2.6.9-78.0.17.plus.c4.x86_64.hdr deleting 4.7/centosplus/x86_64/headers/kernel-doc-0-2.6.9-78.0.22.plus.c4.noarch.hdr deleting 4.7/centosplus/x86_64/headers/kernel-doc-0-2.6.9-78.0.17.plus.c4.noarch.hdr deleting 4.7/centosplus/x86_64/headers/kernel-devel-0-2.6.9-78.0.22.plus.c4.x86_64.hdr deleting 4.7/centosplus/x86_64/headers/kernel-devel-0-2.6.9-78.0.17.plus.c4.x86_64.hdr deleting 4.7/centosplus/x86_64/headers/kernel-0-2.6.9-78.0.22.plus.c4.x86_64.hdr deleting 4.7/centosplus/x86_64/headers/kernel-0-2.6.9-78.0.17.plus.c4.x86_64.hdr 4.7/apt/i386/base/pkglist.centosplus.bz2 :
09.05.20 4:38 AM (UT+9), Tru Huynh wrote,
On Wed, May 20, 2009 at 12:08:59AM +0900, Ichihara Takashi wrote:
Hi Tru
The host centosa3 still remained at least untill Tue May 19 01:03:02 UTC 2009 and this host seems to be make problem.
... that's weird ...
according to the logs of the pdns backend, I have: 124.217.252.175 <- centosa3.centos.org # 2009/04/06 removing A3 124.217.252.175 (9 days late delaying other mirrors)
a3 being one of the pdns server, it might haven't caught the change and still serving the wrong entry. I am checking this now.
Best regards,
Tru
Hi, Tru
After that, we still sometimes hit centosa3 by rsync to msync.centos.org::CentOS-incdvd with the following command:
rsync -avzH --delete-after --exclude=".~tmp~/" msync.centos.org::CentOS-incdvd /ftp/Linux/centos
Since I have created and been running a very simple script to kill rsync when we hit centosa3, now our contents at ftp.riken.jp seems to be keeping always new one.
Or did the lagging contents (Thu Apr 9 08:40:01 UTC 2009) problem of centosa3 fixed already ? Please let us know. Thanks.
==============================================================
Thu May 21 15:10:01 UTC 2009 msync.CentOS.org rsync service (centosa3) ---------------------------------------
This service is intended for the sole use of the CentOS worldwide mirror network to synchronize mirrors.
Unless you are running or intending to run a listed public CentOS mirror use a mirror listed at http://www.CentOS.org/modules/tinycontent/index.php?id=13
If you intend to populate a mirror for public use please read the notes at :- http://www.CentOS.org/modules/tinycontent/index.php?id=15
If you do use this service then it is implied that you are providing a mirror for public use and giving us authority to publicise such mirror.
receiving file list ... ######################################################### Thu May 21 15:11:01 UTC 2009 Upss! We hit centosa3. Rsync will be killed and restarted #########################################################
============================================================
Thu May 21 15:11:02 UTC 2009 msync.CentOS.org rsync service (centosa3) --------------------------------------- : receiving file list ... ######################################################### Thu May 21 15:12:01 UTC 2009 Upss! We hit centosa3. Rsync will be killed and restarted #########################################################
============================================================
Thu May 21 15:12:01 UTC 2009 msync.CentOS.org rsync service (centosa3) --------------------------------------- : receiving file list ... ######################################################### Thu May 21 15:13:01 UTC 2009 Upss! We hit centosa3. Rsync will be killed and restatted #########################################################
============================================================
Thu May 21 15:13:01 UTC 2009 msync.CentOS.org rsync service (centosb3) --------------------------------------- : receiving file list ... done ./ deleting .rsync.log
Regards, Takashi Ichihara
09.5.20 11:25 AM, Takashi Ichihara wrote,
Hi Tru
Thanks. In the last rsync log in ftp.riken.jp, unfortunately we hit centosa3 again!. As a result, our contents of CentOS became obsolute. I killed it and restarted new rsync. (Maybe I will create a simple script to kill rsync when we hit centosa3 ...)
Tue May 19 17:03:01 UTC 2009
msync.CentOS.org rsync service (centosa3)
This service is intended for the sole use of the CentOS worldwide mirror network to synchronize mirrors.
Unless you are running or intending to run a listed public CentOS mirror use a mirror listed at http://www.CentOS.org/modules/tinycontent/index.php?id=13
If you intend to populate a mirror for public use please read the notes at :- http://www.CentOS.org/modules/tinycontent/index.php?id=15
If you do use this service then it is implied that you are providing a mirror for public use and giving us authority to publicise such mirror.
receiving incremental file list deleting .rsync.log ./ deleting 2.1/updates/headers/tzdata-0-2009f-1.el2_1.noarch.hdr deleting 2.1/updates/headers/seamonkey-nss-devel-0-1.0.9-0.33.el2.c2.1.i386.hdr deleting 2.1/updates/headers/seamonkey-nss-0-1.0.9-0.33.el2.c2.1.i386.hdr deleting 2.1/updates/headers/seamonkey-nspr-devel-0-1.0.9-0.33.el2.c2.1.i386.hdr deleting 2.1/updates/headers/seamonkey-nspr-0-1.0.9-0.33.el2.c2.1.i386.hdr : 4.7/apt/i386/base/ deleting 4.7/centosplus/x86_64/headers/kernel-xenU-devel-0-2.6.9-78.0.22.plus.c4.x86_64.hdr deleting 4.7/centosplus/x86_64/headers/kernel-xenU-devel-0-2.6.9-78.0.17.plus.c4.x86_64.hdr deleting 4.7/centosplus/x86_64/headers/kernel-xenU-0-2.6.9-78.0.22.plus.c4.x86_64.hdr deleting 4.7/centosplus/x86_64/headers/kernel-xenU-0-2.6.9-78.0.17.plus.c4.x86_64.hdr deleting 4.7/centosplus/x86_64/headers/kernel-smp-devel-0-2.6.9-78.0.22.plus.c4.x86_64.hdr deleting 4.7/centosplus/x86_64/headers/kernel-smp-devel-0-2.6.9-78.0.17.plus.c4.x86_64.hdr deleting 4.7/centosplus/x86_64/headers/kernel-smp-0-2.6.9-78.0.22.plus.c4.x86_64.hdr deleting 4.7/centosplus/x86_64/headers/kernel-smp-0-2.6.9-78.0.17.plus.c4.x86_64.hdr deleting 4.7/centosplus/x86_64/headers/kernel-largesmp-devel-0-2.6.9-78.0.22.plus.c4.x86_64.hdr deleting 4.7/centosplus/x86_64/headers/kernel-largesmp-devel-0-2.6.9-78.0.17.plus.c4.x86_64.hdr deleting 4.7/centosplus/x86_64/headers/kernel-largesmp-0-2.6.9-78.0.22.plus.c4.x86_64.hdr deleting 4.7/centosplus/x86_64/headers/kernel-largesmp-0-2.6.9-78.0.17.plus.c4.x86_64.hdr deleting 4.7/centosplus/x86_64/headers/kernel-doc-0-2.6.9-78.0.22.plus.c4.noarch.hdr deleting 4.7/centosplus/x86_64/headers/kernel-doc-0-2.6.9-78.0.17.plus.c4.noarch.hdr deleting 4.7/centosplus/x86_64/headers/kernel-devel-0-2.6.9-78.0.22.plus.c4.x86_64.hdr deleting 4.7/centosplus/x86_64/headers/kernel-devel-0-2.6.9-78.0.17.plus.c4.x86_64.hdr deleting 4.7/centosplus/x86_64/headers/kernel-0-2.6.9-78.0.22.plus.c4.x86_64.hdr deleting 4.7/centosplus/x86_64/headers/kernel-0-2.6.9-78.0.17.plus.c4.x86_64.hdr 4.7/apt/i386/base/pkglist.centosplus.bz2 :
09.05.20 4:38 AM (UT+9), Tru Huynh wrote,
On Wed, May 20, 2009 at 12:08:59AM +0900, Ichihara Takashi wrote:
Hi Tru
The host centosa3 still remained at least untill Tue May 19 01:03:02 UTC 2009 and this host seems to be make problem.
... that's weird ...
according to the logs of the pdns backend, I have: 124.217.252.175 <- centosa3.centos.org # 2009/04/06 removing A3 124.217.252.175 (9 days late delaying other mirrors)
a3 being one of the pdns server, it might haven't caught the change and still serving the wrong entry. I am checking this now.
Best regards,
Tru
On Fri, May 22, 2009 at 01:51:58PM +0900, Takashi Ichihara wrote:
Hi, Tru
After that, we still sometimes hit centosa3 by rsync to msync.centos.org::CentOS-incdvd with the following command:
...
I might have found it in the bind zone, could you keep an eye on it and tell us if it's indeed the case? To make sure, I have also killed all rsync/http services on A3.
Sorry for all the inconvenience.
Tru
Hello,
We are currently setting up a new mirror platform.
This platform will exist out of 1 master and 2 nodes
The master will serve all the content to the public, where our 2 nodes will be used to store the data.
There each node will sync its own content, we would like to ask if you can add our node that will host the centos content to the allow list of msync-dvd server.
The hostname/ip of our node that will host centos is, 'mirror-fs01.leaseweb.net' / '94.75.223.123'.
Met vriendelijke groet / With kind regards,
J. Kriegsman Teamleader Support LeaseWeb B.V.
P.O. Box 93054 1090 BB Amsterdam T: +31 203162880 F: +31 203162890 E: j.kriegsman@leaseweb.com http://www.leaseweb.com
-
Ichihara Takashi -
LeaseWeb Mirror Mailing List -
Takashi Ichihara
-
Tru Huynh