Parse Errors GELF_TCP over TLS

Graylog Central (peer support)
1

I use nxlog to send Windows Event logs. On Windows 7 i can use use GELF TCP for a TLS connection. When I send from a Windows Server 2012 the input can not parsed:

Illegal character ((CTRL-CHAR, code 1)): only regular white space (\r, \n, \t) is allowed between tokens
at [Source: ; line: 1, column: 2]

or

ERROR [NettyTransport] Error in Input [GELF TCP/5b45f2606e75817a0c94afd4] (channel [id: 0x59fb3ae2, /10.1.82.41:60133 :> /10.2.59.100:9335])
java.lang.IllegalStateException: GELF message is too short. Not even the type header would fit.

Do anyone knows a solution for this problem ?

P.S. raw input over TLS works

2

Make sure that NXLOG is really sending GELF messages and that TLS is enable in the GELF input in Graylog.

3

@Jochen

These requirements are fulfilled;)

On the configured port, I had previously performed tests with other inputs.

Now i use another Port and it works

Strange behavior or is there a explanation for this ?

4

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