I am running discourse on a self-hosted server. Earlier it was working fine but when I updated the discourse to the latest one I saw my discourse jobs were tucked in the queue for a very long time and not processed.
All the email, webhook, and notification jobs are stuck. Can anyone have any idea how to fix this since I am not to get what is wrong?
@RGJ
This is screen showing which is visible when I click on the busy screen
I am now having the same issue, but in my case it started happening after I increased the memory on my instance. I restarted the sidekiq process which did clear out the queue, but that wasn’t a permanent solution unfortunately.
The only logs that exist are sidekiq restarting because of a lack of memory (also is 500MB RSS normal for a small site with ~20 jobs in queue?) but those are spaced 30-60 minutes apart so I doubt that has much relation.
Screenshot of my busy queue:
