On Thu, Nov 03, 2022 at 03:47:16PM -0700, Kerry Bouchard wrote:
> I edited the tomcat logging.properties file to change the log fevels from
> INFO to FINE, and now when I restart tomcat, the first severe error in the
> catalina.2022-11-03.log file is:
>
> INFO: Deploying configuration descriptor
> /etc/tomcat/Catalina/localhost/ROOT.xml
> Nov 03, 2022 5:31:14 PM org.apache.tomcat.util.digester.Digester fatalError
> SEVERE: Parse Fatal Error at line 1 column 2: The markup declarations
> contained or pointed to by the document type declaration must be
> well-formed.
> org.xml.sax.SAXParseException; systemId:
>
http://www.eclipse.org/jetty/configure.dtd; lineNumber: 1; columnNumber: 2;
> The markup declarations contained or pointed to by the document type
> declaration must be well-formed.
> at
> com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:204)
> [followed by long stack trace]
>
> The /etc/tomcat/Catalina/localhost/ROOT.xml file has not been edited since
> 2015. For what it's worth, the contents are:
>
> <?xml version="1.0" ?>
> <!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN"
This refers to the DTD for configuration of Jetty, not Tomcat. That
may be confusing the parser. I don't know why it should suddenly
become a problem. Perhaps you upgraded Tomcat recently and the new
version is more strict?
I would remove everything starting at the DOCTYPE element down to but
not including the "<Context" line.
> > - Output of the "service tomcat status" shows:
> > - The dspace.log and cocoon.log files show no activity since since the
> > first stop and restart of tomcat.
> > - The /var/log/tomcat/catalina.2022-11-03.log file shows this:
> > - The files in /etc/tomcat/Catalina/localhost haven't been modified
> > since 2015.
> > - The files in /opt/projects/dspace/webapps/xmlui/static/ have owner
> > and group "tomcat" and the files in /etc/tomcat/Catalina/localhost have
> > owner and group "dspace".
> > - As far as I know, this part of the configuration hasn't changed for
> > years.
> > - Oracle and Oracle listener are up and running, but not showing any
> > connections from DSpace.
> > - I've rebooted the server, but the problem persists.
> >
> > Our DSpace 5.4 instance is dead in the water, but the only think I changed
> > before stopping and restarting tomcat was the robots.txt file (which is now
> > back to the original).
> >
> > Any help will be appriciated.
> >
> > Thanks, Kerry
> >
> >
> >
>
> --
> All messages to this mailing list should adhere to the Code of Conduct:
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
> ---
> You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to
dspace-tech...@googlegroups.com.
> To view this discussion on the web visit
https://groups.google.com/d/msgid/dspace-tech/a91aa2fa-2bd2-4f1d-9ddf-f491b99ee07bn%40googlegroups.com.
--
Mark H. Wood
Lead Technology Analyst
University Library
Indiana University - Purdue University Indianapolis
755 W. Michigan Street
Indianapolis, IN 46202
317-274-0749
www.ulib.iupui.edu