RE: connection timeout between ioc and logstash

["Kivel Niko \(PSI\) via Tech-talk" <tech-talk@aps.anl.gov>]

Hi all

while it's true that logstash (or whatever other logging facilities) could artificially keep the connection alive, it's only indirectly related to the actual problem. Which is, that the logger - while obviously noticing the broken connection - doesn't buffer and resend the failed message. It only sends the next message after the reconnect. Which might happen after another timeout.

best
Niko

--
Paul Scherrer Institute
Dr. Niko Kivel
Forschungsstrasse 111
WBGB/014
5232 Villigen PSI
Switzerland

phone: +41 56 310 2226
email: niko.kivel@psi.ch

________________________________________
From: tech-talk-bounces@aps.anl.gov [tech-talk-bounces@aps.anl.gov] on behalf of J. Lewis Muir via Tech-talk [tech-talk@aps.anl.gov]
Sent: Thursday, August 15, 2019 16:48
To: 吴煊
Cc: tech-talk
Subject: Re: connection timeout between ioc and logstash

On 08/15, 吴煊 via Tech-talk wrote:
>   We are testing for using logstash to replace iocLogServer. We found that it will lose connection between the ioc and logstash if none of PV has been written more than an hour(not very accuracy). If writting a PV again, it will establish the connection again, but the caPutLog message of this time will not be sent to logstash. It prompted that in IOC terminal:
>
> log client: lost contact with log server at "10.1.236.30:7011" because "Connection timed out"
>
> log client: connected to log server at "10.1.236.30:7011"
>
> from then on, it will work fine if the interval time of writting PV was not very long.So how can keep the connection all the time without timeout. It seems that using iocLogServer will not lose connection.

How are you logging to Logstash?  A custom Logstash client?  How does it
work?

Can you determine what is closing the connection?  Is it the Logstash
server?  Is it a firewall?  Is it a NAT proxy?

Can you look at the configuration of your Logstash server and see if it
has a timeout or keep-alive option and ensure it is set correctly?

For example, if you're using the TCP input plugin of Logstash

  https://www.elastic.co/guide/en/logstash/current/plugins-inputs-tcp.html

it has a tcp_keep_alive option that defaults to false; you could try
setting that to true.

Regards,

Lewis