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: Troubleshoot "Appliance Down" Issue in EPICS Archiver Applianc |
From: | "Shankar, Murali" <[email protected]> |
To: | "[email protected]" <[email protected]> |
Cc: | "[email protected]" <[email protected]> |
Date: | Mon, 8 May 2017 14:48:29 +0000 |
>> What would be the cause?
The root cause is that your mgmt webapp is having trouble communicating with the engine webapp. You can look into this a bit more by trying the URL yourself from the command line using curl. Also, looking in the engine's logs will help. If you suspect the
engine is non-responsive, you can get a stack trace and then see what the threads are doing. Is there anything in the engine's logs? Does top show anything on the engine?
Exception getting contents of internal URL http://10.2.0.23:17666/engine/bpl/getVersion
org.apache.http.conn.HttpHostConnectException: Connect to 10.2.0.23:17666 [/10.2.0.23] failed: Connection refused
>> Another thing I had to restart the entire engine from the sampleStartup.sh script >> Is there a simpler way to start a single appliance only? I suspect you mean "I had to restart the entire appliance" and "Is
there a simpler way to start a single component only"
Ultimately, these are all Tomcat containers; so you should be able to stop/start them any of the methods available for stopping/starting Tomcat. I assume you are using jsvc; in which case, stopping a component is simply adding a -stop argument to the jsvc
command like so -pidfile ${CATALINA_BASE}/pid \
-stop \
org.apache.catalina.startup.Bootstrap
Hope that helps.
Regards,
Murali
|