No workers after I migrated from 1.0.0

[diegocharles]

Hey everyone!

I’m facing an issue that hasn’t been resolved since upgrading from version 1.0.0. The jobs are getting stuck, and when I manage them through MissionControl, I don’t see any workers.

Here’s my stack:

• Rails 8
• Kamal 2
• Hertzer:
  • Web server
  • Job server
  • Database server

The solid_queue tables are managed by PostgreSQL, and this is how my queue.yml looks:

  dispatchers:
    - polling_interval: 1
      batch_size: 500
      concurrency_maintenance_interval: 300

  workers:
    - queues: “*”
      threads: 3
      polling_interval: 2
    - queues: [ real_time, background ]
      threads: 5
      polling_interval: 0.1
      processes: 3

Thanks in advance

[rosa]

Hey @diegocharles, how are you starting Solid Queue?

[diegocharles]

Hey Rosa!

I believe Kamal 2 starts it, because I don’t have any explicit calls for production like I do for development in the Procfile.dev.

jobs: bin/rails solid_queue:start

Thanks for your help.

[rosa]

@diegocharles that sounds like you're using the Puma plugin to run Solid Queue supervised by Puma, wherever you're running your web app. Do you have logs for when your production server starts?