Jobs Stuck in Enqueue state (Enqueued Actionmailer) about sidekiq HOT 20 CLOSED

Is Sidekiq running?

from sidekiq.

Yes Mike, it is

from sidekiq.

Note: We rolled back to an earlier version of Ruby to 2.7 and this worked again.

from sidekiq.

And what does its logs show?

from sidekiq.

Mike, can you see the image that I've supplied? We are stuck in 'enqueued'. I'm no expert in this by the way, I've just picked up an issue that seems to suggest we are stuck at Sidekiq.

from sidekiq.

Those logs appear to be from your app server, eg puma. I’m asking about sidekiq’s log output.

and your image is in the middle of your initializer code so that’s not correct either. For instance I can’t tell what the “sidekiq_config” variable is.

from sidekiq.

Mike,, does this help?

from sidekiq.

It does answer that question. Now I want to see your Sidekiq logs from the same timestamps as that first log image.

from sidekiq.

Cool. So we rolled back a release early this morning.
No-one could find any sidekiq log yesterday, and if they are created on the service startup, perhaps if the start failed, this is why, leading me to suspect this is the reason the jobs stayed in the enqueued state. I've asked if the logs are now visible since we have rolled back and resolved the immediate issue.
Would this stack up with your expertise?

from sidekiq.

That scenario makes sense to me. The most common reason jobs pile up in a queue is because Sidekiq isn't running for some reason.

from sidekiq.

OK, thanks for the reply, that helps. I'll check my end to see if someone can find the production logs.
May I ask, given the versions we are running, should we move to a newer version do you think? Sorry if this is a dumb question by the way, I am new to your product...

from sidekiq.

7.0 is roughly 18 months old. 7.2.4 is the latest. I always default to using the latest but I don't know the state of your app so I can't give any advice for sure.

from sidekiq.

Appreciate that. We are Rails 7.1, Ruby changed from 3.0 to 3.0.6 (Just now). I'll move to 7.2.4 and see what happens. Thank you.

from sidekiq.

Hi Mike
I've pushed a change out to our sidekiq.yml specifying a log file. We can't find it, and we have redeployed our failed release to a lower environment. Please can you advise?

:verbose: true
:concurrency: 10

:timeout: 30

:queues:

• critical
• default
• mailers
• blast_messages
• credentialing
• compliance
• compliance_snapshotting

development:
:verbose: true
:logfile: ./log/sidekiq_development.log

demo:
:verbose: true
:logfile: ./log/sidekiq_demo.log

production:
:concurrency: 25

from sidekiq.

If you don't know where your log files are, that tells me you're going to need a hell of a lot of help, which I can't do over github issues. Can you show up to my Office Hour in 15 minutes? https://sidekiq.org/support.html

from sidekiq.

from sidekiq.

I don’t provide private help to non-customers. My public Office Hour is your only option. I would strongly recommend reading through the various topics in the wiki if you’re not knowledgeable about Sidekiq.

from sidekiq.

from sidekiq.

Office Hour: https://sidekiq.org/support.html

from sidekiq.

This issue is not closed, and I am still stuck. Please help.

from sidekiq.