Troubleshooting OMi Performance Engine

Problem: OMi Performance Dashboard is not showing data for OpsBridgeStore data source

Solution: To resolve this problem, follow these steps:

If you have reconfigured Vertica database, you must invoke OMi Performance Engine API in OMi to forcefully update the cache config by running the following URL on the OMi server : http://<OMi gateway host info>/PE/rest/1.0/admin/reconfigure/cache

Problem: OpsBridge Store datasource is not listed in Performance Dashboard

Solution: To resolve this problem, follow these steps:

1. To check if OMi Performance Engine is running properly, type the following command in OMi Performance Engine server:

   #/opt/OV/bin/ovc -status PE

   All the PE services should be running.

2. Check for errors in OMi Performance Engine by verifying the logs at /var/opt/OV/pe/log/

3. In OMi console, OMi Performance Engine node should be configured in Administration > Setup and Maintenance > Infrastructure Settings

   1. Choose Performance Engine as the Application.
   2. Provide the OMi Performance Engine node details and password.

4. Check for errors in OMi logs for OMi Performance Engine:

   Windows:

   C:\HPBSM\log\PE\perfengine.log

   Linux:

   opt/HP/BSM/log/PE/perfengine.log

Problem: You are trying to enable HTTPs in OMi Performance Engine, admin tools reports unable to create certtrusted file and error message appears.

Solution: To resolve this problem, follow these steps:

You are trying to enable certificate based authentication in OMi Performance Engine before OMi certificate reaches the node. You need to verify if the overcert –list command is listing the certificates properly before you invoke the admin tool utility.

Problem: When non-root user is configured in OMi Performance Engine, the BBC port is updated from default 383 to port number higher than 1024.

Solution: To resolve this problem, run the following command on the OMi server:

(ovinstalldir)/bin/ovconfchg -ns bbc.cb.ports -set PORTS PEHOSTNAME:BBCPORT

Problem: OMi Performance Engine is retaining the last one month data in Vertica database. As a user, I want to change data retention in Vertica database.

Solution: Out-of- the- box, OMi Performance Engine can retain data for 30 days. To change the data retention duration, follow these steps:

1. Open /opt/HP/BSM/HPEPerfEngine/conf/perfengine.conf

2. Update the purge configuration to required number of days

   # Parameter : purge

   # Specify the number of days after which data will be purged in db.

   purge=30

3. Save the file and run #/opt/OV/bin/ovc -restart pelistener

   Note: In case of cluster installation, you must perform the same steps in all the nodes.

Problem: As a user , I want to know the current throughput of the OMi Performance Engine Server.

Solution: To resolve this problem, you can check the throughput of the node by following these steps:

1. In OMi Workspace, create a new page.
2. From the component gallery, choose Performance Engine Throughput component.
3. The component opens, Performance Engine Throughput data in Performance Dashboard. The dashboard shows the data streamed to PE in Charts.

Problem: You want to increase the maximum POST request size of json data. By default the max size of json is 1MB.

Solution: To resolve this problem, follow these steps:

1. Set following properties in the following file:

   /opt/HP/BSM/HPEPerfEngine/kafka/config/server.properties

   message.max.bytes=<SOME_BIG_VALUE_IN_BYTES>

   replica.fetch.max.bytes=<SOME_BIG_VALUE_IN_BYTES_GREATER_THAN_EQUAL_TO_THE_ABOVE>

2. Change the properties in the following file:

   /opt/HP/BSM/HPEPerfEngine/conf/perfengine.conf file

   max_req_size=<SOME_BIG_VALUE_IN_BYTES_GREATER_THAN_EQUAL_TO_THE_ABOVE>

3. Restart PE services.

   /opt/OV/bin/ovc -restart PE

Problem: PE services are not running or are aborted if the host names are not configured properly on the system.

Solution: To resolve this problem, you must re-install the product with the correct IP address or host name in the PE_Profile file.

Problem:OMi Performance Engine services are not starting after the system is rebooted.

Solution: To resolve this problem, set the "START_ON_BOOT" configuration variable to true. Run the following command:

/opt/OV/bin/ovconfchg -ns ctrl -set START_ON_BOOT true

Problem:OMi Performance Engine services are starting in root user mode even when OMi Performance Engine is configured in a non-root user mode.

Solution: This problem occurs if ovcd is stopped by using /opt/OV/bin/ovc -kill and OMi Performance Engine is started by using /opt/OV/bin/ovc -start PE as root user.

To resolve this issue, do the following:

1. As root user, check if the "START_ON_BOOT" configuration variable is set to true. If it is set to false, run the following command:

   /opt/OV/bin/ovconfchg -ns ctrl -set START_ON_BOOT true

2. Stop OMi Performance Engine services by running the following command:

   service OVCtrl stop

3. Remove log files created by root in the following directories:

   • Default Kafka directory: /opt/HP/BSM/HPEPerfEngine/kafka/kafka-logs/
   • Non-default Kafka directory (if you have changed the default Kafka log directory): <NonDefaultkafkaDirectory>/kafka-logs
   • Zookeeper directory: /opt/HP/BSM/HPEPerfEngine/kafka/zookeeper-data/version-2/

4. Start OMi Performance Engine services by running the following command:

   service OVCtrl start