themkrage
Node Memory and CPU Usage is low
I have a node instance that I'm running with tsx / node commands. I notice the job is slower when run on Railway than when on my local machine. Yet, the Railway memory and CPU usage are very low. How can I have the job use more CPU and memory on Railway?
15 replies
Puppeteer Hangs
Hi! I have Pupeteer up and running with node on railway, but for some reason, my job just hangs when I open too many (10-20) tabs. I automatically kill any worker that is idle for 10 minutes and almost all of them end up idle and killed and restarted! Looks like Puppeteer just doesn't load pages on Railway. 10-20 tabs really is not that much and there are no resource spikes in the Railway console. Why else would this job get killed?
This job runs fine locally.
27 replies
Cron-Job using node-cron is stopping mid execution
Hi! I am running like 5-10 cron- jobs in one instance of node-cron being run. I notice that when multiple jobs overlap at the same time, Railway restarts the instance. I looked into resource usage, and nothing passes any set limits for the instance, but there is certainly a spike.
How can I see why Railway restarted my container? I haven't beeen able to answer this in the UI
15 replies
Any changes recently on Railway that could cause this Auth0 error?
I randomly started getting errors from auth0 that from my research, only happen when the server can't access auth0. auth0 still works locally and when not hosted on Railway. I'm trying to rule out any recent change on railway that could cause this issue. Anything related to limiting web traffic recently get pushed?
Here is the error I now run into and a forum post about possible things that could cause it, including changes to ports, or changes to the default node.js railway container:
https://community.auth0.com/t/login-handler-failed-cause-discovery-requests-failing-for-https-stattracker-uk-auth0-com/128627/8
9 replies
I ran a recursive query and now there is no more space on device
I am getting this error:
2024-03-29 22:10:54.413 UTC [8] FATAL: could not write lock file "postmaster.pid": No space left on device
but i can't access the database with psql or anything to try and remove the uneccessary data. This is resulting in downtime for us.
22 replies
Certain Queries Hit a space Error, but we are no where close to hitting the 50GB allotted for pg
ERROR: could not resize shared memory segment "/PostgreSQL.904483596" to 4194304 bytes: No space left on device.
Hi our app is down from the above error when certain queries are run. These queries were previously working. I've tried restarting everything and the error does not happen on our local database.
Any ideas?
98f66160-ce86-4b15-a73b-cab912256208/service/30c393cd-fc3a-4ed3-a433-9017f7032947
23 replies