I enabled ipv6 on a server recently and started getting errors from yum-cron intermittantly:
(Cron Daemon) root@myserver.corp.example.net Fri, Feb 25, 12:15 AM (9 days ago)
to root
/etc/cron.hourly/0yum-hourly.cron:
Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64 error was
12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64: (28, ‘Operation timed out after 30001 milliseconds with 0 out of 0 bytes received’)
I think there is a problem with one or more of the ipv6 servers for mirror.fedoraproject.org.
AAAA mirror.fedoraproject.org is a multi-AAAA record entry probably to promote roundrobin load balancing. I hit it with curl a few tiems and sometimes get the timeout usually I don’t. I set up a loop to try yum cron every 10 seconds, and here we go:
r 140 at: Sun Mar 6 12:18:55 CST 2022
iter 141 at: Sun Mar 6 12:19:08 CST 2022
iter 142 at: Sun Mar 6 12:19:21 CST 2022
iter 143 at: Sun Mar 6 12:19:34 CST 2022
iter 144 at: Sun Mar 6 12:19:47 CST 2022
Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64 error was
12: Timeout on https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64: (28, ‘Operation timed out after 30001 milliseconds with 0 out of 0 bytes received’)
iter 145 at: Sun Mar 6 12:20:30 CST 2022
iter 146 at: Sun Mar 6 12:20:58 CST 2022
iter 147 at: Sun Mar 6 12:21:26 CST 2022
iter 148 at: Sun Mar 6 12:21:54 CST 2022
How do I get yum-cron to tell me more about why it timed out and show the actual IP that timed out?
I think this is essential to pinpoint which mirror is bad so I can reach out to them.