I’ve configured automatic yum updates on many machines, nearly all of them are frequently (almost every night) receiving a timeout error from “mirrors.fedoraproject.org” for the EPEL repo. The exact error is:
/etc/cron.hourly/0yum-hourly.cron: Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=st[..] error was 12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64&infra=st[..] (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Machines are a mix of Centos 6, 7, and 8. Mostly CentOS 7 and 8; this error happens to be from an EL7 machine; but all of them are doing it.
If I manually run these commands, they’re successful. I suspect this is load on the mirror network during overnight updates; but I can’t definitively say so.
Is there a way that I can confirm this is simply mirror network load?
If this is mirror network load, what is the best practice for scheduling my updates to help distribute load better for the mirror network?