Closed saitheexplorer closed 9 years ago
@saitheexplorer, from what I understand, it's an Elasticsearch configuration issue. There is a logstash ticket from a few years ago describing the problem and provides a possible workaround.
I hope this helps. Let me know if you come up with a way to incorporate the workaround.
We encountered this recently, and in our case it wound up being that the current Docker image was now expecting config files included via Docker volume to be located at /opt/logstash/conf.d/*
rather than /opt/logstash.conf
.
@shanesveller, that's really interesting. I'll keep that scenario in mind. Thanks.
I'm seeing this in my docker container logs after the certs have been downloaded.
Is this a logstash issue?