Troubleshooting

This section provides information about troubleshooting this release.

To change the logging options for the Value Dashboard

1. In a browser, open the following URL:
   http://computerName:portNumber/dashboards
   The Configuration tab opens
2. In the Log Settings section, change the Logger level to one of the following values:
   • Debug—Logs detailed information that provides insight into the sequence of events.
   • Info—Logs interesting runtime events, such as starting or stopping services and creating or deleting important objects. This is the default setting.
   • Error—Logs severe errors, runtime errors, and unexpected conditions.
3. In the Max. file size field, specify a maximum size (in MB) for the log file.
4. In the Max. backup index field, specify how many log files are backed up before the oldest file is deleted.
5. Click Update.

Enterprise AR System Server Health Status is red

If the Health Status of the Enterprise AR System Server is red after onboarding, open the PlatformManager/Configuration/cloudservices.json file and verify the value for the Enterprise Database(AR) Server attribute. If the value is anything other than the name of the Enterprise AR System server, correct the value and then re-onboard the BMC Cloud Lifecycle Management stack.

ARDBC Plugin Health or ARDBC Plugin Provider Health Check are red

If the Health Status of the ARDBC Plugin Health or the ARDBC Plugin Provider Health are red and the listed cause is “Healthcheck interrupted. Multiple sessions are not allowed for this user,” the probable cause is that the administrator credentials used to onboard the BMC Cloud Lifecycle Management stack are also being used to log into the BMC Cloud Lifecycle Management portal or the Enterprise AR or Cloud AR servers. Although there is no specific UI login for the Health Dashboard, internally the system uses the administrative credentials used to onboard the BMC Cloud Lifecycle Management stack. If the same administrator is already logged in to the BMC Cloud Lifecycle Management portal or the Enterprise AR or Cloud AR servers, the health check is interrupted.

To resolve this problem temporarily, the cloud administrator whose credentials were used to onboard the BMC Cloud Lifecycle Management stack should log out for a period of time and then the same administrator should log back in. The health check should be successful.

To resolve this problem permanently, create a separate cloud administrative user and onboard the BMC Cloud Lifecycle Management stack using those credentials. This cloud administrator should not access the BMC Cloud Lifecycle Management portal or the Enterprise AR or Cloud AR servers.

BMC Remedy AR System connection to the Value Dashboard fails

If the BMC Remedy AR System connection to the Value Dashboard fails, ensure that you are able to log in to BMC Remedy AR System using a browser (via the BMC Remedy AR System Mid Tier). Also ensure that no firewall restricts connectivity between BMC Remedy AR System and the Value Dashboard.

"Permission denied" error when installing the Health Dashboard on Linux

If you receive a "permission denied" error when installing the Health Dashboard on Linux, change the permission of the installation file to executable. For example:

Health Dashboard service not terminated on Linux during uninstallation

If the Health Dashboard service is not terminated when uninstalling the Health Dashboard, use the following procedure to terminate the process manually:

1. Enter the following command to obtain the process ID:

   # ps -ef | grep tomcat

   The command returns the ID.

2. Enter the following command to terminate the process, using the ID you obtained in the previous step:

   # kill -9 <ID>

Health Dashboard screens not displaying properly

If elements of the Health Dashboard screens are not displaying properly (such as buttons being disabled when they should be enabled), clear your browser cache and refresh the page.