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: connection timeout between ioc and logstash
From: "Johnson, Andrew N. via Tech-talk" <tech-talk@aps.anl.gov>
To: 吴煊 <wux@ihep.ac.cn>, "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 16:43:01 +0000
Hi,

On 8/16/19 10:22 AM, 吴煊 via Tech-talk wrote:
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.
Apparently the default setting for the TCP SO_KEEPALIVE option can be different on different OSs, and the logstash configuration file I presented had not been widely tested (I've been running logstash on MacOS here). The iocLogServer code does explicitly set SO_KEEPALIVE in its acceptNewClient() routine so I think that logstash option will be the correct solution to this problem — please let tech-talk know your results.

By the way, I found that the grok filter in the example file is not correct for logstash 7.2
I developed those regular expressions using http://grokdebug.herokuapp.com/ and logstash 6.3.2 and am currently running 7.0.0, but we're not doing put-logging here yet. If you have a fix for logstash 7.2 I would be interested in seeing it.

Thanks,

- Andrew
-- 
Complexity comes for free, Simplicity you have to work for.

Replies:
Re: connection timeout between ioc and logstash 吴煊 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
Re: Re: connection timeout between ioc and logstash 吴煊 via Tech-talk

Navigate by Date:
Prev: Re: Undefined Timestamp on Motor Record Torsten Bögershausen via Tech-talk
Next: RE: Undefined Timestamp on Motor Record Pearson, Matthew R. 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: Re: connection timeout between ioc and logstash 吴煊 via Tech-talk
Next: Re: connection timeout between ioc and logstash 吴煊 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, 17 Aug 2019 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·