easyBI Configure attempt yields message: We're sorry, but something went wrong.

I've searched the JIRA installation directory logs subdirectory for log files with name localhost.*.log. This file does not exist.

Any suggestions?

1 answer

By localhost.*.log is meant log file which has current date in place of *. Don't you have any localhost.yyyy-mm-dd.log files in JIRA installation logs subdirectory?

And please better contact support@eazybi.com regarding this issue and we will help you to solve it.

Our files are on Unix, with names like atlassian-jira-log. I tried configuring again this morning (8:42am) and found no messages were placed in this log file.

Here's what was in the log:

2013-03-18 00:00:00,046 QuartzWorker-1 INFO ServiceRunner [issue.index.job.OptimizeIndexJob] Optimize Index Job running...

2013-03-18 00:00:00,046 QuartzWorker-1 INFO ServiceRunner [jira.util.index.CompositeIndexLifecycleManager] Optimize Indexes starting...

2013-03-18 00:00:00,058 QuartzWorker-1 INFO ServiceRunner [jira.util.index.CompositeIndexLifecycleManager] Optimize took: 11ms. Indexer: DefaultIndexManager: paths: [/data/atlassian/runtime/jira/caches/indexes/comments, /data/atlassian/runtime/jira/caches/indexes/issues, /data/atlassian/runtime/jira/caches/indexes/changes]

2013-03-18 00:00:00,058 QuartzWorker-1 INFO ServiceRunner [jira.util.index.CompositeIndexLifecycleManager] Optimize took: 0ms. Indexer: SharedEntityIndexManager: paths: []

2013-03-18 00:00:00,058 QuartzWorker-1 INFO ServiceRunner [jira.util.index.CompositeIndexLifecycleManager] Optimize Indexes complete. Total time: 11ms.

2013-03-18 00:00:00,058 QuartzWorker-1 INFO ServiceRunner [issue.index.job.OptimizeIndexJob] Indexes Optimized. Took: 11 milliseconds.

2013-03-18 00:00:00,058 QuartzWorker-1 INFO ServiceRunner [issue.index.job.OptimizeIndexJob] Optimize Index Job complete.

2013-03-18 00:36:22,106 QuartzWorker-1 INFO ServiceRunner Backup Service [jira.bc.dataimport.DefaultExportService] Data export completed in 8087ms. Wrote 441374 entities to export in memory.

2013-03-18 00:36:22,107 QuartzWorker-1 INFO ServiceRunner Backup Service [jira.bc.dataimport.DefaultExportService] Attempting to save the Active Objects Backup

2013-03-18 00:36:22,501 QuartzWorker-1 INFO ServiceRunner Backup Service [jira.bc.dataimport.DefaultExportService] Finished saving the Active Objects Backup

As we identified there were "SystemStackError: stack level too deep errors" in localhost.*.log file which are caused by too low -Xss Java stack size setting in Java startup parameters. See more information in eazyBI plugin setup help page.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Tuesday in Featured Groups

Tuesday tips & tricks: What is the Atlassian Community?

It's officially Tuesday, which means it's officially time for another tip to help you better navigate this space we call the Atlassian Community. 😄 I got a great question from community member, Sa...

116 views 6 8
View post

Atlassian User Groups

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!

Find my local user group

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

Groups near you