Just as an update, we upgraded the ElasticStack to 6.3.2 a couple of months
ago and Logstash has not crashed since, so whatever the problem was it
appears to have been fixed in the later release.
On Thu, 24 May 2018 at 13:47, Kernel Panic wrote:
> Thanks for getting back to me, yes I susp
at 01:16, Sascha Holzleiter
wrote:
>
> On 8/28/2018 5:33 PM, Kernel Panic wrote:
> > Hello all,
> >
> > I've upgraded all our Elasticsearch cluster components from 6.2.4 to
> 6.3.2
> >
> > The cluster itself seem fine but Kibana will not start; in th
Hello all,
I've upgraded all our Elasticsearch cluster components from 6.2.4 to 6.3.2
The cluster itself seem fine but Kibana will not start; in the Kibana log
it shows the following:
{"type":"log","@timestamp":"2018-08-28T15:17:36Z","tags":["reporting","error"],"pid":76937,"message":"Failed
to
about OOM caused by
> parsing long grok patterns. I didn't have these in 5.3 either so I suspect
> it's a memory leak somewhere.
> I have since upgraded everything to 6.x and am waiting to see if the same
> issue persists.
>
> Regards,
> Benny Goemans
>
> On 23-05-2018 1
Hello, I'll just list the versions before I start:
FreeBSD 11.1
Logstash 6.23
Elasticsearch 5.6.8
Kibana 5.6.8
The issue I'm having is that after a few days Logstash will stop processing
any messages; I'm using the same config file that I used with Logstash
5.3.0 which worked without issue and
