Database DOWN -Error: connect ECONNREFUSED 2600
My database (project) went down completely last night while adding a column to a table.
Full Error:
Failed to retrieve available integrations
Error: connect ECONNREFUSED 2600:1f16:1cd0:3323:43fe:6ed2:2290:6472:5432
Try refreshing your browser, but if the issue persists for more than a few minutes, please reach out to us via support.
Any ideas? (I created ticket SU-254095 last night too.)
15 Replies
Does the dashboard work?
What is the status (upper right of main project page)?
Have you restarted the project?
Project overview works but doesn't show anything useful.
API Gateway shows a lot of 503 on health check.
Table editor just shows that error.
running a query in the SQL editor shows: Error: connect ECONNREFUSED
Project status is yellow - no tables, functions. (See image)
I have restarted the project 2ce
Your instance is stuck/down. If the restarting did not fix it then support is only way.
What region is it in?
You could also check your usage info in settings to make sure not over something.
I figured.
aws-0-us-east-2.pooler.supabase.com
Also check your Postgres logs and see if there is any useful error as it tries to come up.
It seems to be trying to fix iteslf
So you are using orioledb version?
This is my Dev DB so I think I tried that. Honestly I haven't looked into what that is doing for me.
Breaking? 😎
Sorry.
It is alpha so could have problems, but that is not to say this is the issue.
Ok, maybe I will start trying to create a new instance assuming the worst.
Do you think I could increase max_worker_processes using the cli when the database is in this condition?
If so, I will look for the syntax unless you know it.
Sorry, not something I know about.
Thanks for trying to help Gary
So I was talking to SB about Orioledb and if it might be an issue. It is not related to the overall elevated issues users have been seeing with hangs/server lockups.
So no idea if yours is just an Orioledb thing or something related to the other stuff going on.
But the general feel I got was unless you are looking or need some performance feature Orioledb offers you should not be using it. Support may even just punt and say alpha things happen (my comment not theirs).
So I don't think a bad move would be to move your stuff to another instance anyways.