Resolve Event Analytics (EA) Error "Could not find first log file name in binary log index file"
(Doc ID 2898783.1)
Last updated on SEPTEMBER 30, 2022
Applies to:
Oracle Communications Unified Assurance - Version 4.0.51.0.0 to 4.0.87.0.0 [Release 4.0.0.0]Information in this document applies to any platform.
Symptoms
The Elasticsearch Data Importer is designed to read from MariaDB binary logs and insert changes into Elasticsearch. For data to be read from the MariaDB binary logs and sent to Elasticsearch, the Service "Elasticsearch Database Importer" must be up and running with no issues.
The Unified Assurance (Assure1v4) default retention days, when binary logging is enabled, is set in the “expire-logs-days" variable. The default value is 3 days. It resides in the “redundancy-primary.cnf”. The variable, log location and its default value are shown below:
The above error indicates the service "Elasticsearch Database Importer" is out of sync with the current binary log. Perhaps the system was offline for too many days or some sort of ungraceful system crash. If the service does encounter a problem, there are a few steps to take to remedy the issue.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |