Why Is An Error Reported When Pushing Data to CSS After Deploying Logstash on an ECS?
Issue
After Logstash is deployed on an ECS, an error is reported when data is pushed to CSS.
Symptom
After Logstash is deployed on an ECS, an error is reported when data is pushed to CSS. The error message is as follows:
LogStash::Outputs::ElasticSearch::HttpClient::Pool::BadResponseCodeError: Got response code '500' contacting Elasticsearch at URL 'https://192.168.xx.xx:9200/_xpack'.
Possible Causes
CSS currently does not integrate the x-pack plugin. When you access CSS after deploying Logstash, the system will check whether x-pack is enabled for CSS.
Procedure
- Delete the x-pack directory in Logstash.
- Add the configuration item ilm_enabled => false to elasticsearch under the output tag in the Logstash configuration file.
- Push data to CSS again.
Last Article: What Should I Do When Logs Cannot Be Written to CSS and A High CPU Usage Is Displayed?
Next Article: Functions
Did this article solve your problem?
Thank you for your score!Your feedback would help us improve the website.