It wasn't "stuck", it was indexing things it can't pre-count (it can count issues in Jiraissue, so it can estimate on them, but that is not everything it needs to index).
By killing it part way through, it's likely that you have corrupted the index. But it could be something else too. You'll need to read the logs of the new start to see what the internal server error is, then fix that, restart, and re-index in full without killing it again.
thank you Nic.
but it was in the same state for almost 3 hours... so i restarted....
can you tell me which log i need to go through or provide you?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Have a look at
<jira home>/logs/atlassian-jira.log
then, if that is empty or not showing you errors
<jira install>/log/catalina.log
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.