6 months ago
TLDR: My postgre db is unresponsive and i can't redeploy.. all my redeploy attempts fail after 20/30 mins with 0 logs from deployment attempt...
I'm trying to debug the memory spike issue in my postgres db and redeployed my db a couple hours ago with no problem. Just about half an hour ago i tried redeploying the db service but it just keeps failing without providing me any single logs.. I can't even see the logs of the attempted deployment...
Some things i did while i was trying to debug my db memory issue was:
- add pg_stat_statements extension to my db with:
CREATE EXTENSION IF NOT EXISTS pg_stat_statements;sshed into the db service on Railway and tried monitoring memory usage, for that i manually installed
htopthereused queries like below to understand the open connections and memory consumtions of queries:
SELECT pid, usename, datname, state, query_start, now() - query_start as query_duration, query, -- Memory usage (requires track_activities = on) backend_type, wait_event_type, wait_event FROM pg_stat_activity WHERE state = 'active' AND query NOT LIKE '%pg_stat_activity%' ORDER BY query_start;I don't know if this was dues to the control panel outage Railway had this morning that resulted in deployments being blocked, or my manual attempts of trying to debug my memory problem.... I still currently cant redeploy my db and the db is not responsive right now, rejecting all the connection requests..
3 Replies
6 months ago
Hey there! We've found the following might help you get unblocked faster:
If you find the answer from one of these, please let us know by solving the thread!
6 months ago
Hello!
We've escalated your issue to our engineering team.
We aim to provide an update within 1 business day.
Please reply to this thread if you have any questions!
Status changed to Awaiting User Response Railway • 6 months ago
6 months ago
Hello,
Looks like your deployment was in a locked phantom state. I have gone ahead and fixed this for you. Your database is back online and accessible, so I will mark this as solved. Going forward, we will look into how we can prevent this particular case in the future.
Best,
Brody
6 months ago
✅ The ticket Container not shutting down properly has been marked as completed.
Status changed to Solved brody • 6 months ago