You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The application is running using PM2, and the status consistently shows as "online" in the pm2 list output. However, the application becomes unresponsive at random, unexpected times. This issue persists even after enabling --watch for file changes. The problem occurs intermittently without clear error logs or indication in PM2 logs. The PM2 processes are listed as running, but the application is not responsive.
Steps to Reproduce
Start the application using PM2 in cluster mode with the --watch flag.
Allow the application to run for a period of time (seems to happen randomly).
Observe that despite showing "online," the application becomes unresponsive.
Logs do not indicate any immediate issues or failures, and restarts do not resolve the issue.
Expected Behavior
The application should remain responsive as long as it is running and detected as "online" by PM2. When file changes occur, PM2 should restart the application smoothly, and the app should continue to function without interruptions.
Actual Behavior
The application becomes unresponsive intermittently, even though:
PM2 status shows as "online."
The CPU and memory usage remain low, with minimal spikes.
The app instances are running, but no longer handle requests or function correctly.
The application is running using PM2, and the status consistently shows as "online" in the
pm2 list
output. However, the application becomes unresponsive at random, unexpected times. This issue persists even after enabling--watch
for file changes. The problem occurs intermittently without clear error logs or indication in PM2 logs. The PM2 processes are listed as running, but the application is not responsive.Steps to Reproduce
--watch
flag.Expected Behavior
The application should remain responsive as long as it is running and detected as "online" by PM2. When file changes occur, PM2 should restart the application smoothly, and the app should continue to function without interruptions.
Actual Behavior
The application becomes unresponsive intermittently, even though:
PM2 Report
Environment Details
Daemon Logs
The last 20 lines of PM2 logs don’t show anything significant at the time of the issue.
Additional Notes
↺ 6
), but the restarts don’t seem to resolve the issue.--watch
topm2 reload
at intervals, but the problem persists.Expected Fixes
--watch
properly detects changes and restarts the application as needed.The text was updated successfully, but these errors were encountered: