Principles and Practices of Persistent Node.js Application Execution in Linux Environments

Problem Background and Root Cause Analysis

In Linux server environments, many Node.js developers encounter a common issue: after starting a Node.js application through an SSH client (such as Putty), the application service becomes inaccessible once the SSH connection is closed. The fundamental reason for this phenomenon lies in the Linux process management mechanism.

When a user logs into a server via SSH, the system creates an SSH session process. All commands executed within this session, including starting Node.js applications, run as child processes of this SSH process. Linux systems have an important design feature: when a parent process terminates, all its child processes are automatically terminated as well. This is the fundamental reason why closing the Putty window causes the Node.js service to stop.

Basic Solution: Background Process Execution

The simplest solution is to run the Node.js application as a background process. By adding the & symbol at the end of the command, the process can run in the background:

node /srv/www/MyUserAccount/server/server.js &

While this approach is straightforward, it has an important limitation: even though the process runs in the background, its standard output (stdout) and standard error (stderr) still point to the original terminal. If the application performs console output, closing the terminal will cause a "broken pipe" error, leading to abnormal process termination.

Output Redirection Techniques

To address the output stream issue, output redirection techniques can be employed:

node /srv/www/MyUserAccount/server/server.js > stdout.txt 2> stderr.txt &

This command redirects standard output to the stdout.txt file and standard error to the stderr.txt file, thereby avoiding process abnormalities caused by terminal closure.

Advanced Process Management Tools

nohup Command

nohup (no hang up) is a built-in Linux tool specifically designed to keep processes running after user logout:

nohup node /srv/www/MyUserAccount/server/server.js &

When using nohup, it's important to note: properly exiting the SSH session should be done using the exit command, rather than directly closing the terminal window, to ensure the process correctly transitions to background operation.

tmux or Screen Session Management

For scenarios requiring interactive management, terminal multiplexers like tmux or screen can be used. These tools allow the creation of persistent sessions where processes continue running even if the SSH connection is interrupted, and you can later reconnect to the same session.

Node.js Specific Process Managers

PM2 Process Manager

PM2 is a production-grade process manager specifically designed for Node.js applications, offering rich features:

# Install PM2
npm install pm2 -g

# Start application
pm2 start app.js

# Check running status
pm2 list

# Stop application
pm2 stop 0

# Restart application
pm2 restart all

PM2 supports automatic restart, load balancing, log management, monitoring dashboard, and other advanced features, making it highly suitable for production environment deployment.

forever Module

forever is another popular Node.js process management tool:

# Install forever
npm install -g forever

# Start application
forever start server.js

# Limit restart attempts
forever -m5 server.js

# Monitor file changes for auto-restart
forever -w server.js

# Process management
forever list
forever stop 0
forever restart 0

Technical Solution Comparison and Selection Recommendations

Different solutions are suitable for different scenarios:

• Simple Testing Environment: Use & background execution or nohup command
• Development Environment: Recommended to use forever's file monitoring feature
• Production Environment: Recommended to use PM2, providing a complete process management ecosystem
• Multi-language Mixed Environment: Consider tmux or systemd services

Best Practice Recommendations

In actual deployments, it's recommended to follow these best practices:

1. Always configure appropriate logging and output redirection
2. Set reasonable process restart policies and resource limits
3. Use process monitoring tools to ensure service availability
4. Configure system services (such as systemd) in production environments
5. Regularly check log files and system resource usage

By understanding Linux process management mechanisms and selecting appropriate tools, you can ensure that Node.js applications run stably and persistently in various environments.