Kutt Won't Boot after Power Outage

[jhary2112]

Last night the homelab went down after a long power outage. The container that runs Kutt rebooted, but when I try to access Kutt, I get a screen that states: "Error! An error occurred. Please try again later." From the command line, I tried to run "npm start" and get the following error code:

> kutt@3.2.2 start
> node server/server.js --production

node:events:496
      throw er; // Unhandled 'error' event
      ^

Error: listen EADDRINUSE: address already in use :::3000
    at Server.setupListenHandle [as _listen2] (node:net:1937:16)
    at listenInCluster (node:net:1994:12)
    at Server.listen (node:net:2099:7)
    at Function.listen (/root/kutt-3.2.3/node_modules/express/lib/application.js:635:24)
    at Object.<anonymous> (/root/kutt-3.2.3/server/server.js:80:5)
    at Module._compile (node:internal/modules/cjs/loader:1554:14)
    at Object..js (node:internal/modules/cjs/loader:1706:10)
    at Module.load (node:internal/modules/cjs/loader:1289:32)
    at Function._load (node:internal/modules/cjs/loader:1108:12)
    at TracingChannel.traceSync (node:diagnostics_channel:322:14)
Emitted 'error' event on Server instance at:
    at emitErrorNT (node:net:1973:8)
    at process.processTicksAndRejections (node:internal/process/task_queues:90:21) {
  code: 'EADDRINUSE',
  errno: -98,
  syscall: 'listen',
  address: '::',
  port: 3000
}

I see it has a port conflict, but I'm stuck from there. Even a restart of the node did not help. Any suggestions? Thanks.

[jhary2112]

I changed the port to 3001, and that seems to have solved the issue, though I have no other services running on port 3000.

[trgwii]

Seems like Docker is probably holding the port hostage on the host or missing SO_REUSEADDR somewhere in your stack, not a Kutt-specific bug. Kutt does use SO_REUSEADDR by default since nodejs does, so it would not get this error unless another node process was actually alive.

[jhary2112]

Well, after a reboot, the same thing happens. The new port gives me an error. Only when I change the port again in the .env does it work. Do I have to manually restart it every time?

BTW, I'm not using Docker. Should I be? Is that my issue?

[poeti8]

No, do not use Docker unless you really need to, it eats up your resources.

Somehow the port is still in use in the background. Depending on your system, you can manually shut down the port, on Linux/macOS:

# find the process
lsof -i tcp:3000

# kill the process (replace PID with the process ID found above)
kill -9 PID

Or use npm package:

npx kill-port 3000

I'm not sure why this happens, I need more information so I can track it down, but either way I don't think it's particularly because of Kutt.

[jhary2112]

This is weird. I have assigned port 3000, and when I boot the server I get an error in the Kutt web interface. Yes, it's because port 3000 is "in use." I kill the port, per instructions, and it instantly is back up.

What further information may I provide? I'd like to track this down. Thanks.

[poeti8]

Do you use a process manager like pm2? Or do you remember ever using your system's default process manager?
You may want to search for a way to delete that Node.js process on your system.