Urgent Lucene Exception Issue

[Dylan]

Hello,

Could you please advise how this issue:

TP-Processor13 ERROR [com.atlassian.bonnie.ConcurrentLuceneConnection] Error closing writer. java.io.FileNotFoundException: /opt/jira/indexes/comments/_4ubij.fnm (No such file or directory)
java.io.FileNotFoundException: /opt/jira/indexes/comments/_4ubij.fnm (No such file or directory)

Thread-228 ERROR [atlassian.core.user.UserUtils] [Ljava.lang.StackTraceElement;@258e5d0e

Thread-228 ERROR [event.listeners.search.IssueIndexListener] Error re-indexing changes for issue 'current issue'
com.atlassian.jira.issue.index.IndexException: com.atlassian.bonnie.LuceneException: org.apache.lucene.store.LockObtainFailedException: Lock obtain timed out: SimpleFSLock@/opt/jira/indexes/comments/write.lock

can be resolved in JIRA.

I've deleted the write.lock file from directory /opt/jira/indexes/comments/ and restarted JIRA but it did not help. The problem with Lucene still exists.

Please advise how this Lucene Exception can be resolved.

Regards,

Dylan

[tier-0 grump]

In these cases it's not enough to clear out the lock file - you nearly always have to delete the indexes and then reindex. If the problem persists, then you may have to up your open file limit, as this is often the root cause of files not being there, otherwise it's an early sign of hard disk failure...

[Joe Clark]

For urgent requests, you should use https://support.atlassian.com - our support site is staffed by dedicated support engineers across the globe and are able to assist immediately with "system down" issues in most timezones.

Answers.atlassian.com is a community site and we have no dedicated staff to ensure prompt responses to critical issues.

I did a search in our knowledge base and found a couple of articles that might be helpful:

• Accessing JIRA Isse Results in 'Error Re-indexing Changes for Issue'
• Unable to Rebuild JIRA Index