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:
- Adding an environment variable to slow down the CA error message output
- Or redirect messages to files
- What to do to resolve the errors ?
Thanks.
Johnny Tang
Spallation Neutron Source
Oak Ridge National Laboratory