Error getaddrinfo EAI_AGAIN after running out of memory
-
Hi,
last week my droplet running nodebb ran out of memory. After resizing I could start nodebb again without problems but now I have problems fetching URLs with a getaddrinfo EAI_AGAIN error. After googling it could be a problem due to dns lookup.
I can't fetch the current nodebb version in acp for example:
2024-02-17T10:35:42.107Z [4567/138146] - error: [acp] Failed to fetch latest version TypeError: fetch failed at Object.fetch (node:internal/deps/undici/undici:11730:11) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async call (/home/nodebb/NodeBB/src/request.js:36:19) at async getLatestVersion (/home/nodebb/NodeBB/src/admin/versions.js:22:44) at async getLatestVersion (/home/nodebb/NodeBB/src/middleware/render.js:500:11) at async Promise.all (index 4) at async loadAdminHeaderFooterData (/home/nodebb/NodeBB/src/middleware/render.js:253:19) at async loadHeaderFooterData (/home/nodebb/NodeBB/src/middleware/render.js:137:11) at async renderMethod (/home/nodebb/NodeBB/src/middleware/render.js:87:30) at async ServerResponse.renderOverride [as render] (/home/nodebb/NodeBB/src/middleware/render.js:111:5)
I also have problems fetching the used url in the rss widget plugin:
Loading Jenkler RSS widget 3.2.10001 Error: getaddrinfo EAI_AGAIN news.google.com at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:118:26) at GetAddrInfoReqWrap.callbackTrampoline (node:internal/async_hooks:130:17) { errno: -3001, code: 'EAI_AGAIN', syscall: 'getaddrinfo', hostname: 'news.google.com' }
I also cannot send emails:
Fehler
getaddrinfo
EAI_AGAIN
smtp.strato.deI currently have no idea what causes the issue or how I could fix it easily. Does anyone have an idea maybe?
-
@phenomlab said in Error getaddrinfo EAI_AGAIN after running out of memory:
@dave1904 that looks very much like a DNS failure to me. From the CLI, are you able to ping
news.google.com
and get a response?At a guess, I'd say this won't work as you have a resolver issue.
You are right:
:~# ping news.google.com ping: news.google.com: Temporary failure in name resolution
-
Will try these steps later. Hope it helps
-
Fortunately, the problem has been solved. I don't know yet if DigitalOcean has changed anything, but the last thing I did were these prompts for diagnostics:
ping 8.8.8.8 ping google.com dig google.com dig google.com @1.1.1.1 cat /etc/resolv.conf systemd-resolve --status cat /etc/*release
-