Replies: 1 comment 1 reply
|
Hi @saltcod , sorry to tag you directly. I saw you resolved #45958, which was the same error on a free project (57P03 / Hot standby mode is disabled, disk full). Mine (ref xfkoywnrbbirsyzktriz) is stuck in the same crash loop and won't start. Would you be able to take a look, or point me to the right person? I'll delete the excess rows the moment it accepts connections. Thank you. |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
My free-tier project is down and stuck in a crash-recovery loop. It will not accept any connections (the SQL Editor and all clients fail). This is a personal hobby project on the Free plan.
Project ref: xfkoywnrbbirsyzktriz (eu-central-1)
Error returned by the SQL Editor and every client:
FATAL: 57P03: the database system is not accepting connections
Hot standby mode is disabled.
The Postgres logs show the same cycle repeating forever: recovery replays WAL and finishes, then the startup process fails because the disk is full at the WAL level, so it can never create the next WAL segment to finish starting:
LOG: database system was not properly shut down; automatic recovery in progress
LOG: redo done at D7/F5FFFE90
FATAL: could not write to file "pg_wal/xlogtemp.NNNN": No space left on device
LOG: startup process exited with exit code 1
LOG: shutting down due to startup process failure
How it started: I was over my usage quota, so I began deleting rows from a large table to reduce the database size. The deletes generated more WAL than the free disk could hold, the disk filled up, and it has been in this loop ever since (started around 16:25 UTC on 2026-07-30).
What I have already tried, with no change:
I understand disk scaling is Pro-only and that this has to be fixed server-side. I saw discussion Project Unhealthy - Disk 92% - 57P03 Hot standby mode disabled (Free tier) #45958, which had the same 57P03 / Hot standby mode is disabled error on a free project and was resolved server-side the same day. Could someone from the team please expand the disk or free the WAL space so the instance can finish starting? The moment it accepts connections I will immediately delete the excess rows to get back under the quota. I just need it to come up. Thank you.
All reactions