Mdchosen
Issue with node-cron Jobs behaving differently in different environments
I have a strange issue where I have a chron job that behaves properly in my development environment (ie. it runs once a day at the specified time) but in the production environment it runs every minute. The code is exactly the same (it's reading from the same git repository and commit.) Has anyone run into this problem?
17 replies
ECONNRESET
Hi team, I'm very new to this. I've got a Medusa e-commerce website that I deployed on railway. I am seeing the server stops responding every once and a while. (Most recently the server went 4 days without issue) And I got the following error:
Error: read ECONNRESET at TCP.onStreamRead (node:internal/stream_base_commons:217:20) { errno: -104, code: 'ECONNRESET', syscall: 'read' }
In between these errors I have no issue.
I'm on the hobby plan.
I had to redeploy the server to get it working again.
Has anyone experienced this or now how to avoid restarting redeploying the server. This is espcially troubling because as an ecommerce site, when the server randomly stops responding I'm potentially losing customers without knowing.
8 replies
Econnreset error
Hi team, I'm very new to this. I've got a Medusa e-commerce website that I deployed on railway. Yesterday I saw strange behavior on the site specifically the server would stop responding every few hours. And I got the following error:
Error: read ECONNRESET at TCP.onStreamRead (node:internal/stream_base_commons:217:20) { errno: -104, code: 'ECONNRESET', syscall: 'read' }
In between these errors I have no issue.
I'm on the hobby plan.
Can someone tell me if this problem is related to my code or specific to railway, and how would I trouble shoot.
5 replies