On Thursday 22 January 2009 15:32:47 Mark Rivers wrote:
> I noticed that when I start win32-x86 IOCs built with 3.14.10 I get the
> following message just after iocInit:
>
> *******
> The CA server's beacon address list was empty after initialization?
> *******
>
> I do not get this message when running the identical IOC built with
> 3.14.8.2.
>
> Is this significant? Why am I getting this message?
Highly, it means that the IOC is not sending out any CA beacons at all, which
explains why the clients are not reconnecting to it immediately. Try setting
EPICS_CAS_BEACON_ADDR_LIST on the IOC to your 164.54.160.255 broadcast
address, although it should default to the value of EPICS_CA_ADDR_LIST if not
set so I don't understand why it's ignoring that (unless you have other env
settings for the IOC that you haven't told us about).
- Andrew
--
The best FOSS code is written to be read by other humans -- Harold Welte
- Replies:
- RE: Very slow reconnection to medm after IOC reboot Mark Rivers
- References:
- Very slow reconnection to medm after IOC reboot Mark Rivers
- RE: Very slow reconnection to medm after IOC reboot Mark Rivers
- Navigate by Date:
- Prev:
RE: Very slow reconnection to medm after IOC reboot Mark Rivers
- Next:
RE: Very slow reconnection to medm after IOC reboot Mark Rivers
- 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
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
RE: Very slow reconnection to medm after IOC reboot Mark Rivers
- Next:
RE: Very slow reconnection to medm after IOC reboot Mark Rivers
- 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
2019
2020
2021
2022
2023
2024
|