Experimental Physics and
Industrial Control System

John,

One possibility is that during this 10-20 seconds some task in 
your IOC at a higher priority than the CA repeater is using 
all of the CPU. You can use "spyClkStart" and "spyReport" to
see if this is the case.

Otherwise, this might be caused by an unusual port configuration 
for the CA client. When you type inetstatShow you should see a UDP 
CA repeater daemon on port 5065.

Jeff 



> -----Original Message-----
> From: john sinclair [mailto:[email protected]]
> Sent: Friday, January 18, 2002 9:53 AM
> To: tech talk
> Subject: IOC mesage at startup
> 
> 
> Arch = x86
> EPICS = R3.13.4
> VxWorks = tornado 2
> 
> I am getting the following message around 10-20 seconds after an iocInit:
> 
>   Unable to contact CA repeater after 50 tries
>   Silence this message by starting a CA repeater daemon
> 
> What does this mean?
> 
> Examining VxWorks tasks gives (among other things)
> 
>   CA_repeater3e65f04   3cd9650 181 PEND   14db1c  3cd94d8   0  0
> 
> 
> Its seems that this message is a recent occurrence, but I don't think I
> have made any system level changes recently.
> 
> John Sinclair
> [email protected]
> Oak Ridge National Lab
> 865-576-6362   865-574-1268 (fax)
> 

References:

IOC mesage at startup john sinclair

Navigate by Date:

Prev: [no subject] Lynn Foth

Next: LeCroy 4300B FERA search Paul Sichta

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: IOC mesage at startup john sinclair

Next: caTCL with R3.14 and Linux Benjamin Sailer

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