Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  <20192020  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  <20192020 
<== Date ==> <== Thread ==>

Subject: Re: Re: connection timeout between ioc and logstash
From: 吴煊 via Tech-talk <tech-talk@aps.anl.gov>
To: "j. lewis muir" <jlmuir@imca-cat.org>, "kivel niko (psi)" <niko.kivel@psi.ch>
Cc: tech-talk <tech-talk@aps.anl.gov>
Date: Fri, 16 Aug 2019 23:22:37 +0800 (GMT+08:00)
Hi all,
To Lewis,
I simplly followed the instruction written by Andrew Johnson https://events01.synchrotron.org.au/event/85/contributions/2601/attachments/689/997/5_06_Logstash_for_IOCs.pdf
A thread named "IOClog" in May 2th 2019 had mentioned this.
I've installed logstash 7.2 in a linux box. I configured 'caPutLogInit "10.1.236.30:7011", 1' in st.cmd. The configuration file for logstash is fellowing:
input {
 tcp {
 host => "${EPICS_IOC_LOG_INET:10.1.236.30}"
 port => "${EPICS_IOC_LOG_PORT:7011}"
 codec => "line"
 }
output {
 file {
 path => "/log/ioc/putlog-%{+YYYY-MM-dd}.json"
 }
}
}
That's all the configuration. I can not figure out who closed the connection, but I think logstash may closed it, because iocLogServer will not. I'll try the tcp_keep_alive option next and to see it would work or not.
To Niko,
If there was another timeout, it would repeat the behavior which I've described.

By the way, I found that the grok filter in the example file is not correct for logstash 7.2
Many Thanks and Regards!
Xuan
> -----原始邮件-----
> 发件人: "J. Lewis Muir" <jlmuir@imca-cat.org>
> 发送时间: 2019-08-16 22:27:39 (星期五)
> 收件人: "Kivel Niko (PSI)" <niko.kivel@psi.ch>
> 抄送: "吴煊" <wux@ihep.ac.cn>, tech-talk <tech-talk@aps.anl.gov>
> 主题: Re: connection timeout between ioc and logstash
> 
> On 08/16, Kivel Niko (PSI) wrote:
> > 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
> 
> That behavior wasn't clear to me in the original message.
> 
> Also, Xuan specifically asked the following:
> 
> > So how can keep the connection all the time without timeout. It seems
> > that using iocLogServer will not lose connection.
> 
> Regards,
> 
> Lewis

Replies:
Re: connection timeout between ioc and logstash Johnson, Andrew N. via Tech-talk
References:
connection timeout between ioc and logstash 吴煊 via Tech-talk
Re: connection timeout between ioc and logstash J. Lewis Muir via Tech-talk
RE: connection timeout between ioc and logstash Kivel Niko (PSI) via Tech-talk
Re: connection timeout between ioc and logstash J. Lewis Muir via Tech-talk

Navigate by Date:
Prev: Re: connection timeout between ioc and logstash J. Lewis Muir via Tech-talk
Next: Re: Undefined Timestamp on Motor Record Johnson, Andrew N. via Tech-talk
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  <20192020 
Navigate by Thread:
Prev: Re: connection timeout between ioc and logstash J. Lewis Muir via Tech-talk
Next: Re: connection timeout between ioc and logstash Johnson, Andrew N. via Tech-talk
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  <20192020 
ANJ, 16 Aug 2019 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·