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: | How to resolve CA beacon routing error messages when rebooting IOC is not helping |
From: | "Tang, Johnny via Tech-talk" <tech-talk at aps.anl.gov> |
To: | "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
Cc: | "Tang, Johnny" <jtang at ornl.gov> |
Date: | Tue, 7 Jul 2020 21:52:32 +0000 |
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:
Thanks. Johnny Tang Spallation Neutron Source Oak Ridge National Laboratory |