We have been getting the following errors recently:
1.) request to https://cdn.ampproject.org/rtv/metadata failed, reason: getaddrinfo EAI_AGAIN cdn.ampproject.org
2.) request to https://cdn.ampproject.org/version.txt failed, reason: connect EHOSTUNREACH
Both of the errors seems to be originating from:
/node_modules/@ampproject/toolbox-core/node_modules/node-fetch/lib/index.js:1461:11
The issue is intermittent and when it occurs, our nodeJS app is unable to recover without restarting. Is it possible to implement a retry to work around the EAI_AGAIN and EHOSTUNREACH errors? or at least invalidate any output that may have been cached by node-fetch?
We have been getting the following errors recently:
1.) request to https://cdn.ampproject.org/rtv/metadata failed, reason: getaddrinfo EAI_AGAIN cdn.ampproject.org
2.) request to https://cdn.ampproject.org/version.txt failed, reason: connect EHOSTUNREACH
Both of the errors seems to be originating from:
/node_modules/@ampproject/toolbox-core/node_modules/node-fetch/lib/index.js:1461:11
The issue is intermittent and when it occurs, our nodeJS app is unable to recover without restarting. Is it possible to implement a retry to work around the EAI_AGAIN and EHOSTUNREACH errors? or at least invalidate any output that may have been cached by node-fetch?