Webmasters Stack Exchange is a question and answer site for webmasters. It only takes a minute to sign up.
Sign up to join this community
I have a NodeJS server on a virtual machine. I connect to the machine through SSH and leave the server running with:
npm start &
If I disconnect with Ctl-D, the server keeps running. If my internet drops and the connection fails, the server also stops. Why does this happen, and how can I leave the server running without it dropping because of the internet disconnection?
Even when it is running in the background, the server is still a child process of your ssh session. To get it to run independently, you can run it with nohup:
nohup npm start &
Wikipedia says:
Note that nohupping backgrounded jobs is typically used to avoid terminating them when logging off from a remote SSH session. A different issue that often arises in this situation is that ssh is refusing to log off ("hangs"), since it refuses to lose any data from/to the background job(s). This problem can also be overcome by redirecting all three I/O streams:
nohup npm start > npm.out 2> npm.err < /dev/null &
NODE_OPTIONS=--max_old_space_size=50000 NODE_ENV=production nohup npm start >> stdout5.md 2>> stderr5.md < /dev/null &, the SSH session disconnected because of an internet failure, and the server went down. How can I debug it?
Aug 31, 2021 at 18:59
$ cat ~/.ssh/config ConnectTimeout 10 ConnectionAttempts 100 you could also try using a keep alive ping with ServerAliveInterval 60. Those might reduce the problem.
Sep 1, 2021 at 10:18
nohup. If that isn't working for you, my only other suggestion is configuring npm as a service.
Sep 1, 2021 at 10:20