Forum updated, several bugs (sidekiq not running)

Our forum updated 2 days ago to the “February 2025 stable” version (not sure how to find the exact version number).

Our members have noticed several bugs:

  • People aren’t getting notifications for replies.
  • People are having to manually refresh the page to see replies
  • The “Who’s Online” plugin is misbehaving, saying there are over 50 people online when there definitely aren’t.

How can we fix this? Is there going to be a hot fix or something?

Thanks
Shaun

We haven’t seen these issues on our hosting, or from any other self-hosters, so this is likely a problem specific to your server. We don’t have any relevant fixes in the pipeline.

From the symptoms, it sounds like Sidekiq (the background job processor) is not running correctly.

Do you see any recent errors when visiting /logs on your forum?

How does /sidekiq look? Does it show jobs being processed?

1 Like

There are some recent errors:

Sidekiq looks like it’s working?

(Edit: actually I see it’s not working… never viewed this before lol)

I just got loads of notifications, seems it was stuck? Did visiting sidekiq give it a kick?

1 Like

Ah it seems my host replied to my message and they gave it a kick… I’ll see what they say. Thanks!!

2 Likes

Interesting! To be honest I’m surprised that visiting the dashboard would give it a kick, but it’s possible!

What do the numbers look like at the top of the dashboard:

In a healthy state, the ‘enqueued’ number should be close to zero. I suspect if things have been stuck, your number is very high, and may take some time to process down to 0.

Ah great!

1 Like

Sidekiq was (seemingly happily) running, but it seemed to be stuck since the update to 3.4 with about 1000 jobs queued. Since updates often do rebakes or async things, we didn’t really see that as something suspicious.

A restart of the process did the trick. I suspect the who’s online plugin might be the culprit but I’m not 100% sure.

1 Like

Likely unrelated, but we also bumped into something that may also be sidekiq misbehaving after a recent update.

Also,

Coincidence or not, one of our admins saw this in the last 24h, but I haven’t been able to reproduce it yet so it may have been a single glitch.