DM 10.1 CU12 Elasticsearch related RTEs

Solved864 views
2
0 Comments

Recently upgraded a MySQL 9.6 CU23 test system to 10.1 CU12 and now I am getting the following 2 RTEs on each restart:

  • "The TicketingManager was enabled and licensed, but no valid Elasticsearch installation was found. The manager has not been initialized."
  • "The Service Manager is licensed, but no Elasticsearch database is active on the system. Therefore, Resource Manager and Service Manager will not initialize."
  1. Can these alarms be ignored since I am running MySQL.
    1. if not, what would the issue be
  2. I can manually clear each alarm but is there a way to keep these alarms from getting generated in the first place

We are getting ready to roll out DM 10.1 to all our customers and I need to be prepared for all the questions/concerns that will generated when the end users see these.

Thanks

Marieke Goethals [SLC] [DevOps Catalyst] Selected answer as best 17th July 2023

1 Answer

4
1.53K 1 Comment

Hey Jeff,

You can ignore these alarms. They state that part of your setup is licensed to do stuff for which the setup is not compatible at the moment. As long as you do not plan to use the mentioned functionality, the system should not be impacted.

Currently there is no way to automatically clear these alarms, they will be re-created with each agent start. So you could setup a system where after startup or if they appear triggers an automation script fetches these alarms and close them.

Marieke Goethals [SLC] [DevOps Catalyst] Selected answer as best 17th July 2023