EPICS Home

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  <20132014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: unable to see epics variables
From: James F Ross <[email protected]>
To: EPICS Tech Talk <[email protected]>
Date: Thu, 27 Dec 2012 10:50:52 -0800
Hello everyone,
I am not sure if this is an epics problem or not, but if anyone has any insight I would appreciate the help.  The error is the following:

$> caget fgt:status
CAC: Unable to connect because "No route to host"
CA.Client.Exception...............................................
    Warning: "Virtual circuit disconnect"
    Context: "softioc3.starp.bnl.gov:52008"
    Source File: ../cac.cpp line 1214
    Current Time: Thu Dec 27 2012 13:44:42.760798000
..................................................................
cagChannel connect timed out: 'fgt:status' not found.

I have been unable to find anything blocking a route to the host, and I can ping the host from the machine I am trying the caget on. Historically this has been caused by firewall issues, but even with all security (iptables and selinux) disabled I still get this problem.  Is there anything epics related that can cause this issue?  Something that isn't running but should be in order to allow the command caget to connect? 

It would be helpful to know exactly how caget looks over a network.  Is there a particular port it uses?  Does it look via rsh or NFS or some other connection type that may not be working for some reason?

Three machines spontaneously started having this issue which points to it being a network problem and thus nothing tech talk can help me with, but the fact that I can ping each host from the three machines having problems indicates that there is in fact a network connection and may be epics related.

Thanks for the help,
James Ross

Replies:
RE: unable to see epics variables Mark Rivers

Navigate by Date:
Prev: Re: .PACT .TIME Benjamin Franksen
Next: RE: Error in installing asyn driver Mark Rivers
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: .PACT .TIME Andrew Johnson
Next: RE: unable to see epics variables Mark Rivers
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024