{"id":17169,"date":"2025-12-26T18:42:27","date_gmt":"2025-12-26T13:12:27","guid":{"rendered":"https:\/\/www.skynats.com\/?p=17169"},"modified":"2025-12-26T18:42:30","modified_gmt":"2025-12-26T13:12:30","slug":"managing-large-pm2-log-files-how-to-avoid-disk-space-disasters","status":"publish","type":"post","link":"https:\/\/www.skynats.com\/blog\/managing-large-pm2-log-files-how-to-avoid-disk-space-disasters\/","title":{"rendered":"Managing Large PM2 Log Files: How to Avoid Disk Space Disasters"},"content":{"rendered":"\n

If you\u2019re running Node.js applications in production, PM2 is a lifesaver for process management. However, log handling is often overlooked\u2014Managing Large PM2 Log Files is critical, as unmanaged logs can grow rapidly and consume valuable server disk space.<\/p>\n\n\n\n

The Problem<\/strong><\/h2>\n\n\n\n

By default, PM2 generates logs for your Node.js<\/mark><\/a> applications. In development, this isn\u2019t a big deal\u2014but in production, it can become a huge problem.<\/p>\n\n\n\n

We noticed that PM2 log file had grown to large log file size due to repeated application logs. This will make the entire server space to occupy.<\/p>\n\n\n\n

A quick check with:<\/p>\n\n\n\n

du -h ~\/.pm2\/pm2.log<\/code><\/pre>\n\n\n\n
confirmed the massive size of the log.<\/p>\n\n\n\n
The Wrong Way to Delete Logs<\/strong><\/h2>\n\n\n\n
Initially, We will try \u201cdelete the log file\u201d approach:<\/p>\n\n\n\n
\/\/ DANGER: DO NOT DO THIS!\nrm ~\/.pm2\/pm2.log<\/code><\/pre>\n\n\n\n
This doesn\u2019t work because the PM2 process still holds the file open. The disk space won\u2019t be freed until PM2 is restarted or the server is rebooted.<\/p>\n\n\n\n
The Right Way: PM2 Flush<\/strong><\/h2>\n\n\n\n
PM2 provides a proper way to clear logs:<\/p>\n\n\n\n
pm2 flush<\/code><\/pre>\n\n\n\n
This command clears the logs in the main ~\/.pm2\/pm2.log file. You can reboot afterward to ensure everything resets, but flushing alone usually solves the space issue.<\/p>\n\n\n\n
Preventing Future Problems: Log Rotation<\/strong><\/h2>\n\n\n\n
The key lesson: implement log rotation. PM2 has a built-in module called pm2-logrotate that handles this elegantly.<\/p>\n\n\n\n
Step 1: Install pm2-logrotate<\/strong><\/h3>\n\n\n\n
pm2 install pm2-logrotate<\/code><\/pre>\n\n\n\n
Step 2: Configure Your Rotation Settings<\/strong><\/h3>\n\n\n\n
Here\u2019s an example that works well for production:<\/p>\n\n\n\n
pm2 set pm2-logrotate:max_size 100M        # Rotate logs once they reach 100MB\npm2 set pm2-logrotate:retain 10           # Keep the last 10 rotated logs\npm2 set pm2-logrotate:compress true       # Compress old logs<\/code><\/pre>\n\n\n\n
Default Settings<\/strong><\/h4>\n\n\n\n
If you need to reset, these are PM2\u2019s default values:<\/p>\n\n\n\n
pm2 set pm2-logrotate:retain 30\npm2 set pm2-logrotate:compress false\npm2 set pm2-logrotate:dateFormat YYYY-MM-DD_HH-mm-ss\npm2 set pm2-logrotate:max_size 10M\npm2 set pm2-logrotate:rotateInterval 0 0 * * *\npm2 set pm2-logrotate:rotateModule true\npm2 set pm2-logrotate:workerInterval 30<\/code><\/pre>\n\n\n\n
With log rotation enabled, your log files will:<\/p>\n\n\n\n