My database suddenly stopped working. I didn't have any backups, but I created some manually. I tried to recreate a new volume, but the build doesn't complete. What could have happened? Can anyone help me?

problem with postgres database - Railway Central Station

prodrigocostavieira

PROOP

11 days ago

I have the backups but I can't restore them.

Attachments

image.png

Status changed to Open Railway • 11 days ago

0x5b62656e5d

MODERATOR

11 days ago

Can you describe "stopped working"? Can you provide build or deploy logs?

prodrigocostavieira

PROOP

11 days ago

sure!

2026-05-12 00:31:33.937 UTC [178] STATEMENT: SELECT COUNT(*) AS n FROM subscriptions

2026-05-12 00:31:34.065 UTC [178] ERROR: relation "refresh_tokens" does not exist at character 27

2026-05-12 00:31:34.065 UTC [178] STATEMENT: SELECT COUNT(*) AS n FROM refresh_tokens

2026-05-12 00:31:33.683 UTC [178] ERROR: relation "users" does not exist at character 27

2026-05-12 00:31:33.683 UTC [178] STATEMENT: SELECT COUNT(*) AS n FROM users

2026-05-12 00:31:33.809 UTC [178] ERROR: relation "payments" does not exist at character 27

2026-05-12 00:31:33.809 UTC [178] STATEMENT: SELECT COUNT(*) AS n FROM payments

2026-05-12 00:32:29.132 UTC [189] STATEMENT: /* railway:dataui / SET statement_timeout = '30s'; / railway:dataui / SELECT row_to_json(data)::text as json FROM (SELECT (SELECT json_agg(t) FROM (SELECT REPLACE(REPLACE(query, E'\n', ' '), E'\r', ' ') as query, calls, ROUND(total_exec_time::numeric, 2) as total_time, ROUND(mean_exec_time::numeric, 2) as mean_time, ROUND(max_exec_time::numeric, 2) as max_time, rows FROM pg_stat_statements s JOIN pg_database d ON s.dbid = d.oid WHERE d.datname = current_database() AND left(query, 21) != '/ railway:dataui */' AND query != 'SELECT pg_is_in_recovery()' ORDER BY total_exec_time DESC LIMIT 20) t) as queries, (SELECT stats_reset::text FROM pg_stat_statements_info LIMIT 1) as stats_reset) data

2026-05-12 00:32:29.132 UTC [189] ERROR: relation "pg_stat_statements" does not exist at character 378

Stopping Container

Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/f618bbca-412d-4eb2-9e47-3736f3396caf/vol_wkr7ryo3m9l44m2w

Starting Container

2026-05-12 00:49:39.656 UTC [32] LOG: database system was interrupted; last known up at 2026-05-12 00:29:16 UTC

2026-05-12 00:49:40.023 UTC [32] LOG: database system was not properly shut down; automatic recovery in progress

2026-05-12 00:49:40.031 UTC [32] LOG: redo starts at 0/1959190

2026-05-12 00:49:40.031 UTC [32] LOG: invalid record length at 0/19592D0: expected at least 24, got 0

Certificate will not expire

2026-05-12 00:49:40.031 UTC [32] LOG: redo done at 0/1959298 system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s

pgbackrest: restore-gate WAL_RECOVER_FROM_BUCKET= POSTGRES_RECOVERY_TARGET_TIME= PG_VERSION=present RESTORED_MARKER=missing PGDATA=/var/lib/postgresql/data/pgdata

2026-05-12 00:49:40.037 UTC [30] LOG: checkpoint starting: end-of-recovery immediate wait

PostgreSQL Database directory appears to contain a database; Skipping initialization

2026-05-12 00:49:40.055 UTC [30] LOG: checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.005 s, sync=0.002 s, total=0.021 s; sync files=2, longest=0.002 s, average=0.001 s; distance=0 kB, estimate=0 kB; lsn=0/19592D0, redo lsn=0/19592D0

2026-05-12 00:49:39.639 UTC [9] LOG: starting PostgreSQL 17.9 (Debian 17.9-1.pgdg13+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 14.2.0-19) 14.2.0, 64-bit

2026-05-12 00:49:39.639 UTC [9] LOG: listening on IPv4 address "0.0.0.0", port 5432

2026-05-12 00:49:39.639 UTC [9] LOG: listening on IPv6 address "::", port 5432

2026-05-12 00:49:39.647 UTC [9] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"