Hi Anssi,
Thank you for the advice. I have removed "createrepo", added -H option, and switched to "msync.centos.org::CentOS" and done resync.
Here is the output: [root@mirror cron]# stat /xxxxx/centos/7.5.1804/os/x86_64/images/boot.iso File: '/xxxxx/centos/7.5.1804/os/x86_64/images/boot.iso' Size: 519045120 Blocks: 1013768 IO Block: 4096 regular file Device: fd06h/64774d Inode: 9176964 Links: 2 Access: (0644/-rw-r--r--) Uid: ( 1005/ UNKNOWN) Gid: ( 1005/ UNKNOWN) Access: 2018-11-12 08:12:36.728685156 +0700 Modify: 2018-05-04 03:34:18.000000000 +0700 Change: 2018-11-19 23:38:02.011071968 +0700 Birth: - [root@mirror cron]# stat /xxxxx/centos/7.5.1804/isos/x86_64/CentOS-7-x86_64-NetInstall-1804.iso File: '/xxxxx/centos/7.5.1804/isos/x86_64/CentOS-7-x86_64-NetInstall-1804.iso' Size: 519045120 Blocks: 1013768 IO Block: 4096 regular file Device: fd06h/64774d Inode: 9176964 Links: 2 Access: (0644/-rw-r--r--) Uid: ( 1005/ UNKNOWN) Gid: ( 1005/ UNKNOWN) Access: 2018-11-12 08:12:36.728685156 +0700 Modify: 2018-05-04 03:34:18.000000000 +0700 Change: 2018-11-19 23:38:02.011071968 +0700 Birth: -
Hopefully everything is alright now. Thanks.
On 2018-11-19 21:00, Anssi Johansson wrote:
OK, thanks for information. I need to comment on that blog posting that people must not use "createrepo" to generate the repodata. All the repodata files come from msync.centos.org. If some mirror admin creates their own repodata, it will break the GPG signing of repomd.xml (see repomd.xml.asc). You can "yum remove createrepo" if you had installed it only for this purpose.
Additionally, public mirrors should sync their content with only one rsync command (again, without excluding anything) and not separately for each version or repository.
Your rsync seems to be accessible now and there are repodata files as well, so I've now added your mirror to the list. You can now switch to rsyncing from rsync://msync.centos.org/CentOS/
But there's one more issue that needs to be fixed: You don't seem to be using the -H option to rsync that would preserve hard links. This will be important when 7.6.1810 gets released, because the packages you already have in the 7.5.1804/cr repository are the same ones that will end up to 7.6.1810/os. If you don't have that -H option in your rsync command line, you will need to transfer those packages again, instead of rsync simply linking them together. All you need to do is to add the -H flag to your rsync command line, and the situation will be fixed the next time you sync. You can check this afterwards by running "stat /path/to/mirror/centos/7.5.1804/os/x86_64/images/boot.iso". There should be "Links: 2" in the output. The other instance of that file is at centos/7.5.1804/isos/x86_64/CentOS-7-x86_64-NetInstall-1804.iso
The -H flag is mentioned on https://wiki.centos.org/HowTos/CreatePublicMirrors but sadly not on the blog page you linked to.
centos@buana.net kirjoitti 19.11.2018 klo 14.04:
Hi,
I followed steps from http://blog.programster.org/centos-7-create-centos-7-mirror Anyway, as per your guidance, I included repo* now and do resync again.
for your rsync problem, can you try to temporarily disable your firewall?
regards, CB
On 2018-11-19 15:30, Anssi Johansson wrote:
Hmm, there are still missing files. For example, I don't see any "repodata" directories on your mirror, whereas those directories are present in rsync://centos.mirror.angkasa.id/centos/ which I mentioned as a possible source for your initial sync. So where are you syncing from? It's possible that your source is not working properly, and it'd need to be removed from the list of mirrors.
Alternatively, if you have somehow hidden/excluded those "repodata" directories, I'd like to know why, ie. where did you see documentation that those should be excluded/hidden? That documentation should be fixed if this is the case.
Also, your rsync is still having problems:
$ rsync rsync://mirror.buana.web.id/centos/ rsync: failed to connect to mirror.buana.web.id (103.120.64.111): Connection refused (111) rsync error: error in socket IO (code 10) at clientserver.c(125) [Receiver=3.1.2]
centos@buana.net kirjoitti 17.11.2018 klo 17.21:
Hi,
I have done the full resync. Please check again. Thank you.
HTTP: http://mirror.buana.web.id/centos/ HTTPS: n/a RSYNC: rsync://mirror.buana.web.id/centos/
Sync schedule: Every 6 hrs Bandwidth: 1Gbps (will be upgraded to 10Gbps before end of year) Location: Jakarta, Indonesia Sponsor: BUANA dotnet by SUITEN.ID Sponsor URL: buana.net IPv4 address to authorize: 103.120.64.111 IPv6 address to authorize: n/a Email contact: centos@buana.net Mirroring AltArch: no
regards, Christian
On 2018-11-16 04:02, Anssi Johansson wrote:
centos@buana.net kirjoitti 15.11.2018 klo 18.35:
Hi,
I would like to register new mirror:
HTTP: http://mirror.buana.web.id/centos/ HTTPS: n/a RSYNC: rsync://mirror.buana.web.id/centos/
Sync schedule: Every 6 hrs Bandwidth: 1Gbps Location: Jakarta, Indonesia Sponsor: BUANA dotnet by SUITEN.ID Sponsor URL: buana.net IPv4 address to authorize: 103.120.64.111 IPv6 address to authorize: n/a Email contact: centos@buana.net Mirroring AltArch: no
Hi, unfortunately your mirror does not seem to be complete, and thus it does not fulfill the requirements.
Please do a full sync from some other external mirror first, without excluding anything. rsync://centos.mirror.angkasa.id/centos/ may be a convenient source for your initial sync. Please let us know when you think your mirror has all the files.
In addition, your rsync seems to be unreachable from outside:
$ rsync rsync://mirror.buana.web.id/centos/ rsync: failed to connect to mirror.buana.web.id (103.120.64.111): Connection refused (111) rsync error: error in socket IO (code 10) at clientserver.c(125) [Receiver=3.1.2] _______________________________________________ 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
CentOS-mirror mailing list CentOS-mirror@centos.org https://lists.centos.org/mailman/listinfo/centos-mirror