Troubleshooting

On this page:

Installation

Jira issues import

  • If the import fails with errors then please send us all eazyBI log files or eazybi-queues.log file

  • If the import is very slow then check recommended database memory settings (for MySQL and PostgreSQL).
  • If not all Jira issues are visible in eazyBI then see how to re-import all issues. You also need to re-import all issues if any dimension members (for example, statuses, priorities or custom field select list values) are renamed and you would like to see new names in eazyBI.
  • If you are importing issues into Jira from an external system then please ensure that issue update date is set to current date timestamp. If issues will be imported with old update date (before last eazyBI Jira import timestamp) theneazyBIincremental import will consider these issues as already imported.

eazyBI log files

eazyBI stores its log files in the Jira home directory log subdirectory (if you do not know where is your Jira home directory then go to Jira Administration / System / Troubleshooting and Support / System Info page and see Location of Jira Home):

  • eazybi-web.log contains the log of web requests
  • eazybi-queues.log contains the log of background queue jobs
  • If the child process is enabled then there will be also child process log files

You can download a ZIP archive with all eazyBI logs from the Troubleshooting page:



If you have enabled Mondrian logging - Mondrian log files won't be included into the ZIP archive because of possible very big size. You can access Mondrian log files only directly in file system.

The log file download from the Troubleshooting page is available since the eazyBI version 4.0.0. If you are using any previous version then please find log files in the Jira home directory as described in the previous section.

Reports

  • If queries in Analyze tab are failing with an error message then find the error in System Events and send Payload column content to eazyBI support.
  • If there are problems with measures containing Unicode characters then check that UTF-8 encoding is used for Jira.