Troubleshooting Reports

Resolve your reporting issues with Opsview Monitor

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).

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.

$ /etc/init.d/apache2 restart
 * Restarting web server apache2
             [Wed Nov 21 11:46:40 2012] [warn] worker already used by another worker
 ... waiting [Wed Nov 21 11:46:41 2012] [warn] worker already used by another worker                      [ OK ]

Please try this:

$ rm /etc/apache2/conf.d/jasperserver.conf

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, /opt/opsview/jasper/apache-tomcat/webapps/jasperserver/WEB-INF/esapi/

Is Jasperserver Running?

Check with ps -ef | grep java. You should get output like:

root     11468 25337  0 10:59 pts/0    00:00:00 grep java
opsview  30083     1  0 Oct07 ?        00:03:08 /usr/lib/jvm/java-6-sun- -Xms128m -Xmx512m -XX:PermSize=32m -XX:MaxPermSize=128m -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.util.logging.config.file=/opt/opsview/jasper/apache-tomcat/conf/ -Djava.endorsed.dirs=/opt/opsview/jasper/apache-tomcat/common/endorsed -classpath :/opt/opsview/jasper/apache-tomcat/bin/bootstrap.jar:/opt/opsview/jasper/apache-tomcat/bin/commons-logging-api.jar -Dcatalina.base=/opt/opsview/jasper/apache-tomcat -Dcatalina.home=/opt/opsview/jasper/apache-tomcat org.apache.catalina.startup.Bootstrap start

Stopping Jasperserver Gives An Error

If you get an error like this:

Jasperserver stop... Apr 27, 2012 3:12:49 PM org.apache.catalina.startup.Catalina stopServer
SEVERE: Catalina.stop: Connection refused
at Method)

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: 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

Caused by: javax.mail.MessagingException: Could not connect to SMTP host:, port: 25;

Backup and amend the file /opt/opsview/jasper/apache-tomcat/webapps/jasperserver/WEB-INF/ to change the line

from 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/ and amending the following line

JAVA_OPTS="$JAVA_OPTS -Xms128m -Xmx512m -XX:PermSize=32m -XX:MaxPermSize=128m "

to read

JAVA_OPTS="$JAVA_OPTS -Xms128m -Xmx768m -XX:PermSize=32m -XX:MaxPermSize=128m "

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:

com.jaspersoft.jasperserver.api.JSException: jsexception.error.creating.connection
at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.JdbcDataSourceService.createConnection(

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.

The Requested Resource (/jasperserver) returns a 401 response

Relog into your Opsview user via the Opsview UI and retry.

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.

On the Opsview Orchestrator

1) Create your Hashtag, apply this to your Hosts/Service Checks in question and Apply Changes
2) Await the next hourly import from your Runtime database to your ODW database (the import_runtime) process
3) Run the /opt/opsview/coreutils/utils/odw_mass_backdate_keyword script, specifying the host and hashtag (keyword) in question.
- if you run this script without a host and hashtag it will ask you for them and provide a list of hosts, then hashtags to you.

The end syntax would look something like this:
- Example Host: opsview-orchestrator
- Example Hashtag: newhashtagname

sudo su - opsview
/opt/opsview/coreutils/utils/odw_mass_backdate_keyword opsview-orchestrator newhashtagname

Step 2 is important, as the hashtag needs to be present in your ODW database in order for a Report to run against it, so you must wait until that next run (at 4 minutes past the hour), so that the previous hours worth of data is available to be queried.

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:

	at com.jaspersoft.jasperserver.war.validation.FileResourceValidator.validateNaming(
	at sun.reflect.GeneratedMethodAccessor589.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(

I cannot connect Jaspersoft Studio to the Opsview Reporting Module (401 response)

Ensure that your system is configured with a sufficient max number of sessions. See Session Manager Config for Jaspersoft Studio for mitigation details.

I cannot run reports within the Jaspersoft Studio IDE (401 response)

This is not a supported feature. See Running Reports in Jaspersoft Studio for alternatives.

I cannot see all the expected resources, or publish my changes, using Jaspersoft Studio

Ensure your Opsview User has the required permissions. See Permissions for Jaspersoft Studio for details.


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.