Hello,
We've been operating an altarch mirror for some time, as our organisation is heavily dependent on armfp flavour. I noticed the rsync is failing, so I looked around for problems. I see it fails with "Unknown module" error. I see the mirror has also been dropped from the official altarch mirror list. I surmise then that the IP is blcocked from CentOS mirror. I don't know if it was blocked because our rsync was failing, or some other issue.
In any case, I hereby request reinclusion, and I'm currently rsyncing from a Hong Kong mirror. If there is some other reason our mirror cannot be included, please do let me know and I'll try to address it, or if I cannot address it, I'll stop writing to the list and disturbing you.
Note: For operational reasons, we route our rsync requests via one of our Singapore IPs.
Mirror: altarch.centos.shaw.co.th Update IP for whitelisting: 139.99.44.244
Warmest regards,
Patrick
On 28/11/2019 14:49, Patrick Shaw wrote:
Hello,
We've been operating an altarch mirror for some time, as our organisation is heavily dependent on armfp flavour. I noticed the rsync is failing, so I looked around for problems. I see it fails with "Unknown module" error. I see the mirror has also been dropped from the official altarch mirror list. I surmise then that the IP is blcocked from CentOS mirror. I don't know if it was blocked because our rsync was failing, or some other issue.
In any case, I hereby request reinclusion, and I'm currently rsyncing from a Hong Kong mirror. If there is some other reason our mirror cannot be included, please do let me know and I'll try to address it, or if I cannot address it, I'll stop writing to the list and disturbing you.
Note: For operational reasons, we route our rsync requests via one of our Singapore IPs.
Mirror: altarch.centos.shaw.co.th Update IP for whitelisting: 139.99.44.244
Warmest regards,
Patrick
Hi, I just had a quick look and can't see any mirror in our DB for that hostname, nor any official request for it in the list archives, so can you just submit a proper request (following the template from https://wiki.centos.org/HowTos/CreatePublicMirrors) and you'll request will be processed.
Kind Regards,
Hi,
Possibly you can't see any request because we only provide AltArch mirror. It was agreed that this should be the case until we are able to provide more bandwidth for main mirror, because we are so dependent on AltArch yet there is no mirror in Thailand. It's no use me complaining about that unless I do something about it, so, here is my AltArch mirror. . .
altarch.centos.shaw.co.th
Sync schedule: Every 8 hrs Bandwidth: 100Mbps Location: Chiang Rai, Thailand Sponsor: Shaw IT Sponsor URL: www.shaw.co.th IPv4 address to authorize: 139.99.44.244 (note that this is a Singapore IP. We route our update request via Singapore to improve international bandwidth performance) IPv6 address to authorize: - Email contact: patrick@shaw.co.th Mirroring AltArch: Yes
Warm regards,
Patrick
On 2/12/62 16:30, Fabian Arrotin wrote:
On 28/11/2019 14:49, Patrick Shaw wrote:
Hello,
We've been operating an altarch mirror for some time, as our organisation is heavily dependent on armfp flavour. I noticed the rsync is failing, so I looked around for problems. I see it fails with "Unknown module" error. I see the mirror has also been dropped from the official altarch mirror list. I surmise then that the IP is blcocked from CentOS mirror. I don't know if it was blocked because our rsync was failing, or some other issue.
In any case, I hereby request reinclusion, and I'm currently rsyncing from a Hong Kong mirror. If there is some other reason our mirror cannot be included, please do let me know and I'll try to address it, or if I cannot address it, I'll stop writing to the list and disturbing you.
Note: For operational reasons, we route our rsync requests via one of our Singapore IPs.
Mirror: altarch.centos.shaw.co.th Update IP for whitelisting: 139.99.44.244
Warmest regards,
Patrick
Hi, I just had a quick look and can't see any mirror in our DB for that hostname, nor any official request for it in the list archives, so can you just submit a proper request (following the template from https://wiki.centos.org/HowTos/CreatePublicMirrors) and you'll request will be processed.
Kind Regards,
CentOS-mirror mailing list CentOS-mirror@centos.org https://lists.centos.org/mailman/listinfo/centos-mirror
Hi,
In the absence of any response I think we'll just return this to being a firewalled private mirror for our own uses. It's no skin of my nose, but I do however feel compelled to say that I find it pretty impolite to remove our mirror and blacklist our IP with no form of communication or reason.
I also note than a number of Thailand based mirrors have been removed, not only ours, from the mirror list, yet they still appear to be online and working. There must be some reason for this. Just asking.
Kind regards,
Patrick
On 8/12/62 12:00, Patrick Shaw wrote:
Hi,
Possibly you can't see any request because we only provide AltArch mirror. It was agreed that this should be the case until we are able to provide more bandwidth for main mirror, because we are so dependent on AltArch yet there is no mirror in Thailand. It's no use me complaining about that unless I do something about it, so, here is my AltArch mirror. . .
altarch.centos.shaw.co.th
Sync schedule: Every 8 hrs Bandwidth: 100Mbps Location: Chiang Rai, Thailand Sponsor: Shaw IT Sponsor URL: www.shaw.co.th IPv4 address to authorize: 139.99.44.244 (note that this is a Singapore IP. We route our update request via Singapore to improve international bandwidth performance) IPv6 address to authorize: - Email contact: patrick@shaw.co.th Mirroring AltArch: Yes
Warm regards,
Patrick
On 2/12/62 16:30, Fabian Arrotin wrote:
On 28/11/2019 14:49, Patrick Shaw wrote:
Hello,
We've been operating an altarch mirror for some time, as our organisation is heavily dependent on armfp flavour. I noticed the rsync is failing, so I looked around for problems. I see it fails with "Unknown module" error. I see the mirror has also been dropped from the official altarch mirror list. I surmise then that the IP is blcocked from CentOS mirror. I don't know if it was blocked because our rsync was failing, or some other issue.
In any case, I hereby request reinclusion, and I'm currently rsyncing from a Hong Kong mirror. If there is some other reason our mirror cannot be included, please do let me know and I'll try to address it, or if I cannot address it, I'll stop writing to the list and disturbing you.
Note: For operational reasons, we route our rsync requests via one of our Singapore IPs.
Mirror: altarch.centos.shaw.co.th Update IP for whitelisting: 139.99.44.244
Warmest regards,
Patrick
Hi, I just had a quick look and can't see any mirror in our DB for that hostname, nor any official request for it in the list archives, so can you just submit a proper request (following the template from https://wiki.centos.org/HowTos/CreatePublicMirrors) and you'll request will be processed.
Kind Regards,
CentOS-mirror mailing list CentOS-mirror@centos.org https://lists.centos.org/mailman/listinfo/centos-mirror
On 16/12/2019 10:30, Patrick Shaw wrote:
Hi,
In the absence of any response I think we'll just return this to being a firewalled private mirror for our own uses. It's no skin of my nose, but I do however feel compelled to say that I find it pretty impolite to remove our mirror and blacklist our IP with no form of communication or reason.
I also note than a number of Thailand based mirrors have been removed, not only ours, from the mirror list, yet they still appear to be online and working. There must be some reason for this. Just asking.
Kind regards,
Patrick
Hi Patrick,
Probably missing the whole context, but as said I don't see your mirror referenced anywhere in our DB before, and can't find any mail on this mailing-list archive either (happy to be proved wrong)
There is no problem being a private mirror either, but then of course not allowed in the ACL. All altarch mirrors are *also* public mirrors (so the way current mirror crawler consider a node current is by checking first the normal mirror content *and* only then altarch *if* flagged as altarch mirror too)
So if you can/want to be official centos mirror for all, that can happen :)
Also, the "impolite" sentence sounds rude, considering that mirror was never in our DB it seems
Hi,
If I may be so bold, and without ill intent, there seems to be some issue with your database management. I have included here a link to an Archive page including our historic listing. . . https://web.archive.org/web/20190816172658/https://www.centos.org/download/a...
Checking through my personal email archives, the original notification of our public mirror being online was on the 8th of March this year. However, it appears to have been deleted from the CentOS mailing list. Either there is an error, or someone over there seems to have a stick in their craw for Thailand mirrors.
Patrick
On 16/12/62 16:38, Fabian Arrotin wrote:
On 16/12/2019 10:30, Patrick Shaw wrote:
Hi,
In the absence of any response I think we'll just return this to being a firewalled private mirror for our own uses. It's no skin of my nose, but I do however feel compelled to say that I find it pretty impolite to remove our mirror and blacklist our IP with no form of communication or reason.
I also note than a number of Thailand based mirrors have been removed, not only ours, from the mirror list, yet they still appear to be online and working. There must be some reason for this. Just asking.
Kind regards,
Patrick
Hi Patrick,
Probably missing the whole context, but as said I don't see your mirror referenced anywhere in our DB before, and can't find any mail on this mailing-list archive either (happy to be proved wrong)
There is no problem being a private mirror either, but then of course not allowed in the ACL. All altarch mirrors are *also* public mirrors (so the way current mirror crawler consider a node current is by checking first the normal mirror content *and* only then altarch *if* flagged as altarch mirror too)
So if you can/want to be official centos mirror for all, that can happen :)
Also, the "impolite" sentence sounds rude, considering that mirror was never in our DB it seems
CentOS-mirror mailing list CentOS-mirror@centos.org https://lists.centos.org/mailman/listinfo/centos-mirror
On 16/12/2019 10:50, Patrick Shaw wrote:
Hi,
If I may be so bold, and without ill intent, there seems to be some issue with your database management. I have included here a link to an Archive page including our historic listing. . . https://web.archive.org/web/20190816172658/https://www.centos.org/download/a...
Checking through my personal email archives, the original notification of our public mirror being online was on the 8th of March this year. However, it appears to have been deleted from the CentOS mailing list. Either there is an error, or someone over there seems to have a stick in their craw for Thailand mirrors.
Patrick
Let's not dive into politics or false assumptions like you do. We don't have anything against Thailand mirrors, and I even added a new msync node there to speed things up , so to let external mirrors in that region to get faster updates through rsync with a local msync node in Thailand :)
Let's so not spend too much time to "who's right, etc .." but I looked in my mail archives (receiving all mail sent through lists.centos.org) and the only thing I can see is what I can see on https://lists.centos.org/pipermail/centos-mirror/2019-March/011534.html
So it was about another Thailand mirror, that Anssi added.
FWIW, Anssi decided to leave the project, but it can be that you had exchanged mails with him directly and so while having the [CentOS-mirror] tag, conversation went private ?
Anyway, to cut a long story short : if you can be a public mirror for all content, happy to add your mirror (for all) once asked and validated :-)
Kind Regards,