EPICS Home EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

Format page
for printing


Search Tech-talk
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  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 
<== Date ==> <== Thread ==>
Subject: Re: How to resolve CA beacon routing error messages when rebooting IOC is not helping
From: "Hu, Yong via Tech-talk" <tech-talk at aps.anl.gov>
To: jtang <jtang at ornl.gov>, "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>
Date: Tue, 7 Jul 2020 22:31:29 +0000

Use two variables in your startup script (st.cmd) to suppress the messages:

epicsEnvSet("EPICS_CA_AUTO_ADDR_LIST", "NO")

epicsEnvSet("EPICS_CA_ADDR_LIST", "your-CA-network-broadcast-like*.*.*.255)")

 

 

From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>
Reply-To: jtang <jtang at ornl.gov>
Date: Tuesday, July 7, 2020 at 5:52 PM
To: "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>
Cc: jtang <jtang at ornl.gov>
Subject: How to resolve CA beacon routing error messages when rebooting IOC is not helping

 

Many of our operational IOCs at SNS are flooded with following CA error messages:

…

./online_notify.c: CA beacon routing (connect to "172.31.127.255:5065") error was

"S_errno_EHOSTUNREACH"

 

../online_notify.c: CA beacon routing (connect to "172.31.75.255:5065") error was

"S_errno_EHOSTUNREACH"

 

../online_notify.c: CA beacon routing (connect to "172.31.83.255:5065") error was

"S_errno_EHOSTUNREACH"

 

../online_notify.c: CA beacon routing (connect to "172.31.91.255:5065") error was

"S_errno_EHOSTUNREACH"

 

../online_notify.c: CA beacon routing (connect to "172.31.127.255:5065") error was

"S_errno_EHOSTUNREACH"

 

../online_notify.c: CA beacon routing (connect to "172.31.75.255:5065") error was

 

Like to hear any related experiences from anyone to resolve this or redirect the messages:

  1. Adding an environment variable to slow down the CA error message output
  2. Or redirect messages to files
  3. What to do to resolve the errors ?

 

Thanks.

 

Johnny Tang

Spallation Neutron Source

Oak Ridge National Laboratory

 

 

References:
How to resolve CA beacon routing error messages when rebooting IOC is not helping Tang, Johnny via Tech-talk
Navigate by Date:
Prev: How to resolve CA beacon routing error messages when rebooting IOC is not helping Tang, Johnny via Tech-talk
Next: Re: Re: Epics iocInit() fandayu--- via Tech-talk
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: How to resolve CA beacon routing error messages when rebooting IOC is not helping Tang, Johnny via Tech-talk
Next: Get/Set Local Variable in motorAxis From sub Record William Cork via Tech-talk
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 
ANJ, 08 Jul 2020 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·