Hi there, I'm using the OSE of syslog-ng for some weeks. Today I updated syslog-ng to 3.13 and afterwards I started seeing -- Unit syslog-ng.service has begun starting up. Dez 13 11:53:59 syslog syslog-ng[23803]: [2017-12-13T11:53:59.572246] Error initializing message pipeline; plugin name='java', location='#buffer:2:3' Dez 13 11:53:59 syslog systemd[1]: syslog-ng.service: Main process exited, code=exited, status=2/INVALIDARGUMENT Dez 13 11:53:59 syslog systemd[1]: Failed to start System Logger Daemon. -- Subject: Unit syslog-ng.service has failed -- Defined-By: systemd-13T11:53:59.572246] Error initializing message pipeline; plugin name='java', location='#buffer:2:3' In "journalctl -xe" If I disable the elasticsearch destination syslog-ng starts up fine. I don't know what to look at as the error message is not very meaningful to me. Did I miss some configuration format changes regarding the "elasticsearch2" destination? The header of my "/etc/syslog-ng/syslog-ng.conf": === Snip === @version: 3.13 @module mod-java @include "scl.conf" === Snip === My elasticsearch config for syslog-ng: https://pastebin.com/g6UB3gBi "ls -l {/usr/share/elasticsearch/lib/,/usr/lib/syslog-ng/3.13/java-modules/}" https://pastebin.com/nqYAVhHL "cat /etc/systemd/system/multi-user.target.wants/syslog-ng.service" https://pastebin.com/UzfQXvZL I really appreciate any help. Thank you! Best regards, Ruben ____________________________________________________________________________ netsys IT GmbH Ruben Roegels Nelly-Sachs-Str. 4 79111 Freiburg Tel. +49 761 888 691 0 Fax +49 761 888 691 10 <http://www.netsys-it.de> Ruben.Roegels@netsys-it.de ____________________________________________________________________________ Amtsgericht Freiburg HRB 5752 Geschaeftsfuehrer: Juergen Dufner ____________________________________________________________________________