EPICS Controls 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  <20122013  2014  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  <20122013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: RE: Channel Access problem over SSH
From: "Hill, Jeffrey O" <[email protected]>
To: Pavel Masloff <[email protected]>, EPICS Tech Talk <[email protected]>
Date: Mon, 9 Apr 2012 12:59:14 +0000

Hi Pavel,

 

online_notify.c:CA beacon (send to "172.20.255.255:5065") error was "Connection refused"

This probably indicates that the IOC’s IP kernel is unable locate a route to the beacon address 172.20.255.255.

 

To avoid  this type of warning messages, one can modify the CA server beacon destination addresses, independent of the search message destination addresses, using EPICS_CA_AUTO_BEACON_ADDR_LIST and EPICS_CA_BEACON_ADDR_LIST. The server configuration chapter in the CA Reference Manual has some of the details.

 

Jeff

 

From: [email protected] [mailto:[email protected]] On Behalf Of Pavel Masloff
Sent: Saturday, April 07, 2012 12:19 AM
To: EPICS Tech Talk
Subject: Channel Access problem over SSH

 

Hello tech-talkers,


There is an example IOC on a linux machine (Fedora 16) with an IP-address 172.20.92.99/16:
$EPICS_CA_ADDR_LIST=172.20.92.99
$EPICS_CA_AUTO_ADDR_LIST=NO

Which means I can access PVs on the same machine where the IOC is running. It works. No problem.

Now, when I connect to the linux machine via SSH from another machine on the same subnet (Windows XP, Putty), and when I run the IOC from the SSH client, then I get the following message in epics shell (over Putty) every once in a while:

online_notify.c:CA beacon (send to "172.20.255.255:5065") error was "Connection refused"

Still the IOC is running, I can caget, caput, camonitor. The Firewall is off. What might be the case?


Pavel




--
Best regards,


Pavel Maslov, MS
Controls Engineer at Pulsed power Lab
Efremov Institute for Electro-Physical Apparatus
St. Petersburg, Russia

Mobile: +7 (951) 672 22 19
Phone: +7 (812) 461 01 01


Replies:
Re: Channel Access problem over SSH Pavel Masloff
References:
Channel Access problem over SSH Pavel Masloff

Navigate by Date:
Prev: Goodbye and thanks for all the fish Rarback, Harvey M.
Next: does CSS (CAJ?) support CA over an ssh tunnel Peter Milne
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  <20122013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Channel Access problem over SSH Pavel Masloff
Next: Re: Channel Access problem over SSH Pavel Masloff
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  <20122013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 18 Nov 2013 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·