App getting killed/crashed!
I have an app running using node js and node-cron which has 2 cron jobs right now. But the app keeps getting crashed without any logs except Killed.
ProjectId:
ecbdb5a0-8963-4fdd-a885-d53f1f97a52e
19 Replies
Project ID:
ecbdb5a0-8963-4fdd-a885-d53f1f97a52ethis might be the result of using more memory than your plan allows for, can you show me a screenshot of the memory metrics graph?
Looks like issue with memory?
BTW I am on the starter plan
Still not sure what is causing this, I am using
node-cron and slack bolt app, nothing fancy which might consume this amount of memorylooks like youre gonna be debugging your memory leak
Yeah, but hey thanks for helping finding the cause, appreciate it.
youre welcome, and i wish you good luck!
spiky
Trying it out without the cron hoping the spike fades out
definitely an issue with the memory cap. I highly suggest upgrading to the hobby plan. Both because of this issue and because the starter plan is being replaced by a 1-month trial plan starting August
so you won’t be able to use the platform if you don’t upgrade
@Adam I know about it, been trying to upgrade to the hobby plan but seems like my cards get declined for no apparent reason
The issue resolved by using
cron instead of node-cron. Seems some internal issue with node-cron itself.If you’re having issues, email billing@railway.app
cc: @Brody @eirk_
Just did.
@Adam I am trying to mail billing with the exact email that is on railway account (Github signed in) but getting this
there’s no need to ping people here, they’ll see it when they see it
cc’ing @rayofbytes on this. Email isn’t clear whether it’s bouncing or it’s valid. Also could be Github vs account email?
ray gone (on pto)
ahh right
@ngeloxyz then
Flagging this thread. A team member will be with you shortly.
we've identified the reason for bouncing the email to billing and are looking into fixing it
I'll send over a reply re: the payments issue via email.