Re: How to resolve CA beacon routing error messages when rebooting IOC is not helping

["Hu, Yong via Tech-talk" <tech-talk@aps.anl.gov>]

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@aps.anl.gov> on behalf of "tech-talk@aps.anl.gov" <tech-talk@aps.anl.gov>
Reply-To: jtang <jtang@ornl.gov>
Date: Tuesday, July 7, 2020 at 5:52 PM
To: "tech-talk@aps.anl.gov" <tech-talk@aps.anl.gov>
Cc: jtang <jtang@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