I'm Harry, and I want to be public mirror host for Fedora EPEL.
I have 2 server in Indonesia region. Supported by 10G bandwidth.
Sponsor Organization: DomaiNesia
- URL Sponsor: https://www.domainesia.com
- IPv4 Addr: 188.8.131.52
- IPv6 Addr: 2001:df7:5300:2::64
- Hostname Mirror: linux.domainesia.com/fedora/ (http, https, rsync)
Sponsor Organization: NevaCloud
- URL Sponsor: https://nevacloud.com
- IPv4 Addr: 184.108.40.206
- IPv6 Addr: 2001:df7:5300:2::63
- Hostname Mirror: mirror.nevacloud.com/fedora/ (http, https, rsync)
Please help for the next step.
I have a question regarding mirror manager information about our mirror. In december we had a HW failure on our mirror and we probably got disabled from mirror list (if it wasn’t disabled even earlier). As I see it on e.g. RockyLinux MirrorManager, it has to be manually reenabled again. We still keep mirror data-wise, but we are not serving any traffic = wasted space.
Could you please tell us, what administrative account (if any) is used for mirror ftp.sh.cvut.cz (to know whom to contact to get access or how to login to mirror manager) or if we should create new account to administer our mirror participance?
Network & System Administrator
www.siliconhill.cz / sh.cvut.cz
is it possible to move old Fedora systems to archive?
They are still present on primary mirrors. Current usages on mirrors:
Over 2 TB.
Possibly Fedora 34 will end in 2 weeks and can be moved to archives too.
Hey all, Fedora 36 has been staged and should now be available at
it is 543G in /pub/fedora/linux/releases//36/, 41G in
/pub/alt/releases//36/, 260G in /pub/fedora-secondary/releases//36/
and the RPMs are hard linked to pub/fedora/linux/development/36/Everything/
role: CPE Team - Senior Software Engineer
Thanks for the note. This email got held up due to not being from a
subscribed address on the mirror-admin(a)lists.fedoraproject.org address. We
believe we patched the problem later that day and should be 'fine' now.
However, we are still trying to determine what caused this issue with this
and some other mirrors.
Thank you for giving us a time window when this started to happen. What
timezone is that in?
We rsync epel mirror from rsync://download-ib01.fedoraproject.org/ and
we find that epel7_x86_64 repodata was lost all primary gz,xml file on
2020-05-04 06:00-12:00 and this worries us.
What's the reason for the problem and can we avoid such problems.
Stephen J Smoogen.
Let us be kind to one another, for most of us are fighting a hard battle.
-- Ian MacClaren