My production database just failed.
kennymark
PROOP

3 months ago

Please help, I was looking at the database tab in the in my pg db when I decided to click the config, i was looking at the analysis on the db and it recommend i installed pg_stats_statements and now I can't view or connect to my db to fix the problem.

Screenshot_2026-02-08_at_19.45.02.png

Attachments

Solved

13 Replies

kennymark
PROOP

3 months ago

I need this fixed asap


kennymark
PROOP

3 months ago

@Medim can I please get some help


3 months ago

Please don't ping team members/conductors, please look at #🛂|readme 5)


kennymark
PROOP

3 months ago

Sorry


kennymark
PROOP

3 months ago

Any update?


3 months ago

I assume that this is related to https://discord.com/channels/713503345364697088/1467207292100415771, in short SSH into your service and remove the quotes. You can temporarily change your service's start command to something like sleep 100000000, so that there is enough time for you to SSH into it before it crashes.


kennymark
PROOP

3 months ago

I can't ssh, as the server is entirely crashing


3 months ago

Even after changing the start command to sleep 10000000000?


kennymark
PROOP

3 months ago

Its now working.. I am in the machine. I


kennymark
PROOP

3 months ago

Thanks


3 months ago

Can you share what was the fix to your issue?


kennymark
PROOP

3 months ago

Well.. I ssh'd into the machine after applying running sleep 100000000 in the start command, once inside the vps, i run this command sed -i.bak 's/^shared_preload_libraries/#shared_preload_libraries/' /var/lib/postgresql/data/pgdata/postgresql.auto.conf. It commented out the the line in the postgres config file responsible for the crash


kennymark
PROOP

3 months ago

Thats all


Status changed to Solved medim 3 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...