Recently updated on Dashboard is not updating

[Sue Hallwood]

although there have been many updates our clients production wiki over the weekend Recently Updated on the dashboards doesnt show any updates after Sept 16. I have looked at the plugins and they seem to be ok. They are using Confluence 3.5.1. additionally new pages are not showing in search.

Could i get some help to troubleshoot this issue or can i be directed to any support issues already created for this issue?

[David at David Simpson Apps · Accepted solution]

Maybe you now need to take a larger mallet to your index. Delete and reindexing from scratch? Do you have much content to reindex?

[Sue Hallwood]

There is a fair amount as this is the clients main instance of Confluence. We are checking to see if Confluence is running out of memory or disk space as this will also have to be resoled in order to fix the indexing issue.

[Jeremy Largman]

Hi Sue,

Yes, it could indeed be OutOfMemory. Here's the knowledge base article on this.

[Sue Hallwood]

I have also added the com.atlassian.confluence.search.lucene package to logging and set it to DEBUG. I am waiting to hear from one of my team members to restart Confluence so the looging of the package will take affect as I do not have that kind of access to the server.

[Jeremy Largman]

It sounds like you have access to the admin console. If you're have "Atlassian Support Tools" (depends on your version - you might need to install the support tools plugin), you can run Hercules to scan your logs (log scanner). He might identify that knowledge base article I linked above (or a similar one). It's worth a shot!

[Sue Hallwood]

I do have access to the admin console as I am a confluence-Administrator with site-wide permissions. Thanks I will try instalingl the support tools plugin if it isnt already as we just recently upgraded to Confluence 3.5.11 and run the scan.

[Sue Hallwood]

according to System Information in Confluence admin there is only 37% of the heap memory remaing. Once we have resolved the issue with the heap memory will we still need to recreated the index?

[Sue Hallwood]

These are the results:

Hercules didn't find any known problems in the following log file:

/var/confluence-data/logs/atlassian-confluence.log

If you're experiencing problems, please create a support request using the Support Request feature or visit http://support.atlassian.com/.

Do I need to wait until Confluence has been restarted?

[Sue Hallwood]

I read the article at the link you gave me above and I guess i do need to recreate the index after allocating more memory.

[Jeremy Largman]

At this point David's original comment is correct. You'll want to re-index from scratch.

This is definitely a known issue, so I'm a bit surprised there isn't an Out Of Memory error. It might be in an old log. If you get with your administrator, make sure s/he looks through all the old logs for the text 'OutOfMemory'. We've seen this issue a lot and it's usually this cause.

[Sue Hallwood]

Thanks for all your help. My team member is resolving the memory issue right now and we are planning on recreating the indexes at 8pm when there are no users logged into the system.

[Sue Hallwood]

Thanks for all your help. Allocating more memory and re-creating the index has fixed the problem.

[David at David Simpson Apps]

This likely points to a problem with the Content Indexing.

Browse to:

Confluence Admin | Administration | Content Indexing

Check the Queue Contents tab for problems with the indexing queue and maybe even rebuild the search index.

Note: A full rebuild can take a long time depending on the size of your Confluence instance.

[Sue Hallwood]

Will rebuilding the search index affect any users currently logged into the system?

[David at David Simpson Apps]

It shouldn't drastically change things. If this doesn't fix your problem, then next step is to remove the index and rebuild it from scratch. This will mean until the index is rebuilt, you will have no search index, so functionality that depends on it (e.g. recently updated, the search and certain parts of the editor) will be affected.

[Sue Hallwood]

rebuilding seemed to fix the issue with recently updated and the site search but today it is not updating again. I notice that even though I have rebuilt the search index twice now I still see:

Queue is currently idle

Queue Last Processed

StartedSep 16, 2011 16:33

Time taken 48ms

Tasks processed 3

Index recreated NO

Index optimised NO

What would have caused the the queue to go idle and does this mean I need to remove the index and rebiuld it from scracth?