Binary Installer Freezes

If you run the JasperReports Server installer on any platform and the installation fails, the following resources can help you find the source of the error.

Installer Log Files

If you run the JasperReports Server installer on any platform and there is an error, it is helpful to look at the log file created by the installer. This log file records the status and completion of installer operations. If your installer has had an explicit error, there may be a specific error message in the log. At a minimum, the log file should help narrow where the error has occurred even if there is not a specific error message.

You can find the installer log in the following locations:

Windows:

<js-install>/installation.log

Linux:

<js-install>/installation.log

Mac

<js-install>/installation.log

If you have tried multiple installs, make sure you view the most recent install log file. Then, you can submit the installation.log to Jaspersoft Technical Support.

Installer DebugTrace Mode

In addition, if you run the JasperReports Server installer on any platform and have a problem, you can run the installer a second time using the --debugtrace option. The --debugtrace option creates a binary output file that gives precise details about the execution of the installer and any problems encountered; this file can be analyzed by Jaspersoft Technical Support.

To use the --debugtrace option, you must run the installer from the command line and specify an output filename. The precise command depends on your platform (Linux, Windows, or Mac OSX). For example, you can execute the installer with a command similar to the following:

jasperreports-server-cp-<ver>-linux-x64-installer.run --debugtrace install-trace-out.bin

When you run the installer in --debugtrace mode, the installer will take extra time to write the binary output file. The final size of the output file is approximately 10 mg. Contact Jaspersoft Technical Support to hand off of the binary file for analysis.

Version: 
Feedback
randomness