a year ago
Our deployment powered by the marketplace mattermost extension is failing with 'Failed to ping DB' after 3 SQL Pings. We haven't changed anything in te initial deployment and everything was working well just until the most recent deployment to change a couple of settings on Railway side.
ⓘ Deployment information is only viewable by project members and Railway employees.
8 Replies
a year ago
It looks like there is a db shutdownevent that happens before the ping sql event in the logs.
Attachments
a year ago
Hi Brody,
I had enabled the new proxy and static IP in the settings but nothing was changed in the variables, etc. Now while trying to restart a older deployment, same thing is happening but the Postgres instance and the volume attached to it look to be in ok order.
a year ago
Sorry looks like the video link is down, trying to attach the video as a file
Attachments
a year ago
Actually I see that in the Postgres deployment the Database Connection is stuck on connecting to database. I have redeployed the whole instance.
Attachments
a year ago
Nothing looks wrong with the Postgres logs, please keep in mind that red does not always mean errors, and you should consider the contents of the logs when determining if a log is an error or not.
I would also never trust anything the data tab says, always verify the database connections with a database GUI tool like dbgate.
So please go ahead and test a database connection with dbgate.
Status changed to Solved jake • 5 months ago