I’ve just turned on one more new mirror server for software.virtualmin.com, and disabled the old one (that had a hard disk failure a couple weeks back and still has hardware problems that make it untrustworthy). So, there are now two servers for software.virtualmin.com (one in Paris, one in San Jose, both have very fast network and SSD drives).
This should resolve the issue some folks had with yum metadata mismatches on CentOS distros (it happened because repo metadata was generated on each mirror, rather than synced between the two, and changing that required changes to the way I push packages into our repos).
It also means our CentOS 5, and some of the other old distro repositories that stuck around out of inertia, on the old mirror are no longer accessible. Because those repos don’t exist on my staging server which is the “source of truth” for the repositories, they don’t exist on the new mirrors which have stricter rsync commands to keep things a little cleaner and small, so I can spin mirrors up and down very quickly.
Those old distros were already unmaintained (because the distros in question have been end-of-lifed by the upstream vendor for months or years), so this doesn’t actually change anything. But, if you’re still using one of those EOL distros (stop doing that; upgrade ASAP), you’ll need to disable the Virtualmin repository for that distro. You can keep the virtualmin-universal repository enabled, as it isn’t going anywhere and is still being updated with new Virtualmin packages.
Anyway, let me know if you run into any repository related issues. I have tested across most of our distributions and versions, but it’s late and I’m too tired to be extremely thorough about it. But, if you haven’t seen problems over the past couple of weeks, you probably won’t see problems now, as a mirror of this type has been in service for that time. And, the CentOS mirror issue should be resolved, so things should be more reliable.
Thanks for reading!