2 months ago
Postgres instance has crashed and is unable to recover on its own. No changes were to done to DB config.
In that I have received message saying "Postgres in project heartfelt-energy is affected by CVE-2026-15741, CVE-2026-18408, CVE-2026-6464, CVE-2026-14663, CVE-2026-14672, CVE-2026-18024, CVE-2026-6470, CVE-2026-14666, CVE-2026-14681, CVE-2026-16241, CVE-2026-6469. " What is this ? were you compromised ? Can I get an reply and fix on this at the earliest ?
2026-08-20T04:31:23.781310882Z [err] 2026-08-20 04:31:23.777 UTC [56] LOG: database system was interrupted while in recovery at 2026-08-20 04:31:16 UTC
2026-08-20T04:31:23.781313782Z [err] 2026-08-20 04:31:23.777 UTC [56] HINT: This probably means that some data is corrupted and you will have to use the last backup for recovery.
2026-08-20T04:31:23.836952678Z [inf] Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/e0827f7f-3cc0-4bfb-9d44-04e64c4977fd/vol_mz1d4nl4cvbxl1e8
2026-08-20T04:31:24.556089631Z [err] 2026-08-20 04:31:24.336 UTC [56] LOG: database system was not properly shut down; automatic recovery in progress
2026-08-20T04:31:24.556092952Z [err] 2026-08-20 04:31:24.340 UTC [56] LOG: redo starts at 2/DBB03F10
2026-08-20T04:31:24.598878772Z [err] 2026-08-20 04:31:24.591 UTC [57] FATAL: the database system is not yet accepting connections
2026-08-20T04:31:24.598883741Z [err] 2026-08-20 04:31:24.591 UTC [57] DETAIL: Consistent recovery state has not been yet reached.
2026-08-20T04:31:25.754456871Z [err] 2026-08-20 04:31:25.726 UTC [64] FATAL: the database system is not yet accepting connections
2026-08-20T04:31:25.754460073Z [err] 2026-08-20 04:31:25.726 UTC [64] DETAIL: Consistent recovery state has not been yet reached.
2026-08-20T04:31:27.678585024Z [err] 2026-08-20 04:31:27.334 UTC [66] FATAL: the database system is not yet accepting connections
2026-08-20T04:31:27.678589367Z [err] 2026-08-20 04:31:27.334 UTC [66] DETAIL: Consistent recovery state has not been yet reached.
2026-08-20T04:31:27.759386748Z [err] 2026-08-20 04:31:27.753 UTC [73] FATAL: the database system is not yet accepting connections
2026-08-20T04:31:27.759393038Z [err] 2026-08-20 04:31:27.753 UTC [73] DETAIL: Consistent recovery state has not been yet reached.
2026-08-20T04:31:29.666699235Z [err] 2026-08-20 04:31:29.662 UTC [56] LOG: redo done at 2/E0FFFF80 system usage: CPU: user: 0.13 s, system: 0.07 s, elapsed: 5.32 s
2026-08-20T04:31:29.692314768Z [err] 2026-08-20 04:31:29.685 UTC [56] FATAL: could not write to file "pg_wal/xlogtemp.56": No space left on device
2026-08-20T04:31:29.692319324Z [err] 2026-08-20 04:31:29.688 UTC [26] LOG: startup process (PID 56) exited with exit code 1
2026-08-20T04:31:29.692322309Z [err] 2026-08-20 04:31:29.688 UTC [26] LOG: terminating any other active server processes
2026-08-20T04:31:29.692325586Z [err] 2026-08-20 04:31:29.689 UTC [26] LOG: shutting down due to startup process failure
2026-08-20T04:31:29.699304721Z [err] 2026-08-20 04:31:29.696 UTC [26] LOG: database system is shut down
1 Replies
2 months ago
Your Postgres volume is at 482 MB of its 500 MB capacity, and the crash log confirms Postgres cannot complete WAL recovery because there is no space left on the device. You can resize the volume up to 5 GB from the volume settings in your project (Hobby plan cap), which will give Postgres the room it needs to finish recovery and start accepting connections. Regarding the CVE notification, that was a routine security patch we applied to your Postgres image to address known vulnerabilities in the upstream software - it is not a compromise of our systems.
Status changed to Awaiting User Response Railway • about 2 months ago
a month 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 • about 1 month ago