Redis-cli command to check sidekiq process

AI-generated summary

In a support thread titled “Redis-cli command to check sidekiq process,” pfaffman is running a site import to a new Standard Hosting account using a future hostname, which blocks web interface access. They want to verify via redis-cli whether Sidekiq background jobs have finished before uploading the backup. In post 2, they note that keys "*failed*" returns many failed job keys, suggesting jobs are still active. riking advises using a temporary, controllable hostname (e.g., customer72.import.literatecomputing.com) to avoid domain issues, which pfaffman acknowledges as their usual practice — realizing that jumping straight to the final hostname was unnecessary since the client will remap anyway. They remain mildly curious about checking queued jobs via Redis but admit they can’t think of a practical use case. riking suggests examining the Sidekiq web UI code if they’re still curious. The thread ends with a pragmatic resolution: use a temporary hostname to avoid complications, and the Redis check becomes unnecessary for real-world workflow.

I’m running an import right now to upload to a new Standard Hosting account. It’ll likely be finished before I finish this message.

I’m running it with the hostname set that the site will have, so I can’t access the web interface since it’s for a different domain. I’d like to wait for sidekiq to finish before I take the backup to upload it.

Can I do a redis-cli comand to check that the sidekiq processes have finished?

Well, a "keys “failed” is returning a bunch (oh, 214) of lines like:

200) "sidekiq:stat:failed:2019-08-07"

Maybe I should just run it with a bogus hostname and let that be your problem. :man_shrugging:

Use a temporary hostname you control (e.g. customer72.import.literatecomputing.com) so that a remap fixes it all.

That’s what I usually do. I was thinking that it might save a step to go straight to your hostname, but that was wrong. And since they’re going to change the hostname from their temp host name to the real one anyway, and they haven’t yet set up that domain. . . .

Thanks anyway.

Still mildly curious how to see if jobs are queued, but I now cannot think of a situation where it’ll be helpful to know. :slight_smile:

If you’re really curious, I suppose you could pull that out of the Sidekiq web UI code?