amazon web services - Rails backend 500 errors for old assets -
when deploy new version on server new asset versions, see 500 errors reported amazon. in logs, see request seem try fetch old versions of assets (old asset digest)
f, [2016-09-12t22:47:46.657377 #6663] fatal -- : [1a552b90-e121-4817-8d22-28d02677c12a] actioncontroller::routingerror (no route matches [get] "/assets/application-3d5482837991d4fb95e72bd2c8ea9c08b07b349115db14016c71d86b5e295fc2.js"):
i quite disturbed when see logs this, i'm not sure what's happening on client side : browser not render js/css @ all, or poll server again new assets ?? since have never witnessed html-only page rendering after server updates, assume okay, ?.
i'm using many developer tools, fiddling cache options, , i'm thinking maybe users browse without things experience error pages...
exception notifier doesn't throw email/notification errors getting amazon message alerts load balancer 500 errors. aws/elb - metricname: httpcode_backend_5xx - dimensions: [loadbalancername = xxx]
verdict ?
are these assets no longer have on pages? if - can happen when eg google has cached old copy of page , (sometimes google crawler) tries @ , fetch assets it... no longer exists.
normally you'd 404 missing asset, in case - rails has changed path these assets, it'll throw routing error depicted.
likewise - if deploy new version of site , asset has been updated (eg added application.js)... magic id asset changes... (the big long number) causes old version no longer available. customer needs refresh page new url application-<longmagicnumber>.js
Comments
Post a Comment