3 months ago
I was having issue so restarted my db instance, which was getting stuck on the initial volume mount.
Then i redeployed it :
Mounting volume on: /../vol_u82yb79ah1...
Mounting volume on: /../vol_u82yb79ah1...
Mounting volume on: /../vol_u82yb79ah1...
Mounting volume on: /../vol_u82yb79ah1...
Mounting volume on: /../vol_u82yb79ah1...
Starting ContainerI can not connect anymore
error: connect ECONNREFUSED fd12:eb37:73dc:0:1000:6:c3b8:5029:54327 Replies
Starting Container
PostgreSQL Database directory appears to contain a database; Skipping initialization
2025-09-09 11:54:43.010 UTC [1] LOG: starting PostgreSQL 16.9 (Debian 16.9-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
2025-09-09 11:54:43.012 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
2025-09-09 11:54:43.012 UTC [1] LOG: listening on IPv6 address "::", port 5432
2025-09-09 11:54:43.410 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2025-09-09 11:54:43.948 UTC [24] LOG: database system was interrupted; last known up at 2025-09-09 11:20:51 UTC
2025-09-09 11:54:47.185 UTC [24] LOG: database system was not properly shut down; automatic recovery in progress
2025-09-09 11:54:48.943 UTC [24] LOG: redo starts at 0/85EAE50
2025-09-09 11:54:49.515 UTC [24] LOG: invalid record length at 0/860D648: expected at least 24, got 0
2025-09-09 11:54:49.515 UTC [24] LOG: redo done at 0/860D610 system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.57 s
2025-09-09 11:54:53.146 UTC [22] LOG: checkpoint starting: end-of-recovery immediate wait
2025-09-09 11:55:29.907 UTC [22] LOG: checkpoint complete: wrote 23 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=6.161 s, sync=21.277 s, total=38.610 s; sync files=10, longest=5.460 s, average=2.128 s; distance=137 kB, estimate=137 kB; lsn=0/860D648, redo lsn=0/860D648
2025-09-09 11:55:31.938 UTC [1] LOG: database system is ready to accept connectionsAlthough i can no reach it 🙁
disclosure:
I was debugging a slow query and ran -
ALTER SYSTEM SET shared_buffers = '1GB';
ALTER SYSTEM SET work_mem = '64MB';
ALTER SYSTEM SET maintenance_work_mem = '512MB';Prior to restart
3 months ago
I am using the Template from Railway
3 months ago
Its def some sort of disk corruption, I started a new template and tried to move a back up to it and its hanging.
3 months ago
Was able to fix it with a backup.
philliplakis
Was able to fix it with a backup.
3 months ago
So to clarify, this issue is solved?
3 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!
3 months ago
✅ The ticket Storage access issue has been marked as completed.