We setup a new public mirror in Yogyakarta (Asia/Indonesia):
HTTP: http://mirror.citrahost.com/centos/
Sync schedule: Every 8 hours Bandwidth: 500Mbps Location: Asia/Indonesia Sponsor: PT. Citraweb Digital Multisolusi Sponsor URL: https://citrahost.com IPv4 address to authorize: 202.152.131.133 Email contact: hostmaster@citrahost.com Mirroring AltArch: no
Best Regards
hostmaster@citrahost.com kirjoitti 6.6.2018 klo 6.22:
We setup a new public mirror in Yogyakarta (Asia/Indonesia):
HTTP: http://mirror.citrahost.com/centos/
Sync schedule: Every 8 hours Bandwidth: 500Mbps Location: Asia/Indonesia Sponsor: PT. Citraweb Digital Multisolusi Sponsor URL: https://citrahost.com IPv4 address to authorize: 202.152.131.133 Email contact: hostmaster@citrahost.com Mirroring AltArch: no
Hi, the mirror has now been added and you can now rsync from rsync://msync.centos.org/CentOS/ but I have a few comments.
Looks like the fasttrack repository http://mirror.citrahost.com/centos/7.5.1804/fasttrack/ does not exist on your mirror. It also looks like the directories for the old versions such as 4.9 are not present on your mirror, http://mirror.citrahost.com/centos/4.9/
I hope you are not excluding anything when you rsync. Note that all those directories for old versions (2 through 5.11) are essentially empty, so it does not cost anything to have those directories on your mirror.
On 2018-06-06 13:50, Anssi Johansson wrote:
hostmaster@citrahost.com kirjoitti 6.6.2018 klo 6.22:
We setup a new public mirror in Yogyakarta (Asia/Indonesia):
HTTP: http://mirror.citrahost.com/centos/
Sync schedule: Every 8 hours Bandwidth: 500Mbps Location: Asia/Indonesia Sponsor: PT. Citraweb Digital Multisolusi Sponsor URL: https://citrahost.com IPv4 address to authorize: 202.152.131.133 Email contact: hostmaster@citrahost.com Mirroring AltArch: no
Hi, the mirror has now been added and you can now rsync from rsync://msync.centos.org/CentOS/ but I have a few comments.
Looks like the fasttrack repository http://mirror.citrahost.com/centos/7.5.1804/fasttrack/ does not exist on your mirror. It also looks like the directories for the old versions such as 4.9 are not present on your mirror, http://mirror.citrahost.com/centos/4.9/
I hope you are not excluding anything when you rsync. Note that all those directories for old versions (2 through 5.11) are essentially empty, so it does not cost anything to have those directories on your mirror. _______________________________________________ CentOS-mirror mailing list CentOS-mirror@centos.org https://lists.centos.org/mailman/listinfo/centos-mirror
Thank you for the reply. I do rsync from local repository in Indonesia. Now i will rsync to official mirror from centos for the missing folder. I will update the result after i've done that.
On 2018-06-06 14:25, Hostmaster Citrahost wrote:
On 2018-06-06 13:50, Anssi Johansson wrote:
hostmaster@citrahost.com kirjoitti 6.6.2018 klo 6.22:
We setup a new public mirror in Yogyakarta (Asia/Indonesia):
HTTP: http://mirror.citrahost.com/centos/
Sync schedule: Every 8 hours Bandwidth: 500Mbps Location: Asia/Indonesia Sponsor: PT. Citraweb Digital Multisolusi Sponsor URL: https://citrahost.com IPv4 address to authorize: 202.152.131.133 Email contact: hostmaster@citrahost.com Mirroring AltArch: no
Hi, the mirror has now been added and you can now rsync from rsync://msync.centos.org/CentOS/ but I have a few comments.
Looks like the fasttrack repository http://mirror.citrahost.com/centos/7.5.1804/fasttrack/ does not exist on your mirror. It also looks like the directories for the old versions such as 4.9 are not present on your mirror, http://mirror.citrahost.com/centos/4.9/
I hope you are not excluding anything when you rsync. Note that all those directories for old versions (2 through 5.11) are essentially empty, so it does not cost anything to have those directories on your mirror. _______________________________________________ CentOS-mirror mailing list CentOS-mirror@centos.org https://lists.centos.org/mailman/listinfo/centos-mirror
Thank you for the reply. I do rsync from local repository in Indonesia. Now i will rsync to official mirror from centos for the missing folder. I will update the result after i've done that. _______________________________________________ CentOS-mirror mailing list CentOS-mirror@centos.org https://lists.centos.org/mailman/listinfo/centos-mirror
Hello. I would like to update the result after rsync to rsync://msync.centos.org/CentOS/ For old version has been resolved. Now it's there on the list. For the http://mirror.citrahost.com/centos/7.5.1804/fasttrack, it's now showing. But directory of x86_64/Packages and x86_64/drpms is empty. Is there oke? Thanks before.
Hostmaster Citrahost kirjoitti 6.6.2018 klo 11.51:
Hello. I would like to update the result after rsync to rsync://msync.centos.org/CentOS/ For old version has been resolved. Now it's there on the list. For the http://mirror.citrahost.com/centos/7.5.1804/fasttrack, it's now showing. But directory of x86_64/Packages and x86_64/drpms is empty. Is there oke?
Yes, that's OK, there aren't any 7.5.1804 updates released via fasttrack yet but the missing (blank) repodata files caused problems for the mirror validator. Thanks for fixing.
On 2018-06-06 15:54, Anssi Johansson wrote:
Hostmaster Citrahost kirjoitti 6.6.2018 klo 11.51:
Hello. I would like to update the result after rsync to rsync://msync.centos.org/CentOS/ For old version has been resolved. Now it's there on the list. For the http://mirror.citrahost.com/centos/7.5.1804/fasttrack, it's now showing. But directory of x86_64/Packages and x86_64/drpms is empty. Is there oke?
Yes, that's OK, there aren't any 7.5.1804 updates released via fasttrack yet but the missing (blank) repodata files caused problems for the mirror validator. Thanks for fixing. _______________________________________________ CentOS-mirror mailing list CentOS-mirror@centos.org https://lists.centos.org/mailman/listinfo/centos-mirror
Hello. Thank you for reply. Oke then if there is no error to be fixed in my repository. Hope it will help the other for better use in speed up loading repository data. Once again, i want to know what is the step for repository to be listed on https://centos.org/download/mirrors/ ? Hehehe.
Hostmaster Citrahost kirjoitti 6.6.2018 klo 12.16:
On 2018-06-06 15:54, Anssi Johansson wrote:
Hostmaster Citrahost kirjoitti 6.6.2018 klo 11.51:
Hello. I would like to update the result after rsync to rsync://msync.centos.org/CentOS/ For old version has been resolved. Now it's there on the list. For the http://mirror.citrahost.com/centos/7.5.1804/fasttrack, it's now showing. But directory of x86_64/Packages and x86_64/drpms is empty. Is there oke?
Yes, that's OK, there aren't any 7.5.1804 updates released via fasttrack yet but the missing (blank) repodata files caused problems for the mirror validator. Thanks for fixing. _______________________________________________ CentOS-mirror mailing list CentOS-mirror@centos.org https://lists.centos.org/mailman/listinfo/centos-mirror
Hello. Thank you for reply. Oke then if there is no error to be fixed in my repository. Hope it will help the other for better use in speed up loading repository data. Once again, i want to know what is the step for repository to be listed on https://centos.org/download/mirrors/ ? Hehehe.
The download page lists only up-to-date mirrors, and your mirror was slightly behind when it was added to the database. It seems to be up-to-date now, so the next time our mirror crawler visits your mirror, the mirror will get listed on the download page. This may take a few hours, but it's all automatic from now on.
On 2018-06-06 16:43, Anssi Johansson wrote:
Hostmaster Citrahost kirjoitti 6.6.2018 klo 12.16:
On 2018-06-06 15:54, Anssi Johansson wrote:
Hostmaster Citrahost kirjoitti 6.6.2018 klo 11.51:
Hello. I would like to update the result after rsync to rsync://msync.centos.org/CentOS/ For old version has been resolved. Now it's there on the list. For the http://mirror.citrahost.com/centos/7.5.1804/fasttrack, it's now showing. But directory of x86_64/Packages and x86_64/drpms is empty. Is there oke?
Yes, that's OK, there aren't any 7.5.1804 updates released via fasttrack yet but the missing (blank) repodata files caused problems for the mirror validator. Thanks for fixing. _______________________________________________ CentOS-mirror mailing list CentOS-mirror@centos.org https://lists.centos.org/mailman/listinfo/centos-mirror
Hello. Thank you for reply. Oke then if there is no error to be fixed in my repository. Hope it will help the other for better use in speed up loading repository data. Once again, i want to know what is the step for repository to be listed on https://centos.org/download/mirrors/ ? Hehehe.
The download page lists only up-to-date mirrors, and your mirror was slightly behind when it was added to the database. It seems to be up-to-date now, so the next time our mirror crawler visits your mirror, the mirror will get listed on the download page. This may take a few hours, but it's all automatic from now on. _______________________________________________ CentOS-mirror mailing list CentOS-mirror@centos.org https://lists.centos.org/mailman/listinfo/centos-mirror
Hello. Thank you for reply. Oke then. Thank you for the explanation. ehmm, could you please explain to me about mirror age(daily stats) and last probe(probe stats)? I see http://mirror-status.centos.org/#id at mirror.citrahost.com on column mirror age(daily stats) is set to 2,9 days with red bar and last probe(probe stats) set to 3 hours with green bar. Is there i can do to make this all green? Thanks before.
Hostmaster Citrahost kirjoitti 6.6.2018 klo 12.57:
Hello. Thank you for reply. Oke then. Thank you for the explanation. ehmm, could you please explain to me about mirror age(daily stats) and last probe(probe stats)? I see http://mirror-status.centos.org/#id at mirror.citrahost.com on column mirror age(daily stats) is set to 2,9 days with red bar and last probe(probe stats) set to 3 hours with green bar. Is there i can do to make this all green?
It's fairly simple -- when you viewed that page, the mirror crawler had checked your mirror 3 hours prior to that. At that probe time the mirror's age, as determined by the timestamp files in the root directory, was 2.9 days behind the current time.
As of now, the mirror status page says that the mirror crawler visited your mirror an hour ago, and at that time it was three hours behind the current time. This is less than the limit of 28 hours, and your mirror is now "green" and listed on the download page https://www.centos.org/download/mirrors/
As I said in my previous message, this is all automated but it takes a few hours for the changes to propagate everywhere. Therefore the only way to make your mirror "green" is to make sure it is synced properly and wait a few hours.
On 2018-06-06 18:48, Anssi Johansson wrote:
Hostmaster Citrahost kirjoitti 6.6.2018 klo 12.57:
Hello. Thank you for reply. Oke then. Thank you for the explanation. ehmm, could you please explain to me about mirror age(daily stats) and last probe(probe stats)? I see http://mirror-status.centos.org/#id at mirror.citrahost.com on column mirror age(daily stats) is set to 2,9 days with red bar and last probe(probe stats) set to 3 hours with green bar. Is there i can do to make this all green?
It's fairly simple -- when you viewed that page, the mirror crawler had checked your mirror 3 hours prior to that. At that probe time the mirror's age, as determined by the timestamp files in the root directory, was 2.9 days behind the current time.
As of now, the mirror status page says that the mirror crawler visited your mirror an hour ago, and at that time it was three hours behind the current time. This is less than the limit of 28 hours, and your mirror is now "green" and listed on the download page https://www.centos.org/download/mirrors/
As I said in my previous message, this is all automated but it takes a few hours for the changes to propagate everywhere. Therefore the only way to make your mirror "green" is to make sure it is synced properly and wait a few hours. _______________________________________________ CentOS-mirror mailing list CentOS-mirror@centos.org https://lists.centos.org/mailman/listinfo/centos-mirror
Hello. Thank you for reply. Get it. It's about time to get it green, right? Thanks for the explanation. :)
Hello Admin. Good Day. I have a little question. What happen with file called "timestamp.txt" when i have done rsync to mirror centos? Is it updated automatically or i have to update it manual after doing that rsync? Thanks before.
Hostmaster Citrahost kirjoitti 8.6.2018 klo 6.05:
Hello Admin. Good Day. I have a little question. What happen with file called "timestamp.txt" when i have done rsync to mirror centos? Is it updated automatically or i have to update it manual after doing that rsync?
You should (or rather, MUST) use the timestamp files that you get when rsyncing from msync.centos.org. Updating the timestamp files yourself makes it harder for the mirror validator scripts to determine if your mirror is syncing properly. So, in short, please leave them alone.
On 2018-06-08 12:46, Anssi Johansson wrote:
Hostmaster Citrahost kirjoitti 8.6.2018 klo 6.05:
Hello Admin. Good Day. I have a little question. What happen with file called "timestamp.txt" when i have done rsync to mirror centos? Is it updated automatically or i have to update it manual after doing that rsync?
You should (or rather, MUST) use the timestamp files that you get when rsyncing from msync.centos.org. Updating the timestamp files yourself makes it harder for the mirror validator scripts to determine if your mirror is syncing properly. So, in short, please leave them alone. _______________________________________________ CentOS-mirror mailing list CentOS-mirror@centos.org https://lists.centos.org/mailman/listinfo/centos-mirror
Hello. Thank you for the reply. But what i wondering is i schedule sync at Friday Jun 8 06:00:01 AM GMT+7 2018 Asia/Jakarta and the timestamp.txt showing different time that is Thu Jun 7 22:45:01 UTC 2018 Do i have done something worst that causing this?
Can this please be taken off-list? I don't mean to be rude or disrespectful, however this should be common knowledge for a mirror admin and I'm receiving emails every hour about this same mirror.
CH.
On 8 Jun. 2018 4:58 pm, Hostmaster Citrahost hostmaster@citrahost.com wrote: On 2018-06-08 12:46, Anssi Johansson wrote:
Hostmaster Citrahost kirjoitti 8.6.2018 klo 6.05:
Hello Admin. Good Day. I have a little question. What happen with file called "timestamp.txt" when i have done rsync to mirror centos? Is it updated automatically or i have to update it manual after doing that rsync?
You should (or rather, MUST) use the timestamp files that you get when rsyncing from msync.centos.org. Updating the timestamp files yourself makes it harder for the mirror validator scripts to determine if your mirror is syncing properly. So, in short, please leave them alone. _______________________________________________ CentOS-mirror mailing list CentOS-mirror@centos.org https://lists.centos.org/mailman/listinfo/centos-mirror
Hello. Thank you for the reply. But what i wondering is i schedule sync at Friday Jun 8 06:00:01 AM GMT+7 2018 Asia/Jakarta and the timestamp.txt showing different time that is Thu Jun 7 22:45:01 UTC 2018 Do i have done something worst that causing this?
-- Hostmaster Citrahost A Web Hosting Solution from PT. Citraweb Digital Multisolusi Yogyakarta - Indonesia _______________________________________________ CentOS-mirror mailing list CentOS-mirror@centos.org https://lists.centos.org/mailman/listinfo/centos-mirror
On 2018-06-08 14:03, Christopher Hawker wrote:
Can this please be taken off-list? I don't mean to be rude or disrespectful, however this should be common knowledge for a mirror admin and I'm receiving emails every hour about this same mirror.
CH.
On 8 Jun. 2018 4:58 pm, Hostmaster Citrahost hostmaster@citrahost.com wrote:
On 2018-06-08 12:46, Anssi Johansson wrote:
Hostmaster Citrahost kirjoitti 8.6.2018 klo 6.05:
Hello Admin. Good Day. I have a little question. What happen with file called "timestamp.txt" when i have done rsync
to
mirror centos? Is it updated automatically or i have to update it manual after
doing
that rsync?
You should (or rather, MUST) use the timestamp files that you get
when
rsyncing from msync.centos.org. Updating the timestamp files
yourself
makes it harder for the mirror validator scripts to determine if
your
mirror is syncing properly. So, in short, please leave them alone. _______________________________________________ CentOS-mirror mailing list CentOS-mirror@centos.org https://lists.centos.org/mailman/listinfo/centos-mirror
Hello. Thank you for the reply. But what i wondering is i schedule sync at Friday Jun 8 06:00:01 AM GMT+7 2018 Asia/Jakarta and the timestamp.txt showing different time that is Thu Jun 7 22:45:01 UTC 2018 Do i have done something worst that causing this?
-- Hostmaster Citrahost A Web Hosting Solution from PT. Citraweb Digital Multisolusi Yogyakarta - Indonesia _______________________________________________ CentOS-mirror mailing list CentOS-mirror@centos.org https://lists.centos.org/mailman/listinfo/centos-mirror _______________________________________________ CentOS-mirror mailing list CentOS-mirror@centos.org https://lists.centos.org/mailman/listinfo/centos-mirror
No, don't sir. I have done fix this at this time.
On Fri, Jun 08, 2018 at 07:03:15AM +0000, Christopher Hawker wrote:
Can this please be taken off-list? I don't mean to be rude or disrespectful, however this should be common knowledge for a mirror admin and I'm receiving emails every hour about this same mirror.
Please do not top-post to the CentOS lists and please trim replies.
People have to learn somehow and this seems as good of a venue as anywhere else. Not everyone is an instant expert when doing new things. Please cut this person a bit of slack.
John
Hostmaster Citrahost kirjoitti 8.6.2018 klo 9.57:
But what i wondering is i schedule sync at Friday Jun 8 06:00:01 AM GMT+7 2018 Asia/Jakarta and the timestamp.txt showing different time that is Thu Jun 7 22:45:01 UTC 2018 Do i have done something worst that causing this?
Well, first of all, there is a 7 hour timezone difference between GMT+7 Asia/Jakarta and UTC. That explains most of the difference.
timestamp.txt represents the version of the files that you retrieved from the master servers (msync.centos.org), and this is what matters when determining if the mirror is up to date. It does not represent the time when you synced from msync.centos.org. timestamp.txt gets updated on msync.centos.org frequently, I think every 10 minutes or so. The timestamp.txt that you get from msync.centos.org may be slightly behind your current time (typically less than half an hour), but that is normal.
As long as your mirror's entry on http://mirror-status.centos.org/#id is green you're OK. The maximum allowed age is 28 hours, and you are nowhere near that. If you sync every 8 hours, your mirror's age is likely to always be under 8 hours, which is absolutely fine.
Relax, it's all OK now, so you can just sit back and enjoy the traffic :)
It updates automatically.
On 8 Jun. 2018 1:06 pm, Hostmaster Citrahost hostmaster@citrahost.com wrote: Hello Admin. Good Day. I have a little question. What happen with file called "timestamp.txt" when i have done rsync to mirror centos? Is it updated automatically or i have to update it manual after doing that rsync? Thanks before.
-- Hostmaster Citrahost A Web Hosting Solution from PT. Citraweb Digital Multisolusi Yogyakarta - Indonesia _______________________________________________ CentOS-mirror mailing list CentOS-mirror@centos.org https://lists.centos.org/mailman/listinfo/centos-mirror