Sidekiq queues not starting

[ch...@happenate.com]

I've got a sidekiq.yml file that looks like:

:concurrency: 5

:verbose: false

:queues:

  - [mailer, 5]

  - [default, 3]

  - [carrierwave, 3]

myshkin:

  :concurrency: 10

production:

  :concurrency: 25

And upon starting the rails app (using Guard) I check the web view (http://machine.local:3000/queues/queues) and only see a single queue, default.

I've tried starting queues directly with

$ bundle exec sidekiq -q mailer

and restart the server, but I am not seeing the mailer queue active.

I'd like some help figuring out what my next step is to debug/solve this problem.

[Mike Perham]

Queues don't show in the UI until something is put in them. 

--
You received this message because you are subscribed to the Google Groups "Sidekiq" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sidekiq+u...@googlegroups.com.
To post to this group, send email to sid...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sidekiq/a1d195cc-fc75-4587-bf36-2bacfeae63ba%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ch...@happenate.com]

On Thursday, August 14, 2014 11:20:41 AM UTC-4, Mike Perham wrote:

Queues don't show in the UI until something is put in them.

The default queue is always showing in the web ui after startup, without having added anything to its queue.
Default is treated differently than other queues in that respect?


What I'm trying to figure out is why the queues that are specified in the config file are not starting.

Other than looking in Redis for the existence of a queue (though that's likely the same source of info as the web view) I don't know how to verify that a queue exists.

[Mike Perham]

Queues are not created in Redis until something is put in them and the Web UI only shows created queues.  The default queue exists because presumably you've already created a job to test Sidekiq.  You can create a queue by creating a fake job in rails console:

Integer.delay(queue: 'mailer').foo

Now the mailer queue should show in the UI, just make sure you clear out that job.

--

You received this message because you are subscribed to the Google Groups "Sidekiq" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sidekiq+u...@googlegroups.com.
To post to this group, send email to sid...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/sidekiq/2dc5f6d3-8799-419c-b45d-61f49882ac41%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Mike Perham – Contributed Systems

Smart, effective open source infrastructure for your apps.

[ch...@happenate.com]

On Thursday, August 14, 2014 11:45:47 AM UTC-4, Mike Perham wrote:

Queues are not created in Redis until something is put in them and the Web UI only shows created queues.  The default queue exists because presumably you've already created a job to test Sidekiq.  You can create a queue by creating a fake job in rails console:

Integer.delay(queue: 'mailer').foo

Now the mailer queue should show in the UI, just make sure you clear out that job.

The problem lay in how I was adding jobs to queues, not with the setup.

Thank you for your troubleshooting suggestions and help.