9b459aa5-09cd-4fcf-b1f0-f3826cfc5145

[2025-05-22 18:11:25.008] debug: ⛔️ Server wasn't able to start properly.

[2025-05-22 18:11:25.010] error: could not open file "global/pg_filenode.map": I/O error

error: could not open file "global/pg_filenode.map": I/O error

at Parser.parseErrorMessage (/app/node_modules/pg-protocol/dist/parser.js:287:98)

at Parser.handlePacket (/app/node_modules/pg-protocol/dist/parser.js:126:29)

at Parser.parse (/app/node_modules/pg-protocol/dist/parser.js:39:38)

at Socket. (/app/node_modules/pg-protocol/dist/index.js:11:42)

at Socket.emit (node:events:513:28)

at Socket.emit (node:domain:489:12)

at addChunk (node:internal/streams/readable:315:12)

at readableAddChunk (node:internal/streams/readable:289:9)

at Socket.Readable.push (node:internal/streams/readable:228:10)

at TCP.onStreamRead (node:internal/stream_base_commons:190:23)

I didnt reseive any answer for my question.

Railway Database Status Report

Connection Parameters

• Host: roundhouse.proxy.rlwy.net
• Port: 38750
• Database: railway
• User: railway
• Server IP Address: 35.214.158.190

Diagnostic Results

✅ Network Connection

• Port 38750 is accessible
• TCP connection establishes successfully
• DNS resolution works correctly

❌ Database Connection

Status: FAILED

Error:

FATAL: could not open file "global/pg_filenode.map": I/O error

Hi! Have you tried redeploying the DB?

No. I didn't touch anything. Should i try to redeploy postgress image?

And I would also like to understand what happened.

yes please

no clue, could be a random crash

let's try redeploying and observing what happens

The problem was solved after redeploying. But the point is that the database hadn't crashed - it's status was active.

I think it got redeployed to a metal region automatically (since we are on the migration period and you said it was active since 2024) and something made it crash, I don't think it will happen again.

If you could please check if all your data is intact

Hey @Katapult - looking into it.

There we're no deploys for your DB, that's the reason why there seems to be issues.