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 suspect it
Thanks for getting back to me, yes I suspect it has something to do with my
filters though I've no idea which one it could be as I'm filtering on beats
and syslog inputs. As a work around I've just added a cron command to
restart Logstash every morning at 01:00, though obviously that means I'm
I have seen the same issue. In my case however, I had 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
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
