Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 21:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.
×Screen says: By default, the contents of the queue are processed every minute., but it is not running (items Queued For Next Processing Run just build up).
I can successfully hit the flush queue link and it works.
Confluence 4.1.4
Community moderators have prevented the ability to post new answers.
A standard reindex (suggested by Atlassian) did not work, but subsequently shutting down and restarting the server kicked it back into action.
Thanks for your kind help on this one!
Hi Steve, Did the restart cure this issue permanently ? Thanks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Steve,
As a first approach I would suggest you to perform the following approach:
* Stop your instance;
* Then remove the content from the following folders:
a) The <confluence-home>/bundled-plugins folder
b) The <confluence-home>/plugin-cache folder
c) The <confluence-home>/plugins-osgi-cache folder
d) The <confluence-home>/plugins-temp folder
* Perform the following tasks related with the indices from your instance:
1) Make a backup of your <confluence-home>/index/plugin directory if it exists. This is where the Usage Tracking plugin stores it's index for the usage statistics and it cannot be rebuilt.
2) Remove the <confluence-home>/index directory.
3) If in step 1, you have the <confluence-home>/index/plugin directory, create the <confluence-home>/index directory and copy in the backup of <confluence-home>/index/plugin directory made in step 2.
* Now start your instance;
* And finally rebuild your content indices by the following procedure:
https://confluence.atlassian.com/display/DOC/Content+Index+Administration#ContentIndexAdministration-RebuildingtheContentIndexes
After these steps please try to test and reproduce the behaviour. If doesn't help then please raise a support ticket at our support.atlassian.com and attach your latest 'atlassian-confluence.log' for a review, so we can take a better look to see what can be happening from the application side that is causing this behaviour.
Hope this helps.
Cheers,
LJ.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.