tag:help-archives.hannonhill.com,2010-02-09:/discussions/installation/163-production-cms-downCascade CMS: Discussion 2012-11-02T12:55:29Ztag:help-archives.hannonhill.com,2010-02-09:Comment/90630922011-08-03T20:22:56Z2011-08-03T20:22:56ZProduction CMS Down<div><p>This is a strange one that I haven't seen before. I checked your
<em>catalina.out</em> file and noticed over 10,000 occurrences of
the following error message:</p>
<pre>
<code>SEVERE: Error deploying configuration descriptor ._manager.xml
org.xml.sax.SAXParseException: Content is not allowed in prolog.</code>
</pre>
<p>and:</p>
<pre>
<code>SEVERE: Error deploying configuration descriptor ._host-manager.xml
org.xml.sax.SAXParseException: Content is not allowed in prolog.</code>
</pre>
<p>The 'content is not allowed in prolog' portion of this typically
means that the XML configuration file in question is not valid. The
particular files it is referring to are not configured manually,
and I'm not sure how this could happen aside from a bad install
(perhaps?) or just a random issue with the application accessing
those files (which I have never seen before).</p>
<p>The messages in the <em>cascade.log</em> file appear to
suggesting that the connection to the database was closed and/or
the database is not responding:</p>
<pre>
<code>2011-08-03 00:00:06,738 WARN [JDBCExceptionReporter] SQL Error: 0, SQLState: 08001
2011-08-03 00:00:06,742 ERROR [JDBCExceptionReporter] Server connection failure during transaction. Due to underlying exception: 'java.net.ConnectException: Connection refused'.</code>
</pre>
<p>I assume this could be something that happened <em>due</em> to
the issues that are present in the <em>catalina.out</em> file.</p>
<p>When you applied the upgrade, did you make sure to delete the
/tomcat/temp and /tomcat/work directories?</p></div>Timtag:help-archives.hannonhill.com,2010-02-09:Comment/90630922011-08-03T20:31:05Z2011-08-03T20:31:05ZProduction CMS Down<div><blockquote>
<p>When you applied the upgrade, did you make sure to delete the
/tomcat/temp and /tomcat/work directories?</p>
</blockquote>
<p>I <em>think</em> so. I'm pretty that each time I did the upgrade
(3 attempts!) I released a fresh copy that didn't have any log
files, temp files, etc.</p>
<p>Thoughts? How should I proceed? I really don't want to revert
the database and application back to 6.4.5, but if it needs to
happen it should happen asap…</p>
<p>Ian</p></div>irifkintag:help-archives.hannonhill.com,2010-02-09:Comment/90630922011-08-03T20:41:06Z2011-08-03T20:41:06ZProduction CMS Down<div><p>Well, you mentioned that it's up and running now, correct? Check
the <em>catalina.out</em> file and see if it's still throwing
errors (after 4pm) like the ones I mentioned <a href=
"http://help.hannonhill.com/discussions/installation/163-production-cms-down#comment_9063647">
above</a>. If it is, I would assume there could be a potential
issue with some temporary files that may not have been cleared out
before (from the temp and work directories).</p>
<p>We haven't had anyone run into this, so it appears to be
isolated to your environment. One thing you could try is doing a
completely fresh installation to a separate directory, then running
that against your production database.</p></div>Timtag:help-archives.hannonhill.com,2010-02-09:Comment/90630922011-08-03T20:44:37Z2011-08-03T20:44:37ZProduction CMS Down<div><p>I'm still seeing those errors:</p>
<p>Aug 3, 2011 4:44:05 PM org.apache.catalina.startup.HostConfig
deployDescriptor<br>
SEVERE: Error deploying configuration descriptor
._host-manager.xml<br>
org.xml.sax.SAXParseException: Content is not allowed in
prolog.</p>
<pre>
<code> at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1231)
at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522)
at org.apache.tomcat.util.digester.Digester.parse(Digester.java:1546)
at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:583)
at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:553)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:488)
at org.apache.catalina.startup.HostConfig.check(HostConfig.java:1206)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:293)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:120)
at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1306)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1570)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1579)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1559)
at java.lang.Thread.run(Thread.java:662)</code>
</pre>
<p>Aug 3, 2011 4:44:05 PM org.apache.tomcat.util.digester.Digester
fatalError<br>
SEVERE: Parse Fatal Error at line 1 column 1: Content is not
allowed in prolog.<br>
org.xml.sax.SAXParseException: Content is not allowed in
prolog.</p>
<pre>
<code> at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195)
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:174)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:388)
at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1414)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:1039)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:511)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:808)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205)
at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522)
at org.apache.tomcat.util.digester.Digester.parse(Digester.java:1546)
at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:583)
at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:553)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:488)
at org.apache.catalina.startup.HostConfig.check(HostConfig.java:1206)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:293)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:120)
at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1306)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1570)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1579)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1559)
at java.lang.Thread.run(Thread.java:662)</code>
</pre>
<p>Aug 3, 2011 4:44:05 PM org.apache.catalina.startup.HostConfig
deployDescriptor<br>
SEVERE: Error deploying configuration descriptor ._manager.xml<br>
org.xml.sax.SAXParseException: Content is not allowed in
prolog.</p>
<pre>
<code> at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1231)
at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522)
at org.apache.tomcat.util.digester.Digester.parse(Digester.java:1546)
at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:583)
at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:553)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:488)
at org.apache.catalina.startup.HostConfig.check(HostConfig.java:1206)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:293)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:120)
at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1306)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1570)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1579)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1559)
at java.lang.Thread.run(Thread.java:662)</code>
</pre></div>irifkintag:help-archives.hannonhill.com,2010-02-09:Comment/90630922011-08-03T20:49:46Z2011-08-03T20:49:46ZProduction CMS Down<div><blockquote>
<p>We haven't had anyone run into this, so it appears to be
isolated to your environment.</p>
</blockquote>
<p>How many customers do you know are running 6.8.3.1? Are they on
64-bit unix with mysql? How big are their databases?</p>
<p>Maybe there's a particular configuration of mysql that needs to
be adjusted???</p>
<blockquote>
<p>One thing you could try is doing a completely fresh installation
to a separate directory, then running that against your production
database.</p>
</blockquote>
<p>This does not sound like a good idea. Running two instances at
the same time against the production database? I would imagine that
could easily cause more problems.</p>
<p>Thoughts?</p>
<p>Ian</p></div>irifkintag:help-archives.hannonhill.com,2010-02-09:Comment/90630922011-08-03T21:40:45Z2011-08-03T21:40:45ZProduction CMS Down<div><p>It's possible that there is a MySQL configuration that needs to
be adjusted. Looking over your logs some more, I noticed some more
troubling database connection errors:</p>
<pre>
<code>org.quartz.impl.jdbcjobstore.LockException: Failure obtaining db row lock: Connection is read-only. Queries leading to data modification are not allowed [See nested exception: java.sql.SQLException: Connection is read-only. Queries leading to data modification are not allowed]</code>
</pre>
<p>and:</p>
<pre>
<code>** BEGIN NESTED EXCEPTION **
java.net.ConnectException
MESSAGE: Connection refused
STACKTRACE:
java.net.ConnectException: Connection refused</code>
</pre>
<p>So, clearly there are some issues with the database connection.
I'm hoping this doesn't have anything to do with the changes that
you had to make earlier re: the locks. So far I haven't really
found anything decisive online about whether or not that could
cause these types of problems.</p>
<blockquote>
<p>This does not sound like a good idea. Running two instances at
the same time against the production database? I would imagine that
could easily cause more problems.</p>
</blockquote>
<p>Sorry, I should have clarified. This would not be two instances
at once. I meant to install to a separate directory and shut down
the old instance. Then, run the instance from the new directory to
see if that cleared up some of the strange errors that were in
<em>catalina.out</em>.</p></div>Timtag:help-archives.hannonhill.com,2010-02-09:Comment/90630922011-08-03T22:44:57Z2011-08-03T22:44:57ZProduction CMS Down<div><blockquote>
<p>I meant to install to a separate directory and shut down the old
instance.</p>
</blockquote>
<p>Oh, okay. That's fairly trivial. Is this what you recommend as a
next step?</p>
<p>Thanks,<br>
Ian</p></div>irifkintag:help-archives.hannonhill.com,2010-02-09:Comment/90630922011-08-04T14:26:54Z2011-08-04T14:27:55ZProduction CMS Down<div><p>Hi again,</p>
<p>In today's catalina.out, so far I don't see the "Failure
obtaining db row lock" or the "java.net.ConnectException" error
messages. However, I do see the following "SEVERE" error
messages:</p>
<p>1 occurrence of SEVERE: Context [/.<em>ROOT] startup failed due
to previous errors<br>
3377 occurrences of SEVERE: Error deploying configuration
descriptor .</em>host-manager.xml<br>
3377 occurrences of SEVERE: Error deploying configuration
descriptor ._manager.xml<br>
1 occurrence of SEVERE: Error getConfigured<br>
1 occurrence of SEVERE: Error in resourceStart()<br>
1 occurrence of SEVERE: Error starting static Resources<br>
1 occurrence of SEVERE: Exception fixing docBase: {0}<br>
6754 occurrences of SEVERE: Parse Fatal Error at line 1 column 1:
Content is not allowed in prolog.</p>
<p>Thoughts? How should we proceed?</p>
<p>Thanks,<br>
Ian</p></div>irifkintag:help-archives.hannonhill.com,2010-02-09:Comment/90630922011-08-04T14:40:16Z2011-08-04T14:40:48ZProduction CMS Down<div><p>Ian,</p>
<p>Those errors are quite odd, typically they mean that there is a
syntax error within a configuration file. Could you attach the
files below so that I can compare them to our original copies?
Please first check them for blank lines or spaces at the top, as
the following error message typically means that there is a space
or new line at the top of the file (most likely
<strong>._manager.xml</strong> and/or
<strong>.host-manager.xml</strong>).</p>
<p>/tomcat/conf/Catalina/localhost/host-manager.xml
/Applications/CScharlie573/tomcat/server/webapps/host-manager/host-manager.xml</p>
<pre>
<code>6754 occurrences of SEVERE: Parse Fatal Error at line 1 column 1: Content is not allowed in prolog.</code>
</pre>
<ul>
<li>/tomcat/conf/Catalina/localhost/host-manager.xml</li>
<li>/tomcat/server/webapps/host-manager/host-manager.xml</li>
<li>/tomcat/conf/Catalina/localhost/manager.xml</li>
<li>/tomcat/server/webapps/manager/manager.xml</li>
</ul>
<p>If you find any files within any of these locations prepended
with ".<em>" (i.e. .</em>manager.xml and/or .host-manager.xml)
please check these as well.</p>
<p>Thanks!</p></div>Joeltag:help-archives.hannonhill.com,2010-02-09:Comment/90630922011-08-04T15:18:17Z2011-08-04T15:18:17ZProduction CMS Down<div><p>Hi,</p>
<p>Attached are the requested files. I included the folder
structure so you can tell which is which. There with "._" files in
each directory, which I also included.</p>
<p>Ian</p></div>irifkintag:help-archives.hannonhill.com,2010-02-09:Comment/90630922011-08-04T19:10:32Z2011-08-04T19:10:32ZProduction CMS Down<div><p>Ian,</p>
<p>Please try editing your
<em>/tomcat/server/webapps/manager/manager.xml</em> file and remove
the 2 spaces before the following code that exists on each line.
Please see the attached screenshot for further reference, as the
spaces that need to be deleted are shown in <strong>black</strong>
text.</p>
<pre>
<code><!-- Link to the user database we will get roles from -->
<ResourceLink name="users" global="UserDatabase"</code>
</pre>
<p>Thanks!</p></div>Joeltag:help-archives.hannonhill.com,2010-02-09:Comment/90630922011-08-04T19:20:31Z2011-08-04T19:20:31ZProduction CMS Down<div><p>Hi,</p>
<p>I see the spaces and have removed them. Does this require a
restart? What are the next steps?</p>
<p>For what it's worth, I just checked and I also see these errors
in our test instance.</p>
<p>Also, Cascade doesn't seem to have crashed today yet. That
doesn't mean the problem is solved, but figured I'd mention it.</p>
<p>Thanks,<br>
Ian</p></div>irifkintag:help-archives.hannonhill.com,2010-02-09:Comment/90630922011-08-04T19:29:16Z2011-08-04T19:29:16ZProduction CMS Down<div><p>Ian,</p>
<p>Yes this will require a restart before the changes are enabled.
Please let me know what you find after a restart.</p>
<p>Thanks!</p></div>Joeltag:help-archives.hannonhill.com,2010-02-09:Comment/90630922011-08-04T19:32:03Z2011-08-04T19:32:03ZProduction CMS Down<div><p>Hi again,</p>
<p>Do you see this as urgent to restart now? I ask because Web
editors are in there doing their thing. If not urgent, we have a
scheduled nightly restart.</p>
<p>Thanks,<br>
Ian</p></div>irifkintag:help-archives.hannonhill.com,2010-02-09:Comment/90630922011-08-04T20:27:43Z2011-08-04T20:27:43ZProduction CMS Down<div><p>Ian,</p>
<p>No I don't see this as an urgent item as it is not impeding
anything. Please restart whenever you have a window of downtime and
let us know if the problem continues afterward.</p>
<p>Thanks!</p></div>Joeltag:help-archives.hannonhill.com,2010-02-09:Comment/90630922011-08-08T14:17:35Z2011-08-08T14:18:18ZProduction CMS Down<div><p>Hi,</p>
<p>As far as I know our instance of Cascade has not crashed again
yet. As I mentioned, it restarts nightly. I just checked today's
copy of catalina.out and doing a search for severe logs and
counting the occurrences I see the following:</p>
<p>1 SEVERE: Context [/.<em>ROOT] startup failed due to previous
errors<br>
3200 SEVERE: Error deploying configuration descriptor
.</em>host-manager.xml<br>
3200 SEVERE: Error deploying configuration descriptor
._manager.xml<br>
1 SEVERE: Error getConfigured<br>
1 SEVERE: Error in resourceStart()<br>
1 SEVERE: Error starting static Resources<br>
1 SEVERE: Exception fixing docBase: {0}<br>
6400 SEVERE: Parse Fatal Error at line 1 column 1: Content is not
allowed in prolog.</p>
<p>Thoughts?</p>
<p>Thanks,<br>
Ian</p></div>irifkintag:help-archives.hannonhill.com,2010-02-09:Comment/90630922011-08-08T21:26:50Z2011-08-08T21:26:50ZProduction CMS Down<div><p>Ian,</p>
<p>Could you try removing the following files entirely:</p>
<ul>
<li>/tomcat/conf/Catalina/localhost/host-manager.xml</li>
<li>/tomcat/server/webapps/host-manager/host-manager.xml</li>
<li>/tomcat/conf/Catalina/localhost/manager.xml</li>
<li>/tomcat/server/webapps/manager/manager.xml</li>
</ul>
<p>After these have been removed, please restart Cascade Server and
let me know if this problem reoccurs. Also, do you have any more
information or context for this error? Did a user notice anything
when it occurred? Did you just happen to notice it within the
logs?</p>
<p>Thanks!</p></div>Joeltag:help-archives.hannonhill.com,2010-02-09:Comment/90630922011-08-08T21:51:50Z2011-08-08T21:51:50ZProduction CMS Down<div><p>Hi Joel,</p>
<blockquote>
<p>Could you try removing the following files</p>
</blockquote>
<p>Sure, I can remove those file.</p>
<blockquote>
<p>do you have any more information or context for this error? Did
a user notice anything when it occurred? Did you just happen to
notice it within the logs?</p>
</blockquote>
<p>Cascade crashed the day after upgrading to 6.8.3.1. I opened
this ticket about Cascade crashing and attached my log files. Tim
noticed this error.</p>
<p>I'm following up with this because I was under the impression
that this is related to why our instance of Cascade was down.</p>
<p>Let me know if I misunderstood something.</p>
<p>Thanks,<br>
Ian</p></div>irifkintag:help-archives.hannonhill.com,2010-02-09:Comment/90630922011-08-09T12:26:18Z2011-08-09T12:26:18ZProduction CMS Down<div><p>Ian,</p>
<p>My apologies but could you try removing the following folders as
well?</p>
<ul>
<li>/tomcat/server/webapps/host-manager/</li>
<li>/tomcat/server/webapps/manager/</li>
</ul>
<blockquote>
<p>I'm following up with this because I was under the impression
that this is related to why our instance of Cascade was down. Let
me know if I misunderstood something.</p>
</blockquote>
<p>I believe your CMS was down due to a row lock or DB timeout
issue, as I don't believe this is necessarily related but it could
pose a different problem.</p>
<p>Thanks!</p></div>Joeltag:help-archives.hannonhill.com,2010-02-09:Comment/90630922011-08-09T15:01:57Z2011-08-09T15:01:57ZProduction CMS Down<div><blockquote>
<p>could you try removing the following folders as well?</p>
</blockquote>
<p>Sure. I just removed and restarted on my test instance. It
started back up OK. I've removed from prod, which is scheduled to
restart overnight.</p>
<blockquote>
<p>I believe your CMS was down due to a row lock or DB timeout
issue, as I don't believe this is necessarily related</p>
</blockquote>
<p>Oh, I didn't realize we moved on to something else. Given that I
opened this ticket about Cascade crashing, can this also be
addressed? Do I need to configure something differently? Does it
need more CPU or RAM? Or it an intermittent bug in 6.8.3.1?</p>
<p>Thanks,<br>
Ian</p></div>irifkintag:help-archives.hannonhill.com,2010-02-09:Comment/90630922011-08-09T15:38:39Z2011-08-09T15:38:39ZProduction CMS Down<div><p>Hi Ian,</p>
<p>The issues Joel had you correct were related to the first two
errors I mentioned <a href=
"http://help.hannonhill.com/discussions/installation/163-production-cms-down#comment_9063647">
here</a>.</p>
<p>Originally I had mentioned that those could have been
contributing to some of the other issues you were seeing. However,
after speaking with my developers and seeing that your system has
been running fine (even with these continued errors that are
unrelated to the application itself), it is becoming more likely
that this was just a temporary problem with the database
itself.</p>
<p>There aren't any other errors in your log files that would cause
the database driver to return the messages I mentioned <a href=
"http://help.hannonhill.com/discussions/installation/163-production-cms-down#comment_9065950">
here</a>. Can you tell me which version of MySQL is installed on
your production database server?</p>
<p>Thanks!</p></div>Timtag:help-archives.hannonhill.com,2010-02-09:Comment/90630922011-08-09T16:12:26Z2011-08-09T16:12:26ZProduction CMS Down<div><blockquote>
<p>more likely that this was just a temporary problem with the
database itself.</p>
</blockquote>
<p>Oh, okay. So, no change recommended for prevention?</p>
<blockquote>
<p>Can you tell me which version of MySQL is installed on your
production database server?</p>
</blockquote>
<p>5.1.57</p>
<p>Thanks,<br>
Ian</p></div>irifkintag:help-archives.hannonhill.com,2010-02-09:Comment/90630922011-08-09T16:28:58Z2011-08-09T16:28:58ZProduction CMS Down<div><blockquote>
<p>Oh, okay. So, no change recommended for prevention?</p>
</blockquote>
<p>We can try! One thing you can do is increase the number of
connections for Cascade Server. To do so, edit your
<em>\tomcat\conf\context.xml</em> file and change the
<strong>maxActive</strong> value. At this point, try increasing it
by 10 or 15 and then make sure that your database is configured to
allow that number of connections.</p>
<blockquote>
<p>5.1.57</p>
</blockquote>
<p>Gotcha. Ok, it looks like that one error message can be traced
back to <a href="http://bugs.mysql.com/bug.php?id=38747">this MySQL
bug</a>. On that post, it looks like they fixed it for 5.1.7. It's
a minor MySQL update, but unless you consistently see this message
in your log files, I don't know whether it's really worth upgrading
or not.</p>
<p>Let me know if you have any questions about changing the maximum
connections.</p>
<p>Thanks!</p></div>Timtag:help-archives.hannonhill.com,2010-02-09:Comment/90630922011-08-09T17:09:18Z2011-08-09T17:09:18ZProduction CMS Down<div><blockquote>
<p>increase the number of connections for Cascade</p>
</blockquote>
<p>Okay, I've made the change from 50 to 65. The change has been
released to both our test and production instances. I've restarted
test, so if there's anything you want to me to check out there let
me know. Our prod instance is scheduled to restart overnight.</p>
<blockquote>
<p>make sure that your database is configured to allow that number
of connections.</p>
</blockquote>
<p>From our MySQL's my.cnf:<br>
max_connections=300</p>
<blockquote>
<p>it looks like they fixed it for 5.1.7 5.1.57 > 5.1.7. We are
pretty up-to-date in the 5.1.x series: <a href=
"http://dev.mysql.com/doc/refman/5.1/en/news-5-1-x.html">http://dev.mysql.com/doc/refman/5.1/en/news-5-1-x.html</a></p>
</blockquote>
<p>Thanks,<br>
Ian</p></div>irifkintag:help-archives.hannonhill.com,2010-02-09:Comment/90630922011-08-09T18:26:32Z2011-08-09T18:26:32ZProduction CMS Down<div><p>Ha, I read that totally wrong (your MySQL version). My fault!
Since it looks like you're using a recent version, I'm not sure why
that message still occurred that day. If you do happen to see that
one again, please let me know and we'll see if we can dig a little
deeper into investigating that particular error.</p></div>Timtag:help-archives.hannonhill.com,2010-02-09:Comment/90630922011-08-10T14:31:20Z2011-08-10T14:31:20ZProduction CMS Down<div><p>Hi,</p>
<p>Yesterday I made the changes to delete those two directories as
well as increase the maxActive connections in context.xml.</p>
<p>I'm not sure what I should be looking for. I still see the
"severe" errors in today's catalina.out:</p>
<p>grep -i severe catalina.out | sort | uniq -c<br>
1 SEVERE: Context [/.<em>ROOT] startup failed due to previous
errors<br>
3254 SEVERE: Error deploying configuration descriptor
.</em>host-manager.xml<br>
3254 SEVERE: Error deploying configuration descriptor
._manager.xml<br>
1 SEVERE: Error getConfigured<br>
1 SEVERE: Error in resourceStart()<br>
1 SEVERE: Error starting static Resources<br>
1 SEVERE: Exception fixing docBase: {0}<br>
6508 SEVERE: Parse Fatal Error at line 1 column 1: Content is not
allowed in prolog.</p>
<p>Thoughts?</p>
<p>Ian</p></div>irifkintag:help-archives.hannonhill.com,2010-02-09:Comment/90630922011-08-10T14:37:05Z2011-08-10T14:37:05ZProduction CMS Down<div><p>Ian,</p>
<p>If this is a Linux OS please be sure to list all files with "ls
-aF", as the "._" and "." prepended filenames are typically hidden
from the regular "ls" command. Try grepping or searching for these
files and if you find any, please let me know their exact
locations.</p>
<p>Thanks!</p></div>Joeltag:help-archives.hannonhill.com,2010-02-09:Comment/90630922011-08-10T14:52:30Z2011-08-10T14:52:30ZProduction CMS Down<div><p>Hi Joel,</p>
<p>Yes, this is a Linux OS, but I'm sorry, I don't know what you're
asking. I know how ls works -- you want a list of what
directory?</p>
<p>You want to know where the .<em>host-manager.xml and
.</em>manager.xml files are?</p>
<p>You had me delete ./tomcat/server/webapps/host-manager/ and
./tomcat/server/webapps/manager/ so what remains is:</p>
<p>./tomcat/conf/Catalina/localhost/.<em>host-manager.xml and<br>
./tomcat/conf/Catalina/localhost/.</em>manager.xml</p>
<p>I believe I also sent you those in the tomcat.zip on the
4th.</p>
<p>Let me know what you suggest or if you need more info (or if I
misunderstood!).</p>
<p>Ian</p></div>irifkintag:help-archives.hannonhill.com,2010-02-09:Comment/90630922011-08-10T15:15:32Z2011-08-10T15:15:32ZProduction CMS Down<div><p>Ian,</p>
<p>Apologies for the confusion, but could you try deleting the
<em>/tomcat/conf/Catalina</em> directory (just the Catalina
directory) and try restarting Cascade when you have a moment?
Previously I had been trying to find the location of these files
when the directory name was right in front of me.</p>
<p>Thanks!</p></div>Joeltag:help-archives.hannonhill.com,2010-02-09:Comment/90630922011-08-10T15:24:47Z2011-08-10T15:24:47ZProduction CMS Down<div><p>Not a problem.</p>
<p>I've deleted that Catalina directory in both test and prod. I've
restarted our test instance so if there's anything you want me to
try out there let me know.</p>
<p>Our production instance currently has 33 users working in it, so
I'd prefer to not interrupt them unless it's necessary. Otherwise,
it will be restarted overnight.</p>
<p>Thanks,<br>
Ian</p></div>irifkin