The database has died and redeploy is not picking it up (stopped on mounting)
kravetsone
PROOP

10 months ago

Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/1cd59519-1073-47dd-9a12-5264b996c048/vol_wc5f3ho34ve0hs5u

Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/1cd59519-1073-47dd-9a12-5264b996c048/vol_wc5f3ho34ve0hs5u

Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/1cd59519-1073-47dd-9a12-5264b996c048/vol_wc5f3ho34ve0hs5u

Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/1cd59519-1073-47dd-9a12-5264b996c048/vol_wc5f3ho34ve0hs5u

Before redeploy attempts, the database simply stopped responding. From about 10.09 22:00 UTC (I can't specify it exactly yet)

Solved

9 Replies

Railway
BOT

10 months ago

Hey there! We've found the following might help you get unblocked faster:

If you find the answer from one of these, please let us know by solving the thread!


kravetsone
PROOP

10 months ago

It has finally started, but it cannot establish a connection

but in logs

2025-09-10 10:18:25.886 UTC [29] LOG: database system was not properly shut down; automatic recovery in progress

2025-09-10 10:19:15.907 UTC [29] LOG: redo starts at 1/87F3BDF8

2025-09-10 10:19:15.907 UTC [29] LOG: invalid record length at 1/87F3BE30: expected at least 24, got 0

2025-09-10 10:19:15.907 UTC [29] LOG: redo done at 1/87F3BDF8 system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s

2025-09-10 10:19:29.188 UTC [29] LOG: resetting unlogged relations (init), elapsed time: 13.28 s, current path: base/4

2025-09-10 10:25:40.050 UTC [27] LOG: checkpoint starting: end-of-recovery immediate wait

2025-09-10 10:30:51.309 UTC [27] LOG: checkpoint complete: wrote 2 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=49.805 s, sync=12.102 s, total=363.466 s; sync files=3, longest=6.073 s, average=4.034 s; distance=0 kB, estimate=0 kB; lsn=1/87F3BE30, redo lsn=1/87F3BE30

2025-09-10 10:31:02.044 UTC [6] LOG: database system is ready to accept connections

So it should...


kravetsone
PROOP

10 months ago

Okay now it works after MANY hours


qasimj
PRO

10 months ago

how was this solved? I am having the same issue


qasimj

how was this solved? I am having the same issue

10 months ago

Can you share a link to your Postgres service please?

Apologies for the delay here, we were in the middle of investigating and fixing this.


Status changed to Awaiting User Response Railway 10 months ago


ray-chen

Can you share a link to your Postgres service please? Apologies for the delay here, we were in the middle of investigating and fixing this.

qasimj
PRO

10 months ago

postgres-staging-639e.up.railway.app

seems to now deploy but wont connect to database


Status changed to Awaiting Railway Response Railway 10 months ago


Railway
BOT

10 months ago

Hello!

We're acknowledging your issue and attaching a ticket to this thread.

We don't have an ETA for it, but, our engineering team will take a look and you will be updated as we update the ticket.

Please reply to this thread if you have any questions!


10 months ago

Ticket attached and escalated internally!


Status changed to Awaiting User Response Railway 10 months ago


Railway
BOT

10 months ago

✅ The ticket Storage access issue has been marked as completed.


Railway
BOT

9 months ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway 9 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...