Kepler service failed to start after three attempts

Description

This alert is triggered when a Kepler Service has failed to start after three attempts.

When the Service Host starts up, it creates a Kepler Service for each associated application. Each Kepler Service process includes an automatic retry mechanism that attempts to restart the service if it fails during initialization. The Service Host will attempt up to three restarts. If all three attempts fail, it will stop retrying, and no further automatic restart will occur.
Any functionality associated with the affected application will be unavailable.
API calls targeting the failed Kepler Service will not be processed.
In other words, there will be issues with running any Relativity application functionality or making any API calls to the Kepler Service that is not running.

Go to the Backend of the Relativity instance.
Verify the 'kCura Service Host Manager' Windows service is running.
If any one application not working, restart the 'kCura Service Host Manager' Windows service.
Wait for 6 min so that all applications/services are deleted and recreated.
Refresh Kibana browser and the alert will be recovered.

Name	Value	Description
Rule Type	Elastic Query
Data View	Logs-*
Filter Query	labels.event_type :"health_check" AND labels.status_state: "unhealthy" AND labels.event_source :"relsvr.servicehost" AND labels.name:"relsvr.servicehost.startup_service.failure"
Threshold	> 0	Count greater than 0, alert triggers
Time Window	5 min	Verified data for last 5 min
Frequency	1 min	Checks for every 1 min

Feedback

Why was this not helpful?

Check one that applies.

I could not find the information I was looking for.

The information was incorrect.

The instructions are confusing or unclear.

The instructions did not work.