EPICS Home

Experimental Physics and Industrial Control System


 
1994  1995  1996  1997  1998  1999  <20002001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  <20002001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: alh CA Disconnects
From: Marty Kraimer <[email protected]>
To: Paul Sichta <[email protected]>
Cc: [email protected]
Date: Fri, 21 Jan 2000 09:35:34 -0600
Paul Sichta wrote:
> 
> I have been trying to use alh and am getting sporadic (every 2-3 hours) CA
> disconnect of groups of records.  The alh config file has records in two
> IOC's.  When a disconnect occurs,  all records attached to an IOC disconnect
> and then reconnect the next second.  This happens to both IOC but not at the
> same time.
> 
> The system is lightly loaded.  The TMO variable is 30 seconds and the BEACON
> is 15 seconds.  medm clients and other CA clients on the host do not
> disconnect.  This behavior been the case with the latest alh(1.1.2) and a
> former version.

Are you absolutely certain that no other clients see this. The reason I ask is
that connection management is handled by CA and not the clients. Thus if all
your clients are build against the same version of CA they should have the same
connection management behavior.
 
> The error message I get is shown below (one message for each
> mass-disconnect, not one for each record).  The transient PV alarm states
> are  COMM and INVALID,  and then back to NO_ALARM again the next second.
> 
> Using R3.13.0beta11, mv177 IOC, solaris Host.  "Private" network.  Any
> clues?


Perhaps you are having something happen in your network of which you are not
aware. Do you have a metwork sniffer? Did you pay attention to the discussion
last Dec by Garrett D. Rinehart IPNS here at ANL? It had a lot of valuable
information.

Another possibility. Are your IOCs heavily loaded for some period of time. Since
CA is lowest priority it will not be able to do anything if something else grabs
the cpu. If this happens for a long time the clients will think they lost
communication.

Marty Kraimer


References:
EpicsR3.13.1 CA build Zoltan Kakucs
Re: EpicsR3.13.1 CA build Janet Anderson
alh CA Disconnects Paul Sichta

Navigate by Date:
Prev: alh CA Disconnects Paul Sichta
Next: Data Fanouts Russell Page
Index: 1994  1995  1996  1997  1998  1999  <20002001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: alh CA Disconnects Paul Sichta
Next: ARR not Y2K ready - fix ? Brian McAllister
Index: 1994  1995  1996  1997  1998  1999  <20002001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024