Troubleshooting dashboard usage

This topic covers the following issues that you may encounter when using the dashboard and provides more information to help solve the problem.

The dashboard does not automatically refresh data. Remember to click Refresh to update data.

As a general practice, take the following steps to deal with data display issues:

Refresh the data by clicking Refresh.
Check with your Grid administrator to determine if there is an issue with BMC Atrium Orchestrator.
Report the problem.

I cannot access the dashboard.

There are several possible reasons that you cannot access the dashboard. The following list provides some actions that might resolve the problem. If the problem persists, report it.

Verify that the Tomcat server is running.
If it is not running, start the Tomcat server (see Installing-and-configuring-the-BMC-Atrium-Orchestrator-Health-Dashboard for instructions).
Verify that the healthdashboard.war file is located in the tomcat/webapps directory (the directory is the one created when you extracted files from the healthdashboard<version>.zip file or the directory for your already existing Tomcat server).
If it is not there, put it there. If necessary, extract it from the healthdashboard<version>.zip file again (see Installing-and-configuring-the-BMC-Atrium-Orchestrator-Health-Dashboard for instructions).
If the healthdashboard.war file is located in the correct webapps directory, but it is not being deployed (a symptom of this is that you cannot access the dashboard with the correct URL), try the following steps.
1. Check the Tomcat log file for errors related to the war file.
  If there are no errors, try restarting the Tomcat server.
  or...
  If there are errors, replace the war file with a new copy and try restarting the Tomcat server.
2. If the Tomcat server still doesn't start, perform the following steps:
  1. Back up the Tomcat server log file and the gridmap and gridhosts properties files.
  2. Reinstall the dashboard and start the Tomcat server (see Installing-and-configuring-the-BMC-Atrium-Orchestrator-Health-Dashboard for instructions).
  3. Restore the gridmap and gridhosts files from your backup copies.
Verify that the dashboard URL is accurate (see Accessing-the-BMC-Atrium-Orchestrator-Health-Dashboard). The default port is 8080. If you modified the port number, ensure that the port number is correct.
Verify that cookies are enabled in the browser.

What time zone is shown in the dashboard?

The default time zone shown in the dashboard is the time zone of the host server.

What is the session timeout value?

The dashboard times out after 30 minutes of inactivity. You must log back into the dashboard.

My data isn't refreshing.

Click Refresh. If the data does not update, check with the Grid administrator to ensure that BMC Atrium Orchestrator is running and that there are no problems on that side.

BMC Atrium Orchestrator is not running, but the dashboard is showing data.

If you logged into the dashboard before BMC Atrium Orchestrator stopped running, the last recorded data appears in the dashboard.

If you click Refresh only the SSO information appears in the dashboard. If you log out of the dashboard, you will not be able to log back into the dashboard while BMC Atrium Orchestrator is not running.

I do not see the fully qualified host name in the server information on the Home page.

The dashboard does not report the fully qualified host names. As long as the first part of the name matches, there should not be a problem.

I do not see the version in the server or peer information on the Home or Peers page.

Verify that the server is running and that it is running BMC Atrium Orchestrator version 7.7.02. Older versions are not supported.

Adapter information is missing on the Home page.

Click Refresh to ensure that the dashboard displays the latest data. If the adapter information is still missing, check with the Grid administrator to determine if there are any problems on the BMC Atrium Orchestrator side.

Job information is missing on the Home page.

If you believe that there are jobs running and you do not see them in the dashboard, first click Refresh to ensure that the dashboard displays the latest data. If the job information is still missing, ask the Grid administrator to confirm that the jobs are running and, if they are running, to determine if there is a problem on the BMC Atrium Orchestrator side.

The dashboard does not reflect the changes that I made in the gridmap.properties file.

Restart the Tomcat server and log back into the dashboard. Changes to the gripmap.properties file take effect after you restart the Tomcat server.