Deployment Crashed and wont restart
patatinio
HOBBYOP

a year ago

Both my pg database and application crashed and wont restart. there are no logs for the crash

Solved

26 Replies

patatinio
HOBBYOP

a year ago

9207fbc2-11b4-4856-b2c0-bdf71611ce22


a year ago

Did you try redeploying the DB?

Can you also double check to see if there's no error logs in the "Deploy" section of the logs?


patatinio
HOBBYOP

a year ago

10 minutes after the original crash after 3-4 failures i managed to redeploy the DB. but the app wont redeploy. the last available logs are the ones of the original crash


patatinio
HOBBYOP

a year ago

they start like this:

error: could not fdatasync file "000000010000000000000036": No space left on device

the volume of the db is not full.


a year ago

Ok, so is the DB up and running fine right now? The issue is with your app?


patatinio
HOBBYOP

a year ago

corrrect


a year ago

Because the error you sent is a common postgres error afaik, unless your app is using the filesystem like crazy


a year ago

We need to see what errors is your app throwing


patatinio
HOBBYOP

a year ago

this is the from the app log. last entry is at 13:16 -> currrently 16:59 despite trying to redeploy multiple times. the app crashes without log


a year ago

What does your app do? Maybe it needs a volume attached?

https://docs.railway.com/reference/volumes


patatinio
HOBBYOP

a year ago

it is working like this for a year and a half is it possible ?


a year ago

Maybe, if you exceed the ephemeral storage (I think its ~10gb) your app will crash, but since we are redeploying and you don't have a volume attach my guess is that it is empty right now.


a year ago

What are you trying to deploy?


a year ago

What is this "app" of yours?


patatinio
HOBBYOP

a year ago

it is a very simple nodejs app memory never over 100mb. code size not over 10mb.


patatinio
HOBBYOP

a year ago

I have not made any changes to the code for months. It is running like this and clients are connecting normally without issue for over a year. the issue seems identical to @Lucas Contreras reported at the same time


patatinio
HOBBYOP

a year ago

I was trying restart. I now "repedployed" and it is up for now


a year ago

Is it working as intended and making db calls fine?


patatinio
HOBBYOP

a year ago

seems like it works ok. but since this have never happened I am really worrried


a year ago

Don't be worried about it! This was an extensive chat because I thought u had already tried redeploying the service instead of restarting it!


a year ago

And if any issue occur again, feel free to open another help thread 😉


patatinio
HOBBYOP

a year ago

Thank you for the help and sorry for the misinformation. Is this something that happens regularly? I mean is this common ?


a year ago

It isn't common and definitely doesn't happen regularly.


patatinio
HOBBYOP

a year ago

Thank you


a year ago

I will mark this thread as solved, feel free to open a new one if needed!


a year ago

!s


Status changed to Solved medim about 1 year ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...