Mysterious Crash of Next.js Instance - ECONNREFUSED 127.0.0.1:54295
Unanswered
ejlien posted this in #help-forum
ejlienOP
Hi, today we had an issue in production, and I have no clue what caused it. It seems like an issue with Next.js itself. I restarted the instance, and everything started running fine again....
There were messages like these all over the logs as users were trying to access the page. I have no idea what is running on port 127.0.0.1:54295; I assume it’s either calling some low-level Rust library or another Node.js process.
[prod] [2024-08-18 09:03:34] - error Failed to handle request for /75647/blablabla/......
[prod] [2024-08-18 09:03:34] TypeError: fetch failed
[prod] [2024-08-18 09:03:34] at Object.fetch (/workspace/node_modules/next/dist/compiled/undici/index.js:1:26669)
[prod] [2024-08-18 09:03:34] at runMicrotasks (<anonymous>)
[prod] [2024-08-18 09:03:34] at processTicksAndRejections (node:internal/process/task_queues:96:5)
[prod] [2024-08-18 09:03:34] at async invokeRequest (/workspace/node_modules/next/dist/server/lib/server-ipc/invoke-request.js:21:12)
[prod] [2024-08-18 09:03:34] at async requestHandler (/workspace/node_modules/next/dist/server/lib/start-server.js:336:33)
[prod] [2024-08-18 09:03:34] at async Server.<anonymous> (/workspace/node_modules/next/dist/server/lib/start-server.js:152:13) {
[prod] [2024-08-18 09:03:34] cause: Error: connect ECONNREFUSED 127.0.0.1:54295
[prod] [2024-08-18 09:03:34] at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16) {
[prod] [2024-08-18 09:03:34] errno: -111,
[prod] [2024-08-18 09:03:34] code: 'ECONNREFUSED',
[prod] [2024-08-18 09:03:34] syscall: 'connect',
[prod] [2024-08-18 09:03:34] address: '127.0.0.1',
[prod] [2024-08-18 09:03:34] port: 54295
[prod] [2024-08-18 09:03:34] }
[prod] [2024-08-18 09:03:34] }
Any idea what may have caused this or how to prevent this. We host on digitalocean's apps.
There were messages like these all over the logs as users were trying to access the page. I have no idea what is running on port 127.0.0.1:54295; I assume it’s either calling some low-level Rust library or another Node.js process.
[prod] [2024-08-18 09:03:34] - error Failed to handle request for /75647/blablabla/......
[prod] [2024-08-18 09:03:34] TypeError: fetch failed
[prod] [2024-08-18 09:03:34] at Object.fetch (/workspace/node_modules/next/dist/compiled/undici/index.js:1:26669)
[prod] [2024-08-18 09:03:34] at runMicrotasks (<anonymous>)
[prod] [2024-08-18 09:03:34] at processTicksAndRejections (node:internal/process/task_queues:96:5)
[prod] [2024-08-18 09:03:34] at async invokeRequest (/workspace/node_modules/next/dist/server/lib/server-ipc/invoke-request.js:21:12)
[prod] [2024-08-18 09:03:34] at async requestHandler (/workspace/node_modules/next/dist/server/lib/start-server.js:336:33)
[prod] [2024-08-18 09:03:34] at async Server.<anonymous> (/workspace/node_modules/next/dist/server/lib/start-server.js:152:13) {
[prod] [2024-08-18 09:03:34] cause: Error: connect ECONNREFUSED 127.0.0.1:54295
[prod] [2024-08-18 09:03:34] at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16) {
[prod] [2024-08-18 09:03:34] errno: -111,
[prod] [2024-08-18 09:03:34] code: 'ECONNREFUSED',
[prod] [2024-08-18 09:03:34] syscall: 'connect',
[prod] [2024-08-18 09:03:34] address: '127.0.0.1',
[prod] [2024-08-18 09:03:34] port: 54295
[prod] [2024-08-18 09:03:34] }
[prod] [2024-08-18 09:03:34] }
Any idea what may have caused this or how to prevent this. We host on digitalocean's apps.