renai reported that their Discourse forum at http://forum.delimiter.com.au was showing an error: “Sidekiq is not running,” which prevents background tasks like email delivery. fefrei suggested checking logs and the /sidekiq page, noting errors like “Sidekiq heartbeat test failed” and JavaScript issues renai confirmed. fefrei recommended rebuilding the Discourse container via SSH with ./launcher rebuild app, predicting the queued jobs would clear afterward. After rebuilding, renai confirmed the error disappeared and previously delayed notifications appeared, indicating Sidekiq had resumed processing. fefrei explained this was expected — queued emails and notifications were now being delivered. renai speculated that the outage may have caused reduced forum activity and thanked fefrei for the help. The fix was successful, though both hope the issue doesn’t recur.
Firstly, Discourse rocks. Best forum software ever. Thanks so much for creating and supporting it!
Secondly, I have a small bug. I have a Discourse instance at http://forum.delimiter.com.au. It was installed in a DigitalOcean droplet by the Discourse team for me.
Everything has been performing fine for months, but recently I’ve been getting the following error:
“Some problems have been found with your installation of Discourse: Sidekiq is not running. Many tasks, like sending emails, are executed asynchronously by sidekiq. Please ensure at least one sidekiq process is running. Learn about Sidekiq here.”
I just rebuilt as per your instructions, and yeah – the error is gone. Also, a bunch of notifications which I hadn’t previously received popped up on my icon on the top right, so it seems like things are flowing again.
Much appreciated for your help! Will post again if there are any further issues.
I should have paid more attention.