Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Health check failed,Index error Lucene

史海坤 I'm New Here Feb 19, 2021

error log:

Exception during health check invocation com.atlassian.util.concurrent.LazyReference$InitializationException: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'tenantedLuceneConnection' defined in class path resource [indexingSubsystemContext.xml]: Bean instantiation via constructor failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.atlassian.bonnie.LuceneConnection]: Constructor threw exception; nested exception is com.atlassian.bonnie.LuceneException: java.io.FileNotFoundException: /var/atlassian/application-data/confluence/index/segments_6c (Permission denied)

 

I don't know what to do

2 answers

0 votes
Pramodh Community Leader Feb 19, 2021
0 votes

Note the "Permission denied" in the error message.  This almost certainly means the index files or directories have the wrong permissions on them, and the user running Confluence does not have the read/write/execute/delete access it requires

This usually happens when someone (re)starts Confluence as the wrong user (usually root), and that user takes ownership of any files it writes to, which then locks the correct user out of them.  When the correct user is used to start Confluence next time, it can't access the files it needs.

Check the ownership and permissions of the files in the home and install directories first.  If you do have this case, you then need to stop Confluence, change ownership or permissions of the files, restart Confluence and then visit Admin -> Indexing and run a full re-index

Note that although I've said to look at ownership and permissions, in 99.9999% of cases, it is just ownership - root or your user will have taken ownership of *some* of the files, and the command chown -R confluence:confluence run against confluence-home and confluence-install will fix it without needing to touch the rwx flags (assumes you have a user called "confluence" for running Confluence!)

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Confluence Cloud

Get to know the Confluence team!

Go “behind the screen” to meet some of the Confluence Cloud team. In this video series, we tackle some of the hard-hitting questions you never knew you wanted the answer to!  Meet some of the ...

236 views 0 10
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you