Over the QA Hackathon, we added Fastly caching to the cpantesters. That error appears when the cache can't access cpantesters itself to update its cache. We're still trying to get everything figured out here.
Fastly does geocaching, so you get a local version faster. It caches for about an hour, since that's approximately how often the static site gets updated anyway. It doesn't seem to have a way to set how long it waits for a response from cpantesters though. The cache not waiting long enough is my current theory on why this problem is happening. From what I understand, Varnish isn't going away. It serves a different use-case than (though slightly overlapping with) Nginx. I'm also not sure which features of Nginx are premium-only these days... > On May 3, 2016, at 3:27 PM, L Walsh <cpan-tes...@tlinx.org> wrote: > > When I am looking at a smoker's test, there are buttons for 'RAW' and 'BACK'. > BACK has reliably taken me to the version matrix, showing me > highest module value for a given perl, and showing me all the tests > run w/latest module on what platform. > > Starting a few months back, hitting that BACK button has given me > some variation on the following: > > at address: > > http://www.cpantesters.org/distro/P/P.html#P-1.1.34 > > I get the following message: > > > Error 503 backend read error > > backend read error > > > Guru Mediation: > > Details: cache-lax1431-LAX 1462305240 3596103454 > > ------------------------------------------------------------------------ > > Varnish cache server > > > ================================================== > What does the above mean? As near as I can tell, varnish > is supposed to be an accelerator of pre-composed, static > content. > I get a very vague impression that it may be nearing its EOL > as other options (involving NGINX/fastcgi cache, et al) are > starting show some improvements. ( > https://deliciousbrains.com/page-caching-varnish-vs-nginx-fastcgi-cache/ ), > but those could be some particular workload on some specific HW. > > Meanwhile, I've gone from never having seen the above message several months > ago, to seeing it multiple times per day (or more) depending on > how often I try to look at overall error reports. > > Is something wrong/misconfigured with the server that is > using this package, or is the package being updated faster than > the bugs can be ironed out? > > Thank for any ideas & or cue-sticks... ;-) > > Linda > > > > > >
