Syslog not working

Hello, i get no logs from syslog 2 different syslog server
first i have try with Port 514, but this port is not allowed then i will switch to port 5044 (high port).

ive got this error message in logstash.log
[2018-05-15T14:09:28,837][ERROR][logstash.pipeline ] A plugin had an unrecoverable error. Will restart this plugin.
Plugin: <LogStash::Inputs::Beats ssl=>false, host=>"", port=>5044, id=>"cd84264b23308b5a3966a309b11ebd5fc938f081d8f60d0d1d04bf29f54cf8be", enable_metric=>true, codec=><LogStash::Codecs::Plain id=>"plain_0f48bb3e-d183-4713-9c7a-24947da85076", enable_metric=>true, charset=>"UTF-8">, ssl_verify_mode=>"none", include_codec_tag=>true, ssl_handshake_timeout=>10000, tls_min_version=>1, tls_max_version=>1.2, cipher_suites=>["TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384", "TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384", "TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256", "TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256", "TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384", "TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384", "TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256", "TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256"], client_inactivity_timeout=>60, executor_threads=>4>
Error: event executor terminated
Exception: Java::JavaUtilConcurrent::RejectedExecutionException
Stack: io.netty.util.concurrent.SingleThreadEventExecutor.reject(io/netty/util/concurrent/
opt.bitnami.logstash.logstash_minus_core.lib.logstash.pipeline.block in start_input(/opt/bitnami/logstash/logstash-core/lib/logstash/pipeline.rb:507)

My syslog.conf in logstash
input {
tcp {
port => 5044
type => syslog
udp {
port => 5044
type => syslog

filter {
if [type] == "syslog" {
grok {
match => { "message" => "%{SYSLOGTIMESTAMP:syslog_timestamp} %{SYSLOGHOST:syslog_hostname} %{DATA:syslog_program}(?:[%{POSINT:syslog_pid}])?: %{GREEDYDATA:syslog_message}" }
add_field => [ "received_at", "%{@timestamp}" ]
add_field => [ "received_from", "%{host}" ]
date {
match => [ "syslog_timestamp", "MMM d HH:mm:ss", "MMM dd HH:mm:ss" ]

output {
elasticsearch { hosts => ["localhost:9200"] }
stdout { codec => rubydebug }

Thats pretty strange. Can anybody help me?

It looks like you already have a beats input that listens on port 5044.

Yes thats right the beats plugin use the same port.
i have change the port to 5500. now i have no error messages put i cant use telnet from my local pc to this port. on my debian system is no firewall active.
Thats pretty strange :slight_smile:
Anybody have an idea?

Does Logstash start up fine? Have you looked in the logs? Have you used netstat to check whether Logstash is actually listening on port 5500?

When i start a TCPdump, i can see the traffic from the syslog client

Logstash log look like this after restart:

[2018-05-16T14:29:52,400][INFO ][] Starting server on port: 5044
[2018-05-16T14:29:52,401][WARN ][] Force-closing a channel whose registration task was not accepted by an event loop: [id: 0x39f52092]
java.util.concurrent.RejectedExecutionException: event executor terminated
at io.netty.util.concurrent.SingleThreadEventExecutor.reject( ~[netty-all-4.1.18.Final.jar:4.1.18.Final]
at io.netty.util.concurrent.SingleThreadEventExecutor.offerTask( ~[netty-all-4.1.18.Final.jar:4.1.18.Final]
at io.netty.util.concurrent.SingleThreadEventExecutor.addTask( ~[netty-all-4.1.18.Final.jar:4.1.18.Final]
at io.netty.util.concurrent.SingleThreadEventExecutor.execute( ~[netty-all-4.1.18.Final.jar:4.1.18.Final]
at$AbstractUnsafe.register( [netty-all-4.1.18.Final.jar:4.1.18.Final]
at [netty-all-4.1.18.Final.jar:4.1.18.Final]
at [netty-all-4.1.18.Final.jar:4.1.18.Final]
at [netty-all-4.1.18.Final.jar:4.1.18.Final]
at io.netty.bootstrap.AbstractBootstrap.initAndRegister( [netty-all-4.1.18.Final.jar:4.1.18.Final]
at io.netty.bootstrap.AbstractBootstrap.doBind( [netty-all-4.1.18.Final.jar:4.1.18.Final]
at io.netty.bootstrap.AbstractBootstrap.bind( [netty-all-4.1.18.Final.jar:4.1.18.Final]
at io.netty.bootstrap.AbstractBootstrap.bind( [netty-all-4.1.18.Final.jar:4.1.18.Final]
at [logstash-input-beats-5.0.13.jar:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_161]
at sun.reflect.NativeMethodAccessorImpl.invoke( ~[?:1.8.0_161]
at sun.reflect.DelegatingMethodAccessorImpl.invoke( ~[?:1.8.0_161]
at java.lang.reflect.Method.invoke( ~[?:1.8.0_161]
at org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling( [jruby-complete-]
at org.jruby.javasupport.JavaMethod.invokeDirect( [jruby-complete-]
at [jruby-complete-]
at opt.bitnami.logstash.vendor.bundle.jruby.$$method$run$0(/opt/bitnami/logstash/vendor/bundle/jruby/2.3.0/gems/logstash-input-beats-5.0.13-java/lib/logstash/inputs/beats.rb:198) [jruby-complete-]
at opt.bitnami.logstash.logstash_minus_core.lib.logstash.pipeline.RUBY$method$inputworker$0(/opt/bitnami/logstash/logstash-core/lib/logstash/pipeline.rb:514) [jruby-complete-]
at opt.bitnami.logstash.logstash_minus_core.lib.logstash.pipeline.RUBY$method$inputworker$0$VARARGS(/opt/bitnami/logstash/logstash-core/lib/logstash/pipeline.rb) [jruby-complete-]
at [jruby-

sorry Logstash and the hole elastic stack looks nice but its too complex.
Splunk is very easy to use!!!!!!!!!
I hate logstash. I've been working on it for 3 days now and no one knows why it does not work.

It is all a matter of experience. I have the same sentiment about Splunk... it is way more difficult than Elastic. However I feel that way primarily because I have more experience with one over the other. Everything has a learning curve, and it can be frustrating until it finally "clicks".

I am actually glad that's the case. If everything was easy, there would no value in mastering it, and we in IT would all be paid a lot less than we are. Embrace difficulty... it is how you set yourself apart from average.

There are people out there that can help in a number of ways. Training, consulting, etc. If you find the right partner to work with I am confident you will find that you can achieve with Elastic everything you can with Splunk... and more... and for a lot less money.

Thank you for your answer. Today I was able to fix the error and I am now receiving syslog messages in kibana. At the moment I try to restrict everything with the grok filter. maybe you have some help for me at the following LOG

<14>1 2018-05-19T13:38:20.147+02:00 localhost XMS - AdminAudit [@18060"ApplePush" client.ip="""F17xxx" device.imei="35 000000 009142 2" device.ownerName="" device.serial="F2LKTJC6BHFY7""" event.action="PUSH_SOFTWARE_INVENTORY_REQUEST" event.status="DONE""1818201999-31034" http.user-agent="WorxMailAppStore/ CFNetwork/897.15 Darwin/17.5.0" push.device="2793""63715""[UID=63715,,dev=2793]""ApplePushTarget[os=iOS, device=2793,, type=DEVICE]" push.user="""38918DDF9400EB5C"""] {"source":"PUSH_SERVICE","deviceUser":"","deviceIMEI":"35 000000 609917 1"}

Normally i can sort this log in seperat fields?

For a better starting point with Syslog, take a look at this...

Then for examples on how to further enrich data look at this...

It contains a step-by-step walk through of going from a raw log to useful dashboards.

For a far more advanced example of what is possible, you can dig through my ElastiFlow solution...


Robert Cowart (
True Turnkey SOLUTIONS for the Elastic Stack

1 Like

Hi Rob,
Can not I use grok filter for syslog?

Wie ich gelesen habe sprichst du auch sehr gut deutsch Robert :slightly_smiling_face:
Grüße aus der Nähe von München :slight_smile:

Sure you can. But the grok filter alone is unlikely to get you where you want to be. For example... the log that you have above will probably benefit from (at a minimum)... grok, syslog_pri, kv

You should really walk through the PDF slides in the eslog_tutorial link above. The things you should be thinking about is...

  1. Handle the basic syslog stuff (priority, timestamp, hostname/ip, etc)
  2. Break the message up into its various parts - I see some key-value pairs and some JSON.
  3. Use the various filters available to turn these parts into document fields.

The tutorial walks through this stuff. I created it because I went through the same beginner frustrations that you are experiencing, and I wanted to help others more easily learn it more quickly. Usually I would present it in a meetup format, walking through each step. Everything you need is there... The Logstash pipelines (at each step), the index templates, the Kibana dashboards, sample data, etc.

If you spend a few hours really digesting that material, you should see that your log is not as intimidating as it might first appear to be.

Und Ja, Deutsch kann Ich auch. Aber Ich bin Ami und schreibe lieber auf Englisch :wink:

OK verstehe, aber ich habe das ganze system noch nicht zu 100% verstanden. Das ist mir noch zu hoch dein Produkt.
OK, but I have not understood the whole system 100%. That's still too high for your product.

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.