RVR-ES-700
- 1 Minute to read
- Print
- DarkLight
- PDF
RVR-ES-700
- 1 Minute to read
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Issue Summary
- The error "External Error - Run FailureError Code: RVR-ES-700" indicates an issue with the connection to Elasticsearch using Rivery's data connectors. This error suggests a failure in running the process that extracts data from Elasticsearch, likely due to a configuration issue or a problem connecting to the Elasticsearch server.
- Elasticsearch connection issues may be caused by incorrect configuration in the connection settings, invalid credentials, or an issue with the Elasticsearch server or network connectivity.
Action Steps:
- Verify Connection Settings: Ensure that your Elasticsearch connection settings in Rivery are correctly configured. Check that the host, port, and authentication details (if any) are correctly set.
- Check Elasticsearch Server Status: Make sure the Elasticsearch server is running and accessible from the network. Confirm network connectivity and that there are no firewall rules blocking access.
- Review Logs: Check the logs in Rivery and Elasticsearch for any specific error messages or details that might indicate what's causing the run failure.
- Authentication Credentials: If the connection requires authentication, ensure that the credentials are correct and have appropriate permissions to access the required indices.
- Verify Index Settings: Confirm that the indices or documents being accessed are available and there's no issue in querying them.
- Increase Timeout Values: Sometimes increasing the timeout settings in the connection configuration might help if the issues are related to network latency or timeout.
External References:
- Refer to Rivery’s Elasticsearch documentation to ensure that all configurations are compliant with Rivery’s guidelines.
- Visit Elasticsearch official documentation for further troubleshooting on their end.
If the issue persists or you need further assistance, please open a ticket with Rivery support.
Was this article helpful?