Confluence Fails to Start with LuceneException
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Symptoms
Confluence 3.0.x fail to start and the following is reported in atlassian-confluence.log:
1
2
3
4
5
6
7
8
9
10
11
2009-10-08 20:04:33,048 ERROR [main\] [springframework.web.context.ContextLoader\] initWebApplicationContext Context initialization failed
:
: <skipped>
Caused by: com.atlassian.bonnie.LuceneException: Failed to create searcher for directory: org.apache.lucene.store.FSDirectory@/<your confluence home folder>/index
at com.atlassian.bonnie.LuceneConnection.createSearcher(LuceneConnection.java:486)
at com.atlassian.bonnie.LuceneConnection.<init>(LuceneConnection.java:92)
at com.atlassian.bonnie.LuceneConnection.<init>(LuceneConnection.java:107)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
Cause
The Application Server is not able to create searcher for the indices due to some file system permission.
Resolution
See How to Rebuild the Content Indexes From Scratch on Unclustered Confluence.
Was this helpful?