a year ago
Project ID: 4d88bd05-8122-4159-90e0-4dc061af6807
I'm hosting an n8n instance on Railway and unfortunately every few hours the Railway deployment restarts, causing an error in our n8n and crashing our active n8n workflows. At the time of the crash, Railway showed this error I've screenshotted. How can we make sure the deployment doesn't restart constantly?
14 Replies
a year ago
is this a Worker or the Primary service?
a year ago
what's the ram usage like?
a year ago
seems related
a year ago
yeah they havent hit their limit, thats what i was gonna recommend too, set a service variable - NODE_OPTIONS=--max_old_space_size=8192
a year ago
Thanks.
Does it make sense to set this variable for Worker too?
a year ago
yes i would definitely set it on the worker too, regardless, it wont hurt
a year ago
thanks!
a year ago
the template has now been updated with these by default
a year ago
Hi guys,
I implemented these changes to both worker and primary, and I upgraded to pro plan and increased the Postgres rhythm volume to 20gb instead of 5gb
Since then, navigating through n8n, as well as the workflow executions, became extremely slow
I removed these variables to see if it would get back to normal, and it works even slower now
What might be the reason?