1 |
5313
|
daigle
|
<!--
|
2 |
|
|
* '$RCSfile$'
|
3 |
|
|
* Purpose: web page describing the installation of Metacat
|
4 |
|
|
* Copyright: 2008 Regents of the University of California and the
|
5 |
|
|
* National Center for Ecological Analysis and Synthesis
|
6 |
|
|
* Authors: Chad Berkley
|
7 |
|
|
*
|
8 |
|
|
* '$Author: daigle $'
|
9 |
|
|
* '$Date: 2008-11-19 16:48:24 -0800 (Wed, 19 Nov 2008) $'
|
10 |
|
|
* '$Revision: 4597 $'
|
11 |
|
|
*
|
12 |
|
|
*
|
13 |
|
|
-->
|
14 |
|
|
|
15 |
|
|
<!DOCTYPE html PUBLIC "-//W3C//DTD html 4.0//EN">
|
16 |
|
|
<html>
|
17 |
|
|
|
18 |
|
|
<head>
|
19 |
|
|
<title>Troubleshooting Metacat</title>
|
20 |
|
|
<link rel="stylesheet" type="text/css" href="../user/common.css">
|
21 |
|
|
<link rel="stylesheet" type="text/css" href="./default.css">
|
22 |
|
|
</head>
|
23 |
|
|
|
24 |
|
|
<body>
|
25 |
|
|
|
26 |
|
|
<table width="100%">
|
27 |
|
|
<tr>
|
28 |
|
|
<td class="tablehead" colspan="2"><p class="label">Troubleshooting Metacat</p></td>
|
29 |
|
|
<td class="tablehead" colspan="2" align="right">
|
30 |
|
|
<a href="./testing-metacat.html">Back</a> | <a href="./index.html">Home</a> |
|
31 |
|
|
<!-- a href="put next page here" -->Next<!-- /a -->
|
32 |
|
|
</td>
|
33 |
|
|
</tr>
|
34 |
|
|
</table>
|
35 |
|
|
|
36 |
|
|
<div class="header1">Table of Contents</div>
|
37 |
|
|
<div class="toc">
|
38 |
|
|
<div class="toc1"><a href="#BuildIssues">Build Issues</a></div>
|
39 |
|
|
<div class="toc2"><a href="#HttpServletExceptions">Ant BUILD FAILED : Multiple HttpServlet Exceptions</a></div>
|
40 |
|
|
<div class="toc1"><a href="#InstallationIssues">Installation Issues</a></div>
|
41 |
|
|
<div class="toc1"><a href="#StartupIssues">Startup Issues</a></div>
|
42 |
|
|
<div class="toc2"><a href="#Jdk14Logger">Metacat doesn't start and Jdk14Logger exception</a></div>
|
43 |
|
|
<div class="toc1"><a href="#ConfigurationIssues">Configuration Issues</a></div>
|
44 |
|
|
<div class="toc2"><a href="#DbUpdateIssue">Database Update Fails (not a connectivity issue)</a></div>
|
45 |
|
|
<div class="toc1"><a href="#GeneralApplicationIssues">General Application Issues</a></div>
|
46 |
|
|
<div class="toc2"><a href="#MapDisplayIssue">Maps will not display</a></div>
|
47 |
|
|
<div class="toc1"><a href="#UnitTestingIssues">Unit Testing Issues</a></div>
|
48 |
|
|
<div class="toc2"><a href="#503ServiceTemporarilyUnavailable">Mutliple Tests Fail : 503 Service Temporarily Unavailable</a></div>
|
49 |
|
|
</div>
|
50 |
|
|
|
51 |
|
|
<a name="BuildIssues"></a><div class="header1">Build Issues</div>
|
52 |
|
|
<a name="HttpServletExceptions"></a><div class="header2">Ant BUILD FAILED : Multiple HttpSevlet Exceptions</div>
|
53 |
|
|
<p>During an Ant build of Metacat, you will see many HttpServletRequest, HttpServletResponse and
|
54 |
|
|
other errors. The compiler will complain that it cannot find a symbol, for example:</p>
|
55 |
|
|
<div class="code">
|
56 |
|
|
[javac] /home/daigle/workspace/metacat/build/src/edu/ucsb/nceas/metacat/MetaCatServlet.java:506: cannot find symbol<br>
|
57 |
|
|
[javac] symbol : class HttpServletResponse<br>
|
58 |
|
|
[javac] location: class edu.ucsb.nceas.metacat.MetaCatServlet<br>
|
59 |
|
|
[javac] HttpServletResponse response) throws ServletException, IOException {<br>
|
60 |
|
|
[javac] ^<br>
|
61 |
|
|
</div>
|
62 |
|
|
|
63 |
|
|
<p>This is usually caused by the build not being able to find native Tomcat libraries. edit your
|
64 |
|
|
build.properties file in
|
65 |
|
|
|
66 |
|
|
<a name="InstallationIssues"></a><div class="header1">Installation Issues</div>
|
67 |
|
|
|
68 |
|
|
<a name="StartupIssues"></a><div class="header1">Startup Issues</div>
|
69 |
|
|
<a name="Jdk14Logger"></a><div class="header2">Metacat doesn't start and Jdk14Logger exception</div>
|
70 |
|
|
<p>The symptoms are that the metacat service will not show up at all, even though Tomcat
|
71 |
|
|
is serving, and the following error shows up in the tomcat log (catalina.log):</p>
|
72 |
|
|
|
73 |
|
|
<div class="code">org.apache.commons.logging.LogConfigurationException: User-specified log
|
74 |
|
|
class 'org.apache.commons.logging.impl.Jdk14Logger' cannot be found or is
|
75 |
|
|
not useable </div>
|
76 |
|
|
|
77 |
|
|
<p>This message typically occurs in the tomcat log (catalina.log)
|
78 |
|
|
when Tomcat has been installed on an Ubuntu/Debian system using apt-get install.
|
79 |
|
|
And the application is started using:
|
80 |
|
|
|
81 |
6558
|
leinfelder
|
<div class="code">/etc/init.d/tomcat6 start</div>
|
82 |
5313
|
daigle
|
|
83 |
|
|
<p>The problem is that the standard startup scripts reference the
|
84 |
|
|
common java service, jsvc. Metacat will not run under jsvc. The solutions are:
|
85 |
|
|
<ul>
|
86 |
|
|
<li>Download the <a href="http://knb.ecoinformatics.org/software/download.html">Metacat binary install package</a>
|
87 |
6558
|
leinfelder
|
and replace your /etc/init.d/tomcat6 startup script with the one provided in the
|
88 |
5313
|
daigle
|
package.</li>
|
89 |
|
|
<li>Run Tomcat from the Tomcat binary directory: <tomcat_home>/bin/startup.sh and
|
90 |
|
|
<tomcat_home>/bin/shutdown.sh</li>
|
91 |
|
|
</ul>
|
92 |
|
|
</p>
|
93 |
|
|
<a name="ConfigurationIssues"></a><div class="header1">Configuration Issues</div>
|
94 |
|
|
<a name="DbUpdateIssue"></a><div class="header2">Database Update Fails (not a connectivity issue)</div>
|
95 |
|
|
<p>There are a number of reasons why the database update utility might fail during
|
96 |
|
|
configuration. You will need to determine if the error returned indicates a connectivity issue
|
97 |
|
|
or some issue with the database schema/data. If it is the latter, the first step in
|
98 |
|
|
troubleshooting the issue is to run the db scripts manually and analyze the output.</p>
|
99 |
|
|
|
100 |
|
|
<p>The configuration utility will report which scripts it tried to run. To
|
101 |
|
|
run these scripts, refer to
|
102 |
|
|
<a href="../user/run-db-scripts.html">how to run database scripts</a></p>
|
103 |
|
|
|
104 |
|
|
<p>If the answer is not obvious, further troubleshooting may require a database
|
105 |
|
|
administrator.</p>
|
106 |
|
|
|
107 |
|
|
<a name="GeneralApplicationIssues"></a><div class="header1">General Application Issues</div>
|
108 |
|
|
<a name="MapDisplayIssue"></a><div class="header2">Maps will not display</div>
|
109 |
|
|
<p>There are two known reasons why maps might not display in a web browser.</p>
|
110 |
|
|
<ul>
|
111 |
|
|
<li>Sarfari Browser - the safari browser is not supported by the map libraries. You will
|
112 |
|
|
need to switch to a different browser.</li>
|
113 |
|
|
<li>Firefox Browser with the Firebug plugin - Firebug is a plugin that allows a developer
|
114 |
|
|
to easily view and troubleshoot web page layouts. Unfortunately, this plugin can
|
115 |
|
|
keep the maps from displaying. There is no plan by the third party map display
|
116 |
|
|
developers to address this issue. You will need to disable Firebug in your
|
117 |
|
|
browser.</li>
|
118 |
|
|
</ul>
|
119 |
|
|
|
120 |
|
|
<a name="UnitTestingIssues"></a><div class="header1">Unit Testing Issues</div>
|
121 |
|
|
<a name="503ServiceTemporarilyUnavailable"></a><div class="header2">Mutliple Tests Fail : 503 Service Temporarily Unavailable</div>
|
122 |
|
|
<p>When running "ant test", multiple tests fail. The output files have the error: </p>
|
123 |
|
|
<div class="code">503 Service Temporarily Unavailable</div>
|
124 |
|
|
<p>This typically means your Metacat server is not running.</p>
|
125 |
|
|
|
126 |
|
|
<br>
|
127 |
|
|
|
128 |
|
|
<a href="./testing-metacat.html">Back</a> | <a href="./index.html">Home</a> |
|
129 |
|
|
<!--a href="add next file here when one exists" -->Next<!-- /a -->
|
130 |
|
|
</body>
|
131 |
|
|
</html>
|