Fedora MirrorManager report for Lab001
by admin
This is an automated report from the Fedora MirrorManager at https://admin.fedoraproject.org.
Site: Lab001 https://admin.fedoraproject.org/site/1251
* Details for Host name ipa.example.com
[https://admin.fedoraproject.org/mirrormanager/host/1637]:
* Host ipa.example.com Category Fedora Linux has no URLs. Please
add a URL to the content your mirror carries, or if not carried,
delete the Category.
* Please consider adding an rsync URL for Category Fedora Linux.
This will speed up the MirrorManager crawler and reduce load on your
server. URLs can be marked 'for other mirrors only', in which case
they will not appear in publiclists, mirrorlists, or metalinks, but
will be available to the MirrorManager crawler. If necessary, you
can restrict access to only allow from the MirrorManager crawler
through a 'hosts allow = 209.132.181.0/24' line in your rsyncd.conf
file.
* Host ipa.example.com Category Fedora Linux has no up-to-date
directories. * Consult the crawler logs and check your
report_mirror.conf.
* Host ipa.example.com Category Fedora EPEL has no URLs. Please
add a URL to the content your mirror carries, or if not carried,
delete the Category.
* Please consider adding an rsync URL for Category Fedora EPEL.
This will speed up the MirrorManager crawler and reduce load on your
server. URLs can be marked 'for other mirrors only', in which case
they will not appear in publiclists, mirrorlists, or metalinks, but
will be available to the MirrorManager crawler. If necessary, you
can restrict access to only allow from the MirrorManager crawler
through a 'hosts allow = 209.132.181.0/24' line in your rsyncd.conf
file.
* Host ipa.example.com Category Fedora EPEL has no up-to-date
directories. * Consult the crawler logs and check your
report_mirror.conf.
* Host ipa.example.com has never checked in with report_mirror.
Private mirrors must run report_mirror after each rsync run
completes in order for MirrorManager to know what content your
mirror carries. The crawler does not generally run against private
mirrors.
* Host ipa.example.com is private has no netblocks or ASN set or
asn_clients set. Clients will not automatically be directed to your
mirror. Please set either netblocks or ASN value and asn_clients.
If you no longer mirror Fedora, we thank you for your past support,
and ask that you please delete any references to your mirror from
the MirrorManager database. This will prevent any further such
reports from being mailed to you unnecessarily. If you have any
other questions, consult
https://fedoraproject.org/wiki/Infrastructure/Mirroring or mail to
mirror-admin(a)fedoraproject.org.
10 years, 10 months
Fedora MirrorManager report for Globo.com
by admin
This is an automated report from the Fedora MirrorManager at https://admin.fedoraproject.org.
Site: Globo.com https://admin.fedoraproject.org/site/1250
* Details for Host name mirror.globo.com
[https://admin.fedoraproject.org/mirrormanager/host/1636]:
* Please consider adding an rsync URL for Category Fedora Linux.
This will speed up the MirrorManager crawler and reduce load on your
server. URLs can be marked 'for other mirrors only', in which case
they will not appear in publiclists, mirrorlists, or metalinks, but
will be available to the MirrorManager crawler. If necessary, you
can restrict access to only allow from the MirrorManager crawler
through a 'hosts allow = 209.132.181.0/24' line in your rsyncd.conf
file.
* Please consider adding an rsync URL for Category Fedora EPEL.
This will speed up the MirrorManager crawler and reduce load on your
server. URLs can be marked 'for other mirrors only', in which case
they will not appear in publiclists, mirrorlists, or metalinks, but
will be available to the MirrorManager crawler. If necessary, you
can restrict access to only allow from the MirrorManager crawler
through a 'hosts allow = 209.132.181.0/24' line in your rsyncd.conf
file.
If you no longer mirror Fedora, we thank you for your past support,
and ask that you please delete any references to your mirror from
the MirrorManager database. This will prevent any further such
reports from being mailed to you unnecessarily. If you have any
other questions, consult
https://fedoraproject.org/wiki/Infrastructure/Mirroring or mail to
mirror-admin(a)fedoraproject.org.
10 years, 10 months
Fedora MirrorManager report for Tekelec-GSS
by admin
This is an automated report from the Fedora MirrorManager at https://admin.fedoraproject.org.
Site: Tekelec-GSS https://admin.fedoraproject.org/site/1243
* Details for Host name tekelec-gss-mirror
[https://admin.fedoraproject.org/mirrormanager/host/1630]:
* Host tekelec-gss-mirror has set asn_clients, but has not set
it's Autonomous System Number (ASN). Please set a value for ASN
(lookup tool at http://asn.cymru.com/).
* Host tekelec-gss-mirror Category Fedora Linux has no URLs.
Please add a URL to the content your mirror carries, or if not
carried, delete the Category.
* Please consider adding an rsync URL for Category Fedora Linux.
This will speed up the MirrorManager crawler and reduce load on your
server. URLs can be marked 'for other mirrors only', in which case
they will not appear in publiclists, mirrorlists, or metalinks, but
will be available to the MirrorManager crawler. If necessary, you
can restrict access to only allow from the MirrorManager crawler
through a 'hosts allow = 209.132.181.0/24' line in your rsyncd.conf
file.
* Host tekelec-gss-mirror Category Fedora Linux has no up-to-date
directories. * Consult the crawler logs and check your
report_mirror.conf.
* Host tekelec-gss-mirror Category Fedora Other has no URLs.
Please add a URL to the content your mirror carries, or if not
carried, delete the Category.
* Please consider adding an rsync URL for Category Fedora Other.
This will speed up the MirrorManager crawler and reduce load on your
server. URLs can be marked 'for other mirrors only', in which case
they will not appear in publiclists, mirrorlists, or metalinks, but
will be available to the MirrorManager crawler. If necessary, you
can restrict access to only allow from the MirrorManager crawler
through a 'hosts allow = 209.132.181.0/24' line in your rsyncd.conf
file.
* Host tekelec-gss-mirror Category Fedora Other has no up-to-date
directories. * Consult the crawler logs and check your
report_mirror.conf.
* Host tekelec-gss-mirror has never checked in with report_mirror.
Private mirrors must run report_mirror after each rsync run
completes in order for MirrorManager to know what content your
mirror carries. The crawler does not generally run against private
mirrors.
* Host tekelec-gss-mirror is private has no netblocks or ASN set
or asn_clients set. Clients will not automatically be directed to
your mirror. Please set either netblocks or ASN value and
asn_clients.
If you no longer mirror Fedora, we thank you for your past support,
and ask that you please delete any references to your mirror from
the MirrorManager database. This will prevent any further such
reports from being mailed to you unnecessarily. If you have any
other questions, consult
https://fedoraproject.org/wiki/Infrastructure/Mirroring or mail to
mirror-admin(a)fedoraproject.org.
10 years, 10 months
Fedora MirrorManager report for mirror.UNEJ.ac.id
by admin
This is an automated report from the Fedora MirrorManager at https://admin.fedoraproject.org.
Site: mirror.UNEJ.ac.id https://admin.fedoraproject.org/site/1241
* Details for Host name mirror.unej.ac.id
[https://admin.fedoraproject.org/mirrormanager/host/1628]:
* Host mirror.unej.ac.id claims to be on Internet2, but is not in
the Internet2 BGP table. Please clear the Internet2 flag.
* Please consider adding an rsync URL for Category Fedora EPEL.
This will speed up the MirrorManager crawler and reduce load on your
server. URLs can be marked 'for other mirrors only', in which case
they will not appear in publiclists, mirrorlists, or metalinks, but
will be available to the MirrorManager crawler. If necessary, you
can restrict access to only allow from the MirrorManager crawler
through a 'hosts allow = 209.132.181.0/24' line in your rsyncd.conf
file.
* Host mirror.unej.ac.id has never checked in with report_mirror.
Public mirrors are encouraged to run report_mirror after each rsync
run completes.
If you no longer mirror Fedora, we thank you for your past support,
and ask that you please delete any references to your mirror from
the MirrorManager database. This will prevent any further such
reports from being mailed to you unnecessarily. If you have any
other questions, consult
https://fedoraproject.org/wiki/Infrastructure/Mirroring or mail to
mirror-admin(a)fedoraproject.org.
10 years, 10 months
Fedora MirrorManager report for umepel
by admin
This is an automated report from the Fedora MirrorManager at https://admin.fedoraproject.org.
Site: umepel https://admin.fedoraproject.org/site/1238
* Details for Host name rhel.umops.us
[https://admin.fedoraproject.org/mirrormanager/host/1625]:
* Host rhel.umops.us Category Fedora EPEL has no URLs. Please add
a URL to the content your mirror carries, or if not carried, delete
the Category.
* Please consider adding an rsync URL for Category Fedora EPEL.
This will speed up the MirrorManager crawler and reduce load on your
server. URLs can be marked 'for other mirrors only', in which case
they will not appear in publiclists, mirrorlists, or metalinks, but
will be available to the MirrorManager crawler. If necessary, you
can restrict access to only allow from the MirrorManager crawler
through a 'hosts allow = 209.132.181.0/24' line in your rsyncd.conf
file.
* Host rhel.umops.us Category Fedora EPEL has no up-to-date
directories. * Consult the crawler logs and check your
report_mirror.conf.
* Host rhel.umops.us has never checked in with report_mirror.
Private mirrors must run report_mirror after each rsync run
completes in order for MirrorManager to know what content your
mirror carries. The crawler does not generally run against private
mirrors.
If you no longer mirror Fedora, we thank you for your past support,
and ask that you please delete any references to your mirror from
the MirrorManager database. This will prevent any further such
reports from being mailed to you unnecessarily. If you have any
other questions, consult
https://fedoraproject.org/wiki/Infrastructure/Mirroring or mail to
mirror-admin(a)fedoraproject.org.
10 years, 10 months
Fedora MirrorManager report for ahs-cloud
by admin
This is an automated report from the Fedora MirrorManager at https://admin.fedoraproject.org.
Site: ahs-cloud https://admin.fedoraproject.org/site/1235
* Details for Host name 206.142.229.20
[https://admin.fedoraproject.org/mirrormanager/host/1622]:
* Host 206.142.229.20 has set asn_clients, but has not set it's
Autonomous System Number (ASN). Please set a value for ASN (lookup
tool at http://asn.cymru.com/).
* Host 206.142.229.20 Category Fedora EPEL has no URLs. Please
add a URL to the content your mirror carries, or if not carried,
delete the Category.
* Please consider adding an rsync URL for Category Fedora EPEL.
This will speed up the MirrorManager crawler and reduce load on your
server. URLs can be marked 'for other mirrors only', in which case
they will not appear in publiclists, mirrorlists, or metalinks, but
will be available to the MirrorManager crawler. If necessary, you
can restrict access to only allow from the MirrorManager crawler
through a 'hosts allow = 209.132.181.0/24' line in your rsyncd.conf
file.
* Host 206.142.229.20 Category Fedora EPEL has no up-to-date
directories. * Consult the crawler logs and check your
report_mirror.conf.
* Host 206.142.229.20 has never checked in with report_mirror.
Private mirrors must run report_mirror after each rsync run
completes in order for MirrorManager to know what content your
mirror carries. The crawler does not generally run against private
mirrors.
* Host 206.142.229.20 is private has no netblocks or ASN set or
asn_clients set. Clients will not automatically be directed to your
mirror. Please set either netblocks or ASN value and asn_clients.
If you no longer mirror Fedora, we thank you for your past support,
and ask that you please delete any references to your mirror from
the MirrorManager database. This will prevent any further such
reports from being mailed to you unnecessarily. If you have any
other questions, consult
https://fedoraproject.org/wiki/Infrastructure/Mirroring or mail to
mirror-admin(a)fedoraproject.org.
10 years, 10 months
Fedora MirrorManager report for G3nius.net
by admin
This is an automated report from the Fedora MirrorManager at https://admin.fedoraproject.org.
Site: G3nius.net https://admin.fedoraproject.org/site/1233
* Details for Host name mirror.g3nius.net
[https://admin.fedoraproject.org/mirrormanager/host/1619]:
* Please consider adding an rsync URL for Category Fedora Linux.
This will speed up the MirrorManager crawler and reduce load on your
server. URLs can be marked 'for other mirrors only', in which case
they will not appear in publiclists, mirrorlists, or metalinks, but
will be available to the MirrorManager crawler. If necessary, you
can restrict access to only allow from the MirrorManager crawler
through a 'hosts allow = 209.132.181.0/24' line in your rsyncd.conf
file.
* Please consider adding an rsync URL for Category Fedora EPEL.
This will speed up the MirrorManager crawler and reduce load on your
server. URLs can be marked 'for other mirrors only', in which case
they will not appear in publiclists, mirrorlists, or metalinks, but
will be available to the MirrorManager crawler. If necessary, you
can restrict access to only allow from the MirrorManager crawler
through a 'hosts allow = 209.132.181.0/24' line in your rsyncd.conf
file.
If you no longer mirror Fedora, we thank you for your past support,
and ask that you please delete any references to your mirror from
the MirrorManager database. This will prevent any further such
reports from being mailed to you unnecessarily. If you have any
other questions, consult
https://fedoraproject.org/wiki/Infrastructure/Mirroring or mail to
mirror-admin(a)fedoraproject.org.
10 years, 10 months