Re: cpan.org Metadata and modules files not being updated
[email protected] (James E Keenan) Sun, 22 Mar 2026 07:38:11 -0400
| Newsgroups | perl.cpan.workers |
|---|---|
| Message-ID | <[email protected]> |
On 3/22/26 00:10, Ask Bjørn Hansen wrote: > Hi James (and everyone), > > Sorry about the head-banging, that was my fault! > > The CPAN index files on www.cpan.org were stale for most of today, for users in North America and Asia (in Europe it should have been okay). > > Yesterday I added two new backends for the Fastly CDN as part of decommissioning the old primary cluster (going from two to three origins). The CPAN sync into the web server storage wasn't set up on the new clusters, so they were serving a static copy from when they were first provisioned. The old working backend had fresh data, but requests hitting the new ones got stale index files. > > We usually catch this with monitoring, but not all the monitoring is in place yet for the new clusters. There's been a lot of work getting the new infrastructure up and it slipped through. > > I've switched the CDN back to only the working backend while I get the sync sorted on the new clusters. > > If you were seeing "this index file is 39 days old" warnings from the cpan shell, or modules not showing updated versions, that was this. > Ah! So it required deep sysadmin foo to understand! No wonder I was puzzled! Thanks for your investigation. At the very least, it got me to align my MyConfig.pm on 3 different machines.