3 months ago
New error and I have seen it twice today. Potentially some networking blips but want to make sure this isn't a leaky bucket somewhere.
ActiveRecord::NoDatabaseError
We could not find your database: railway. Available database configurations can be found in config/database.yml. (ActiveRecord::NoDatabaseError)
To resolve this error:
- Did you not create the database, or did you delete it? To create the database, run:
bin/rails db:create
- Has the database name changed? Verify that config/database.yml contains the correct database name.2 Replies
2 months ago
The ActiveRecord::NoDatabaseError here is misleading. Rails raises this when it can't establish a connection to Postgres at all, not because the database was actually deleted. It tries to connect, gets a transient failure, and interprets it as "database not found."
Since it's happened twice today and recovered on its own, this points to brief network blips between your sidekiq service and Postgres rather than a persistent issue. Rails' connection pool will auto-recover from these.
I also noticed your Postgres instance is logging collation version mismatch warnings (created with glibc 2.36, now running 2.41). This is cosmetic and not related to the connection blips, but you can clean it up by running:
ALTER DATABASE railway REFRESH COLLATION VERSION;If the frequency increases or you start seeing actual job failures, let us know and we can dig deeper into the networking side.
Status changed to Awaiting User Response Railway • 2 months ago
2 months ago
Thank you, Sam. Just wanted to call it out in case it was something bigger.
Status changed to Awaiting Railway Response Railway • 2 months ago
Status changed to Solved sam-a • 2 months ago