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  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 
<== Date ==> <== Thread ==>

Subject: RE: Channel Access problem over SSH
From: <michael.abbott@diamond.ac.uk>
To: <pavel.masloff@gmail.com>
Cc: tech-talk@aps.anl.gov
Date: Tue, 17 Apr 2012 13:53:55 +0000
From: tech-talk-bounces@aps.anl.gov [mailto:tech-talk-bounces@aps.anl.gov] On Behalf Of Pavel Masloff
> Look. I have noticed that even when I am normally starting
> an IOC on a linux machine, then I get these messages:
> online_notify.c:CA beacon (send to "172.20.255.255:5065") error was "Connection refused"

These messages are an old old chestnut and a pain in the bum.  We get them here all the time on our development network, and I understand that they're triggered by a misconfigured IOC somewhere on our network incorrectly responding to discovery packets (or something like that).  I would so much like to see the offending machine thrown in the bin, but apparently it's too hard to fix or something.

>From what I remember being told, the offending machine doesn't understand our /20 network and is incapable of understanding anything that isn't a class A B or C network.  Why this should affect every other IOC machine on the same network is, I confess, a mystery to me.

-- 
This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd. 
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
 





Replies:
Re: Channel Access problem over SSH Andrew Johnson
References:
Channel Access problem over SSH Pavel Masloff
RE: Channel Access problem over SSH Hill, Jeffrey O
Re: Channel Access problem over SSH Pavel Masloff

Navigate by Date:
Prev: Re: Channel Access problem over SSH Pavel Masloff
Next: How to debug record processing? Nerses Gevorgyan
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 
Navigate by Thread:
Prev: Re: Channel Access problem over SSH Pavel Masloff
Next: Re: Channel Access problem over SSH Andrew Johnson
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 
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 ·