You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
New rails 8.0.2 project with defaults. solid_queue (1.1.5). queue_schema.rb is generated. Using a separate queue DB. db:prepare does not load the schema for the queue db. Locally, I could do db:schema:load:queue, but in production (default kamal deployment) I get:
DISABLE_DATABASE_ENVIRONMENT_CHECK=1 bin/rails db:schema:load:queue
bin/rails aborted!
ActiveRecord::ConnectionNotEstablished: connection to server at "172.18.0.10", port 5432 failed: FATAL: password authentication failed for user "postgres" (ActiveRecord::ConnectionNotEstablished)
Caused by:
PG::ConnectionBad: connection to server at "172.18.0.10", port 5432 failed: FATAL: password authentication failed for user "postgres" (PG::ConnectionBad)
Tasks: TOP => db:schema:load:queue => db:test:purge:queue
(See full trace by running task with --trace)
It tries to purge the test db even though it's in production.
The text was updated successfully, but these errors were encountered:
@thisismydesign, looks like this is not related to Solid Queue, but to your DB configuration.
PG::ConnectionBad: connection to server at "172.18.0.10",
port 5432 failed: FATAL: password authentication failed for user "postgres"
(PG::ConnectionBad)
It seems you have configured the wrong credentials in database.yml.
It tries to run db:test:purge:queue, a task on the test DB, despite RAILS_ENV=production. Then it fails with an authentication error, because it can't authenticate to the prod db using the test config in database.yml.
But I guess that's a rails issue, not solid queue.
Uh oh!
There was an error while loading. Please reload this page.
New rails 8.0.2 project with defaults. solid_queue (1.1.5).
queue_schema.rb
is generated. Using a separate queue DB.db:prepare
does not load the schema for the queue db. Locally, I could dodb:schema:load:queue
, but in production (default kamal deployment) I get:It tries to purge the test db even though it's in production.
The text was updated successfully, but these errors were encountered: