Hi Jochen,
You can see below that the TCP connection is established correctly from
Firewall (192.168.113.17) to Graylog Server (192.168.119.71)
<https://lh3.googleusercontent.com/-8tpwir4Le1Q/VUdFhaPnPSI/AAAAAAAAAVg/kgRCxCSyICo/s1600/Syslog-to-GraylogTCP-1514-SYN.PNG>
But after a few seconds, it is closed abruptly
<https://lh3.googleusercontent.com/-p9bkRgMUJ0E/VUdF86KzbWI/AAAAAAAAAVo/UoQ4c5V0Sp8/s1600/Syslog-to-GraylogTCP-1514-RST.PNG>
Regards,
Le jeudi 30 avril 2015 17:01:35 UTC+2, Jochen Schalanda a écrit :
>
> Hi Ludovic,
>
> there is no explicit timeout for TCP connections in Graylog, as far as I
> know. Are you sure that the RST packets are sent by Graylog and not by some
> network appliance in between that tries to enforce a certain TTL for TCP
> connections?
>
> Cheers,
> Jochen
>
> On Thursday, 30 April 2015 16:27:36 UTC+2, Ludovic B. wrote:
>>
>> Hello,
>>
>> Nobody has ever get this issue ?
>>
>> Regards
>>
>>
>> Le mardi 28 avril 2015 22:14:17 UTC+2, Ludovic B. a écrit :
>>>
>>> Hello,
>>>
>>> I send syslogs messaes from a firewall over TCP to Graylog. I received
>>> those messages well but after a while, Graylog closes the TCP session with
>>> a RST packet. I do not understand this behavior
>>>
>>> Could'you help me please ?
>>>
>>> Here is versions I use:
>>>
>>> rpm -qa | grep graylog
>>> graylog-1.0-repository-el6-1.2.0-1.noarch
>>> graylog-web-1.0.1-1.noarch
>>> graylog-server-1.0.1-1.noarch
>>>
>>> Kernel 2.6.32-358.el6.x86_64
>>>
>>> And Input in Cluster
>>>
>>> Syslog TCP 1514 (Syslog TCP) running
>>> Network IO: 16,9kiB 0B (total: 13,0GiB 0B )
>>> Total connections: 11512 (2 active)
>>> recv_buffer_size: 1048576
>>> port: 1514
>>> tls_key_file:
>>> tls_key_password: *******
>>> max_message_size: 2097152
>>> override_source:
>>> allow_override_date: true
>>> bind_address: 0.0.0.0
>>> tls_cert_file:
>>>
>>> Regards,
>>>
>>>
--
You received this message because you are subscribed to the Google Groups
"graylog2" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
