We had a null pointer exception the other day in Crucible which seemed to indicate a corrupt index. We cleared the cache directory and restarted Crucible which launched a full scan/index. After about 8 hours scanning the largest repo, there's a shutdown request in the log. What would be causing a shutdown during the scan? We've restarted twice and the same thing happens. After about 8 hours, it shuts down. Please help.
2016-05-05 01:08:36,132 INFO [Thread-1 ] fisheye ShutdownService-stopImpl - Shutdown requested
2016-05-05 01:08:37,213 INFO [InitPing2 DEV ] fisheye BaseRepositoryScanner-ping - done slurp for /DEV time = 26495758ms
2016-05-05 01:08:37,897 INFO [Thread-1 ] / ContextHandler$Context-log - org.tuckey.web.filters.urlrewrite.UrlRewriteFilter INFO: destroy called
There are few ways to stop FishEye: one can use stop.sh script, use UI (Admin / System Settings / Shutdown) or send TERM signal to the JVM. I'd suggest enabling Debug mode on (Admin / Server / Turn Debug on) so you may find more details what is the source of this shutdown request.
...word of mouth, so by 2016, we were working with several other entities on campus to implement Jira Service Desk . The Atlassian motto of “for every team” has really come true for us in this case. We...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot