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 2025 | 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 2025 |
<== Date ==> | <== Thread ==> |
---|
Subject: | RE: EPICS Archiver Appliance web interface error |
From: | 김지화(빔라인장치팀) <[email protected]> |
To: | "Shankar, Murali" <[email protected]>, "[email protected]" <[email protected]> |
Date: | Fri, 11 Mar 2016 23:01:00 +0000 |
Hi Murali, I've attached server.xml file.
I found error lines according to "xmllint server.xml" and fixed that line.
I did stop and restart sampleStartup.sh but web client displayed same error.
[root@localhost apache-tomcat-7.0.68]# ./sampleStartup.sh stop
Stopping tomcat at location /opt/archappl/apache-tomcat-7.0.68/engine /opt/archappl/apache-tomcat-7.0.68/engine/logs /opt/archappl/apache-tomcat-7.0.68 /opt/archappl/apache-tomcat-7.0.68 Stopping tomcat at location /opt/archappl/apache-tomcat-7.0.68/retrieval /opt/archappl/apache-tomcat-7.0.68/retrieval/logs /opt/archappl/apache-tomcat-7.0.68 /opt/archappl/apache-tomcat-7.0.68 Stopping tomcat at location /opt/archappl/apache-tomcat-7.0.68/etl /opt/archappl/apache-tomcat-7.0.68/etl/logs /opt/archappl/apache-tomcat-7.0.68 /opt/archappl/apache-tomcat-7.0.68 Stopping tomcat at location /opt/archappl/apache-tomcat-7.0.68/mgmt /opt/archappl/apache-tomcat-7.0.68/mgmt/logs /opt/archappl/apache-tomcat-7.0.68 /opt/archappl/apache-tomcat-7.0.68 [root@localhost apache-tomcat-7.0.68]# ./sampleStartup.sh start
Starting tomcat at location /opt/archappl/apache-tomcat-7.0.68/mgmt Using 64 bit versions of libraries /opt/archappl/apache-tomcat-7.0.68/mgmt/logs /opt/archappl/apache-tomcat-7.0.68 /opt/archappl/apache-tomcat-7.0.68 Starting tomcat at location /opt/archappl/apache-tomcat-7.0.68/engine Using 64 bit versions of libraries /opt/archappl/apache-tomcat-7.0.68/engine/logs /opt/archappl/apache-tomcat-7.0.68 /opt/archappl/apache-tomcat-7.0.68 Starting tomcat at location /opt/archappl/apache-tomcat-7.0.68/etl Using 64 bit versions of libraries /opt/archappl/apache-tomcat-7.0.68/etl/logs /opt/archappl/apache-tomcat-7.0.68 /opt/archappl/apache-tomcat-7.0.68 Starting tomcat at location /opt/archappl/apache-tomcat-7.0.68/retrieval Using 64 bit versions of libraries /opt/archappl/apache-tomcat-7.0.68/retrieval/logs /opt/archappl/apache-tomcat-7.0.68 /opt/archappl/apache-tomcat-7.0.68 [root@localhost apache-tomcat-7.0.68]# Regards,
Jihwa
보낸 사람: Shankar, Murali <[email protected]>
보낸 날짜: 2016년 3월 12일 토요일 오전 6:38 받는 사람: 김지화(빔라인장치팀); [email protected] 제목: Re: EPICS Archiver Appliance web interface error It is very likely the file /opt/archappl/apache-tomcat-7.0.68/conf/server.xml has syntax errors; could you run this thru xmllint
to validate? Alternatively, you can send me the server.xml and I can look at it for you...
Regards, Murali
SEVERE: Parse Fatal Error at line 144 column 5: The element type "Server" must be terminated by the matching end-tag "</Server>". org.xml.sax.SAXParseException; systemId: file:/opt/archappl/apache-tomcat-7.0.68/conf/server.xml; lineNumber: 144; columnNumber: 5; The element type "Server" must be terminated by the matching end-tag "</Server>". at com.sun.org.apache.xerces.internal
From: 김지화(빔라인장치팀) <[email protected]>
Sent: Friday, March 11, 2016 12:40 PM To: Shankar, Murali; [email protected] Subject: EPICS Archiver Appliance web interface error Hi Murali, Did you fix this problem?
CentOS release 6.7 (Final) java version "1.8.0_73" Java(TM) SE Runtime Environment (build 1.8.0_73-b02) mysql Ver 14.14 Distrib 5.1.73, for redhat-linux-gnu (x86_64) using readline 5.1 archappl_v0.0.1_SNAPSHOT_23-September-2015T07-41-14.tar.gz apache-tomcat-7.0.68.tar.gz mysql-connector-java-5.1.38.tar.gz I can see apache default pages.
http://localhost:17665/mgmt/ui/index.html HTTP Status 503 - This appliance is still starting up. Please wait a few minutes before trying again. Thank you for your patience. type Status report message This appliance is still starting up. Please wait a few minutes before trying again. Thank you for your patience. description The requested service is not currently available. Apache Tomcat/7.0.68B And I've attached error message.
Best regards,
Jihwa Kim Control & DAQ Pohang Accelerator Laboratory
|
<?xml version='1.0' encoding='utf-8'?> <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to You under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. --> <!-- Note: A "Server" is not itself a "Container", so you may not define subcomponents such as "Valves" at this level. Documentation at /docs/config/server.html --> <Server port="8005" shutdown="SHUTDOWN"> <Listener className="org.apache.catalina.startup.VersionLoggerListener" /> <!-- Security listener. Documentation at /docs/config/listeners.html <Listener className="org.apache.catalina.security.SecurityListener" /> --> <!--APR library loader. Documentation at /docs/apr.html --> <Listener className="org.apache.catalina.core.AprLifecycleListener" SSLEngine="on" /> <!--Initialize Jasper prior to webapps are loaded. Documentation at /docs/jasper-howto.html --> <Listener className="org.apache.catalina.core.JasperListener" /> <!-- Prevent memory leaks due to use of particular java/javax APIs--> <Listener className="org.apache.catalina.core.JreMemoryLeakPreventionListener" /> <Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener" /> <Listener className="org.apache.catalina.core.ThreadLocalLeakPreventionListener" /> <!-- Global JNDI resources Documentation at /docs/jndi-resources-howto.html --> <GlobalNamingResources> <!-- Editable user database that can also be used by UserDatabaseRealm to authenticate users --> <Resource name="UserDatabase" auth="Container" type="org.apache.catalina.UserDatabase" description="User database that can be updated and saved" factory="org.apache.catalina.users.MemoryUserDatabaseFactory" pathname="conf/tomcat-users.xml" /> </GlobalNamingResources> <!-- A "Service" is a collection of one or more "Connectors" that share a single "Container" Note: A "Service" is not itself a "Container", so you may not define subcomponents such as "Valves" at this level. Documentation at /docs/config/service.html --> <Service name="Catalina"> <!--The connectors can use a shared executor, you can define one or more named thread pools--> <!-- <Executor name="tomcatThreadPool" namePrefix="catalina-exec-" maxThreads="150" minSpareThreads="4"/> --> <!-- A "Connector" represents an endpoint by which requests are received and responses are returned. Documentation at : Java HTTP Connector: /docs/config/http.html (blocking & non-blocking) Java AJP Connector: /docs/config/ajp.html APR (HTTP/AJP) Connector: /docs/apr.html Define a non-SSL HTTP/1.1 Connector on port 8080 --> <Connector port="17665" protocol="HTTP/1.1" connectionTimeout="20000" redirectPort="8443" /> <!-- A "Connector" using the shared thread pool--> <!-- <Connector executor="tomcatThreadPool" port="8080" protocol="HTTP/1.1" connectionTimeout="20000" redirectPort="8443" /> --> <!-- Define a SSL HTTP/1.1 Connector on port 8443 This connector uses the BIO implementation that requires the JSSE style configuration. When using the APR/native implementation, the OpenSSL style configuration is required as described in the APR/native documentation --> <!-- <Connector port="8443" protocol="org.apache.coyote.http11.Http11Protocol" maxThreads="150" SSLEnabled="true" scheme="https" secure="true" clientAuth="false" sslProtocol="TLS" /> --> <!-- Define an AJP 1.3 Connector on port 8009 --> <!-- Connector port="8009" protocol="AJP/1.3" redirectPort="8443" /--> <!-- Server port="8005" shutdown="SHUTDOWN" --> <!-- An Engine represents the entry point (within Catalina) that processes every request. The Engine implementation for Tomcat stand alone analyzes the HTTP headers included with the request, and passes them on to the appropriate Host (virtual host). Documentation at /docs/config/engine.html --> <!-- You should set jvmRoute to support load-balancing via AJP ie : <Engine name="Catalina" defaultHost="localhost" jvmRoute="jvm1"> --> <Engine name="Catalina" defaultHost="localhost"> <!--For clustering, please take a look at documentation at: /docs/cluster-howto.html (simple how to) /docs/config/cluster.html (reference documentation) --> <!-- <Cluster className="org.apache.catalina.ha.tcp.SimpleTcpCluster"/> --> <!-- Use the LockOutRealm to prevent attempts to guess user passwords via a brute-force attack --> <Realm className="org.apache.catalina.realm.LockOutRealm"> <!-- This Realm uses the UserDatabase configured in the global JNDI resources under the key "UserDatabase". Any edits that are performed against this UserDatabase are immediately available for use by the Realm. --> <Realm className="org.apache.catalina.realm.UserDatabaseRealm" resourceName="UserDatabase"/> </Realm> <Host name="localhost" appBase="webapps" unpackWARs="true" autoDeploy="true"> <!-- SingleSignOn valve, share authentication between web applications Documentation at: /docs/config/valve.html --> <!-- <Valve className="org.apache.catalina.authenticator.SingleSignOn" /> --> <!-- Access log processes all example. Documentation at: /docs/config/valve.html Note: The pattern used is equivalent to using pattern="common" --> <Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs" prefix="localhost_access_log." suffix=".txt" pattern="%h %l %u %t "%r" %s %b" /> </Host> </Engine> </Service> </Server>