## Login Issues
### I Cannot Access The Reporting Module As There Is No Menu Option
Check that the user has REPORTUSER access in their role as this determines if they are allowed to use the Reporting Module (Jasperserver).
### I Get An X-Opsview-AuthTkt-Username Error
If you get an error such as:
This is because we use Single Sign-On to authenticate into Jasperserver. Ensure you have set the correct Apache options by reviewing our [Reports](🔗) documentation.
### Invalid Ticket
If you see the error `
Authentication to Opsview succeeds, but the ticket is invalid for jasperserver`, restart the reporting module and try again:
/opt/opsview/watchdog/bin/opsview-monit restart opsview-reportingmodule`
Alternatively, this could be the result of a forward proxy masking browser IPs. Please refer to [this page](🔗) for more information about this issue.
## General Usage
### Apache Restart Generates Errors
If, when restarting Apache, the following error is generated, then it may be that config files from an earlier version of Jasperserver have not been cleaned up correctly.
Please try this:
### The Requested Resource (/jasperserver) Is Not Available
If that is displayed in your web browser, the Jasperserver application did not start up correctly. Check the Tomcat logs, which can be found in `
/opt/opsview/jasper/apache-tomcat/logs/`. One possible solution, noted on recent 64-bit platforms, might be to add `
org.owasp.csrfguard.PRNG.Provider=IBMJCE` to the file, `
### Is Jasperserver Running?
Check with _ps -ef | grep java_. You should get output like:
### Stopping Jasperserver Gives An Error
If you get an error like this:
This means that jasperserver is not currently running, so the stop command gives a warning message. This can be ignored.
### Jasperserver Fails To Connect To The Database
This can be caused by using TCP wrappers. To resolve, add entries to `
/etc/hosts.allow` such as _mysqld: 127.0.0.1_ which will allow Jasperserver to talk to the database. The rest of Opsview may be unaffected as it uses a MySQL file socket by default rather than a TCP port.
### I'm Not Receiving Any Reports By E-mail
This may be due to the email configuration of Jasperserver. Check the log file `
/opt/opsview/jasper/apache-tomcat/webapps/jasperserver/WEB-INF/logs/jasperserver.log` for lines such as
Backup and amend the file `
/opt/opsview/jasper/apache-tomcat/webapps/jasperserver/WEB-INF/js.quartz.properties` to change the line
mail.localhost.com` to either `
localhost` or your SMTP server.
### I've Had An "Out of Memory" (OOM) Error
If you are generating particularly large reports, the Java Virtual Machine (JVM) may hit an imposed memory limit which prevents it from using too much RAM. By default this limit is 512MB which can be increased by editing `
/opt/opsview/jasper/apache-tomcat/bin/setclasspath.sh` and amending the following line
The limit here was increased from 512MB to 768MB - ensure this limit is still within a reasonable range for your server. **Note**: This change will be lost on an upgrade.
### Running A Report Returns Database Not Found
This could also be seen as this error:
Ensure that the ODW data source is set properly, matching the credentials that were setup within the [Reports setup](🔗) of MySQL.
Also, check the Driver and URL are of the form:
Depending what is set within your /opt/opsview/jasper/etc/jasper.conf
The driver can be exactly as shown (since Opsview uses MySQL), but the URL may change depending upon the location of the MySQL server.
### I Think iReport Has Some Caching Issues, Especially If You Change The XML Directly.
Seems the Designer doesn't reload with the XML changes (seen when amending the SQL query). Clicking Save (top left corner) sometimes helps. Workaround is to close that report and re-open. We didn't observe this behaviour with iReport 5.6.0.
### I've Just Added A Hashtag And Reports Are Not Working For It
ODW stores configuration over time, so adding a new Hashtag will not be reflected over historically (because it didn't exist for that service at that time). There is a mechanism by which Hashtags may be 'backdated' onto Hosts and Service Checks in ODW.
### Running An Adhoc Report Doesn't Show Anything
This is often caused by the time-out parameter of Apache being set too low for the length of the time the report takes to run. Connect to Jasperserver on port 8080 and try running report http://localhost:8080/jasperserver/
### Updating An Existing Report With A New Resource Sometimes Gives A Null Pointer Error
This has occurred when changing an existing report's JRXML file and then adding a new resource. The work around is to save the report first, and then edit it again and add the JRXML file again. Error:
### Tomcat Logs
Look in _/opt/opsview/jasper/apache-tomcat/logs/catalina.out_. This holds the web server's log output.
### Jasperserver logs
If Jasperserver doesn't seem to have created the reports, check their log file in _/opt/opsview/jasper/apache-tomcat/webapps/jasperserver/WEB-INF/logs/jasperserver.log_. You can also see messages of failed jobs in View -> Messages.