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
Describe the bug
My evershop server stops responding every 5 minutes and I am not able to debug the issue. I tried running the server in production with --debug but the pm2 logs still remains same. No extra informative or debug logs to understand what's causing this. I have checked CPU and memory spikes as well everything is normal.
Hitting pm2 reload or restart resolves the issue.
The only logs I see in nginx error logs is
2024/11/04 05:42:29 [error] 490617#490617: *60350 upstream timed out (110: Unknown error) while reading response header from upstream, client: 106.219.122.245, server: shopscape.co, request: "GET / HTTP/2.0", upstream: "http://[::1]:3000/", host: "shopscape.co"
2024/11/04 05:43:29 [error] 490617#490617: *60350 upstream timed out (110: Unknown error) while reading response header from upstream, client: 106.219.122.245, server: shopscape.co, request: "GET / HTTP/2.0", upstream: "http://127.0.0.1:3000/", host: "shopscape.co"
2024/11/04 05:44:30 [error] 490617#490617: *60350 upstream timed out (110: Unknown error) while reading response header from upstream, client: 106.219.122.245, server: shopscape.co, request: "GET /favicon.ico HTTP/2.0", upstream: "http://[::1]:3000/favicon.ico", host: "shopscape.co", referrer: "https://shopscape.co/"
How do I debug this?
The text was updated successfully, but these errors were encountered:
I was mistaken, the server did run for 12 hours and when it stopped again I tried to curl on localhost and it didn't even respond on localhost at that time. It seems like some specific event or trigger takes down the evershop server. I am not able to debug this.
pm2 reload/restart fixes the issue
Describe the bug
My evershop server stops responding every 5 minutes and I am not able to debug the issue. I tried running the server in production with
--debug
but the pm2 logs still remains same. No extra informative or debug logs to understand what's causing this. I have checked CPU and memory spikes as well everything is normal.Hitting pm2 reload or restart resolves the issue.
The only logs I see in nginx error logs is
How do I debug this?
The text was updated successfully, but these errors were encountered: