Graylog2 / Graylog2/graylog2-server

rsyslog over tls: incoming messages but no message in the input stream

Open
#5,013 2 comments 0 reactions 0 assignees View on GitHub
to-verify
Dominant language
Java
Stars
8.1k
Forks
1.1k
Avg merge
1d 20h
Merged PRs (30d)
217

Description

We have set up a client with rsyslog to send data over TLS to the graylog server. We see incoming data on the right port with tcpdump and we have no errors in our logs (both client and graylog), but we can't see any messages in the input stream.

We have configured the input stream on the webinterface like this:
![](https://www.proudcommerce.com/out/pictures/master/product/3/xgraylog_input_tls.png.pagespeed.ic.i9KZYNwcmU.webp)

graylog server log messages:
```
2018-08-21_10:34:01.95319 INFO [AbstractTcpTransport] Enabled TLS for input [Syslog TCP/5b7bde773500d103c0a38504]. key-file="/etc/graylog/rsyslog-tls.key.pem" cert-file="/etc/graylog/graylog-pubkey.pem"
2018-08-21_10:34:01.95445 INFO [InputStateListener] Input [Syslog TCP/5b7bde773500d103c0a38504] is now STARTING
2018-08-21_10:34:01.97969 WARN [NettyTransport] receiveBufferSize (SO_RCVBUF) for input SyslogTCPInput{title=Syslog-over-TLS, type=org.graylog2.inputs.syslog.tcp.SyslogTCPInput, nodeId=82767910-b4b4-4997-aa8e-b2b62f0805e1} should be 1048576 but is 212992.
2018-08-21_10:34:01.98067 INFO [InputStateListener] Input [Syslog TCP/5b7bde773500d103c0a38504] is now RUNNING
```

rsyslog client configuration looks like this:
```
$ModLoad imuxsock # provides support for local system logging (e.g. via logger command)
$ModLoad imjournal # provides access to the systemd journal
$WorkDirectory /var/lib/rsyslog
$ActionFileDefaultTemplate RSYSLOG_TraditionalFileFormat
$IncludeConfig /etc/rsyslog.d/*.conf
$OmitLocalLogging on
$IMJournalStateFile imjournal.state
*.info;mail.none;authpriv.none;cron.none /var/log/messages
authpriv.* /var/log/secure
mail.* -/var/log/maillog
cron.* /var/log/cron
*.emerg :omusrmsg:*
uucp,news.crit /var/log/spooler
local7.* /var/log/boot.log
$DefaultNetstreamDriverCAFile /etc/ssl/graylog-pubkey.pem
$ActionSendStreamDriver gtls # use gtls netstream driver
$ActionSendStreamDriverMode 1 # require TLS
$ActionSendStreamDriverAuthMode x509/name # authenticate by hostname
$ActionSendStreamDriverPermittedPeer graylog.
*.* @@:514
```
rsyslog log messages:
```
Aug 21 10:38:11 cloud-168. systemd[1]: Starting System Logging Service...
Aug 21 10:38:11 cloud-168. rsyslogd[1063]: [origin software="rsyslogd" swVersion="8.24.0" x-pid="1063" x-info="http://www.rsyslog.com"] start
Aug 21 10:38:11 cloud-168. systemd[1]: Started System Logging Service.
```

## Expected Behavior

We should be able to see incoming messages in the graylog instance.

## Current Behavior

We see incoming messages on the port via tcpdump, but we don't see any messages in the webinterface
## Possible Solution

no idea

## Steps to Reproduce (for bugs)

1. Setup rsyslog over tls with the configuration above
2. configure syslog tcp input with tls like above
3. restart rsyslog on client
4. watch incoming messages with tcpdump

## Context

My goal is secure log forwarding via rsyslog on clients to graylog

## Your Environment

* Graylog Version: 2.4.6
* Elasticsearch Version: no idea
* MongoDB Version: no idea
* Operating System: Description: Ubuntu 14.04.5 LTS
* Browser version: Chrome 68

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.