#1323 CentOS Stream 9 Mirror request
Closed: Fixed by arrfab. Opened by basilm.

CentOS Stream 9 Mirror request

Make sure you're signed up as a mirror in the shared Fedora/CentOS
Mirrormanager instance: https://admin.fedoraproject.org/mirrormanager/
Link to your node/server in mirrormanager:

URLs - These are the hostnames and paths to where you host CentOS Stream

  • HTTP: http://mirrors.behostings.net/centos9
  • HTTPS: https://mirrors.behostings.net/centos9
  • RSYNC: rsync://mirrors.behostings.net/centos9

Bandwidth: 1250 Mbps
Country Location: BElgium
Sponor organization (optional): Behostings
Sponsor URL (optional): https://www.behostings.com

  • IPv4 Addresses: 193.138.101.173

Metadata Update from @arrfab:
- Issue assigned to arrfab
- Issue tagged with: low-trouble, medium-gain, mirrormanager

Thanks, but the link to your registered server in mirrormanager is missing .. can you provide it ?

minor remark : wondering if using centos9 is the best choice (but up2you) : it's all about centos-stream and stream 9 is there, but stream 10 started and will land at the same place so what about using centos-stream instead ? (and so be consistent about what other mirrors providers are also doing)

Thanks, but the link to your registered server in mirrormanager is missing .. can you provide it ?

The link to mirror manager >> https://admin.fedoraproject.org/mirrormanager/site/2561

minor remark : wondering if using centos9 is the best choice (but up2you) : it's all about centos-stream and stream 9 is there, but stream 10 started and will land at the same place so what about using centos-stream instead ? (and so be consistent about what other mirrors providers are also doing)

So, is the centos-stream better one?

Thanks, but the link to your registered server in mirrormanager is missing .. can you provide it ?

The link to mirror manager >> https://admin.fedoraproject.org/mirrormanager/site/2561

yes, that's a site but then you can add a host under that, which will be your mirror :)
wrt centos-stream name, yes I think it would be better, so if you can just change your rsync module name and also the directly for the vhost, that would be then perfect

Thanks, but the link to your registered server in mirrormanager is missing .. can you provide it ?

The link to mirror manager >> https://admin.fedoraproject.org/mirrormanager/site/2561

yes, that's a site but then you can add a host under that, which will be your mirror :)
wrt centos-stream name, yes I think it would be better, so if you can just change your rsync module name and also the directly for the vhost, that would be then perfect

The host has been added "mirrors.centos.behostings.net"

Thanks, but the link to your registered server in mirrormanager is missing .. can you provide it ?

The link to mirror manager >> https://admin.fedoraproject.org/mirrormanager/site/2561

yes, that's a site but then you can add a host under that, which will be your mirror :)
wrt centos-stream name, yes I think it would be better, so if you can just change your rsync module name and also the directly for the vhost, that would be then perfect

No, we cannot set that directly. So, please proceed with centos9 instead of stream

I added it but worth knowing that at your side, the A record doesn't exist anymore so host is actually unreachable

dig mirrors.behostings.net

; <<>> DiG 9.11.4-P2-RedHat-9.11.4-26.P2.el7_9.15 <<>> mirrors.behostings.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 28813
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;mirrors.behostings.net.                IN      A

;; AUTHORITY SECTION:
behostings.net.         1784    IN      SOA     ns1.behostings.net. root.behostings.net. 2023111500 1800 3600 1209600 86400

;; Query time: 8 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Tue Nov 28 13:13:16 UTC 2023
;; MSG SIZE  rcvd: 96

Closing request though, as you can fix it at your side but your mirror was added and CentOS category added to your host in mirrormanager

Metadata Update from @arrfab:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

The domain is >> mirrors.centos.behostings.net

I added it but worth knowing that at your side, the A record doesn't exist anymore so host is actually unreachable

```
dig mirrors.behostings.net

; <<>> DiG 9.11.4-P2-RedHat-9.11.4-26.P2.el7_9.15 <<>> mirrors.behostings.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 28813
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;mirrors.behostings.net. IN A

;; AUTHORITY SECTION:
behostings.net. 1784 IN SOA ns1.behostings.net. root.behostings.net. 2023111500 1800 3600 1209600 86400

;; Query time: 8 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Tue Nov 28 13:13:16 UTC 2023
;; MSG SIZE rcvd: 96
```

Closing request though, as you can fix it at your side but your mirror was added and CentOS category added to your host in mirrormanager

The domain or host is >> mirrors.centos.behostings.net

~~~
[root@powerdns zones]# dig a mirrors.centos.behostings.net

; <<>> DiG 9.11.36-RedHat-9.11.36-8.el8_8.2 <<>> a mirrors.centos.behostings.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39052
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;mirrors.centos.behostings.net. IN A

;; ANSWER SECTION:
mirrors.centos.behostings.net. 1800 IN A 193.138.101.173
~~~~~

I just used what you put in the description above btw :)

Sorry for the mishap.

The correct one is:

HTTP: http://mirrors.centos.behostings.net/centos9
HTTPS: https://mirrors.centos.behostings.net/centos9
RSYNC: rsync://mirrors.centos.behostings.net/centos9

yep, fixed in the DB too

yep, fixed in the DB too

thank you. Also, when will the site be visible in centos mirror list ?

Log in to comment on this ticket.

Metadata