Hi Tim, I was able to fix the access issue to the database by making the selinux permissions of the whole dspace install area to a tomcat user. Not sure if this is the most efficient and secure solution.
Thanks for your help. Keith On Thu, Mar 21, 2019 at 3:28 PM Tim Donohue <[email protected]> wrote: > Hi Keith, > > The general errors are listed in the log snippet you provided. Take a look > at these SEVERE logs, which essentially say that Tomcat cannot run "/xmlui": > > SEVERE: One or more listeners failed to start. Full details will be found > in the appropriate container log file > Mar 21, 2019 2:10:35 PM org.apache.catalina.core.StandardContext > startInternal > SEVERE: Context [/xmlui] startup failed due to previous errors > Mar 21, 2019 2:10:35 PM org.apache.catalina.loader.WebappClassLoaderBase > clearReferencesJdbc > SEVERE: The web application [/xmlui] registered the JDBC driver > [org.postgresql.Driver] but failed to unregister it when the web > application was stopped. To prevent a memory leak, the JDBC Driver has been > forcibly unregistered. > Mar 21, 2019 2:10:35 PM org.apache.catalina.loader.WebappClassLoaderBase > clearReferencesJdbc > SEVERE: The web application [/xmlui] registered the JDBC driver > [org.postgresql.Driver] but failed to unregister it when the web > application was stopped. To prevent a memory leak, the JDBC Driver has been > forcibly unregistered. > > The first one in that list says "Full details will be found in the > appropriate container log file". That essentially means there's a > different Tomcat log which should have the full error details. My guess is > you might be looking at "catalina.out", but the error might be detailed > fully in a "localhost.[date].log" or a separate "catalina.[date].log". I'd > recommend looking at any other logs that are in your Tomcat for more > specific errors when you see that message. > > - Tim > > On Thu, Mar 21, 2019 at 1:29 PM Keith Jones <[email protected]> wrote: > >> Hi Tim, >> >> I've gone into Tomcat's log file and it doesn't give me enough >> information to help me figure out why it will not load the xmlui folder. >> I copied the xmlui folder into the webapps directory in Tomcat. >> >> Here is the log file: >> >> Mar 21, 2019 2:10:22 PM org.apache.coyote.AbstractProtocol pause >> INFO: Pausing ProtocolHandler ["http-bio-8090"] >> Mar 21, 2019 2:10:22 PM org.apache.coyote.AbstractProtocol pause >> INFO: Pausing ProtocolHandler ["ajp-bio-8009"] >> Mar 21, 2019 2:10:22 PM org.apache.catalina.core.StandardService >> stopInternal >> INFO: Stopping service Catalina >> Mar 21, 2019 2:10:22 PM org.apache.coyote.AbstractProtocol stop >> INFO: Stopping ProtocolHandler ["http-bio-8090"] >> Mar 21, 2019 2:10:22 PM org.apache.coyote.AbstractProtocol stop >> INFO: Stopping ProtocolHandler ["ajp-bio-8009"] >> Mar 21, 2019 2:10:22 PM org.apache.coyote.AbstractProtocol destroy >> INFO: Destroying ProtocolHandler ["http-bio-8090"] >> Mar 21, 2019 2:10:22 PM org.apache.coyote.AbstractProtocol destroy >> INFO: Destroying ProtocolHandler ["ajp-bio-8009"] >> Mar 21, 2019 2:10:27 PM org.apache.catalina.startup.VersionLoggerListener >> log >> INFO: Server version: Apache Tomcat/7.0.76 >> Mar 21, 2019 2:10:27 PM org.apache.catalina.startup.VersionLoggerListener >> log >> INFO: Server built: Oct 16 2018 09:15:49 UTC >> Mar 21, 2019 2:10:27 PM org.apache.catalina.startup.VersionLoggerListener >> log >> INFO: Server number: 7.0.76.0 >> Mar 21, 2019 2:10:27 PM org.apache.catalina.startup.VersionLoggerListener >> log >> INFO: OS Name: Linux >> Mar 21, 2019 2:10:27 PM org.apache.catalina.startup.VersionLoggerListener >> log >> INFO: OS Version: 3.10.0-862.14.4.el7.x86_64 >> Mar 21, 2019 2:10:27 PM org.apache.catalina.startup.VersionLoggerListener >> log >> INFO: Architecture: amd64 >> Mar 21, 2019 2:10:27 PM org.apache.catalina.startup.VersionLoggerListener >> log >> INFO: Java Home: >> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.201.b09-2.el7_6.x86_64/jre >> Mar 21, 2019 2:10:27 PM org.apache.catalina.startup.VersionLoggerListener >> log >> INFO: JVM Version: 1.8.0_201-b09 >> Mar 21, 2019 2:10:27 PM org.apache.catalina.startup.VersionLoggerListener >> log >> INFO: JVM Vendor: Oracle Corporation >> Mar 21, 2019 2:10:27 PM org.apache.catalina.startup.VersionLoggerListener >> log >> INFO: CATALINA_BASE: /usr/share/tomcat >> Mar 21, 2019 2:10:27 PM org.apache.catalina.startup.VersionLoggerListener >> log >> INFO: CATALINA_HOME: /usr/share/tomcat >> Mar 21, 2019 2:10:27 PM org.apache.catalina.startup.VersionLoggerListener >> log >> INFO: Command line argument: -Dcatalina.base=/usr/share/tomcat >> Mar 21, 2019 2:10:27 PM org.apache.catalina.startup.VersionLoggerListener >> log >> INFO: Command line argument: -Dcatalina.home=/usr/share/tomcat >> Mar 21, 2019 2:10:27 PM org.apache.catalina.startup.VersionLoggerListener >> log >> INFO: Command line argument: -Djava.endorsed.dirs= >> Mar 21, 2019 2:10:27 PM org.apache.catalina.startup.VersionLoggerListener >> log >> INFO: Command line argument: -Djava.io.tmpdir=/var/cache/tomcat/temp >> Mar 21, 2019 2:10:27 PM org.apache.catalina.startup.VersionLoggerListener >> log >> INFO: Command line argument: >> -Djava.util.logging.config.file=/usr/share/tomcat/conf/logging.properties >> Mar 21, 2019 2:10:27 PM org.apache.catalina.startup.VersionLoggerListener >> log >> INFO: Command line argument: >> -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager >> Mar 21, 2019 2:10:27 PM org.apache.catalina.core.AprLifecycleListener >> lifecycleEvent >> INFO: The APR based Apache Tomcat Native library which allows optimal >> performance in production environments was not found on the >> java.library.path: >> /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib >> Mar 21, 2019 2:10:27 PM org.apache.coyote.AbstractProtocol init >> INFO: Initializing ProtocolHandler ["http-bio-8090"] >> Mar 21, 2019 2:10:27 PM org.apache.coyote.AbstractProtocol init >> INFO: Initializing ProtocolHandler ["ajp-bio-8009"] >> Mar 21, 2019 2:10:27 PM org.apache.catalina.startup.Catalina load >> INFO: Initialization processed in 970 ms >> Mar 21, 2019 2:10:27 PM org.apache.catalina.core.StandardService >> startInternal >> INFO: Starting service Catalina >> Mar 21, 2019 2:10:27 PM org.apache.catalina.core.StandardEngine >> startInternal >> INFO: Starting Servlet Engine: Apache Tomcat/7.0.76 >> Mar 21, 2019 2:10:27 PM org.apache.catalina.startup.HostConfig >> deployDirectory >> INFO: Deploying web application directory /var/lib/tomcat/webapps/ROOT >> Mar 21, 2019 2:10:27 PM org.apache.catalina.startup.TldConfig execute >> INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable >> debug logging for this logger for a complete list of JARs that were scanned >> but no TLDs were found in them. Skipping unneeded JARs during scanning can >> improve startup time and JSP compilation time. >> Mar 21, 2019 2:10:27 PM org.apache.catalina.startup.HostConfig >> deployDirectory >> INFO: Deployment of web application directory >> /var/lib/tomcat/webapps/ROOT has finished in 616 ms >> Mar 21, 2019 2:10:27 PM org.apache.catalina.startup.HostConfig >> deployDirectory >> INFO: Deploying web application directory /var/lib/tomcat/webapps/xmlui >> Mar 21, 2019 2:10:28 PM org.apache.catalina.loader.WebappClassLoaderBase >> validateJarFile >> INFO: >> validateJarFile(/usr/share/tomcat/webapps/xmlui/WEB-INF/lib/servlet-api-2.5-20081211.jar) >> - jar not loaded. See Servlet Spec 3.0, section 10.7.2. Offending class: >> javax/servlet/Servlet.class >> Mar 21, 2019 2:10:33 PM org.apache.catalina.startup.TldConfig execute >> INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable >> debug logging for this logger for a complete list of JARs that were scanned >> but no TLDs were found in them. Skipping unneeded JARs during scanning can >> improve startup time and JSP compilation time. >> Mar 21, 2019 2:10:35 PM org.apache.catalina.core.StandardContext >> startInternal >> SEVERE: One or more listeners failed to start. Full details will be found >> in the appropriate container log file >> Mar 21, 2019 2:10:35 PM org.apache.catalina.core.StandardContext >> startInternal >> SEVERE: Context [/xmlui] startup failed due to previous errors >> Mar 21, 2019 2:10:35 PM org.apache.catalina.loader.WebappClassLoaderBase >> clearReferencesJdbc >> SEVERE: The web application [/xmlui] registered the JDBC driver >> [org.postgresql.Driver] but failed to unregister it when the web >> application was stopped. To prevent a memory leak, the JDBC Driver has been >> forcibly unregistered. >> Mar 21, 2019 2:10:35 PM org.apache.catalina.loader.WebappClassLoaderBase >> clearReferencesJdbc >> SEVERE: The web application [/xmlui] registered the JDBC driver >> [org.postgresql.Driver] but failed to unregister it when the web >> application was stopped. To prevent a memory leak, the JDBC Driver has been >> forcibly unregistered. >> Mar 21, 2019 2:10:35 PM org.apache.catalina.startup.HostConfig >> deployDirectory >> INFO: Deployment of web application directory >> /var/lib/tomcat/webapps/xmlui has finished in 7,592 ms >> Mar 21, 2019 2:10:35 PM org.apache.coyote.AbstractProtocol start >> INFO: Starting ProtocolHandler ["http-bio-8090"] >> Mar 21, 2019 2:10:35 PM org.apache.coyote.AbstractProtocol start >> INFO: Starting ProtocolHandler ["ajp-bio-8009"] >> Mar 21, 2019 2:10:35 PM org.apache.catalina.startup.Catalina start >> INFO: Server startup in 8260 ms >> >> Any help is appreciated. >> >> Thanks >> Keith >> >> On Thu, Mar 21, 2019 at 10:05 AM Tim Donohue <[email protected]> >> wrote: >> >>> You may also want to check your Tomcat logs to see if any errors are >>> being reported there. You noted checking the DSpace logs, but it's unclear >>> if you've also looked closely at the Tomcat logs. It's possible the Tomcat >>> logs will tell you exactly why Tomcat is failing to load the DSpace webapp. >>> >>> - Tim >>> >>> On Wed, Mar 20, 2019 at 2:44 PM <[email protected]> wrote: >>> >>>> Hi Terry, >>>> >>>> I tried your suggestions but catalina.out is reporting that the >>>> doucument base does not exist or is not a readable directory. I change the >>>> directory to be owned by tomcat but still the same error. >>>> Im not seeing any information in the dspace log area becauise the >>>> dspace app never loads in tomcat. >>>> When I mvn -U package, I'm see only success, here is the report: >>>> >>>> [INFO] Reactor Summary: >>>> [INFO] >>>> [INFO] DSpace Parent Project ............................. SUCCESS >>>> [9.285s] >>>> [INFO] DSpace Services Framework :: API and Implementation SUCCESS >>>> [3.793s] >>>> [INFO] DSpace Kernel :: API and Implementation ........... SUCCESS >>>> [10.179s] >>>> [INFO] DSpace Addon Modules .............................. SUCCESS >>>> [0.083s] >>>> [INFO] DSpace Kernel :: Additions and Local Customizations SUCCESS >>>> [1.354s] >>>> [INFO] DSpace XML-UI (Manakin) ........................... SUCCESS >>>> [4.095s] >>>> [INFO] DSpace XML-UI (Manakin) :: Local Customizations ... SUCCESS >>>> [7.638s] >>>> [INFO] DSpace JSP-UI ..................................... SUCCESS >>>> [1.952s] >>>> [INFO] DSpace JSP-UI :: Local Customizations ............. SUCCESS >>>> [6.120s] >>>> [INFO] DSpace RDF ........................................ SUCCESS >>>> [5.343s] >>>> [INFO] DSpace RDF :: Local Customizations ................ SUCCESS >>>> [9.175s] >>>> [INFO] DSpace REST :: API and Implementation ............. SUCCESS >>>> [5.702s] >>>> [INFO] DSpace REST :: Local Customizations ............... SUCCESS >>>> [8.817s] >>>> [INFO] DSpace SWORD ...................................... SUCCESS >>>> [0.865s] >>>> [INFO] DSpace SWORD :: Local Customizations .............. SUCCESS >>>> [4.787s] >>>> [INFO] DSpace SWORD v2 ................................... SUCCESS >>>> [0.764s] >>>> [INFO] DSpace SWORD v2 :: Local Customizations ........... SUCCESS >>>> [4.937s] >>>> [INFO] Apache Solr Webapp ................................ SUCCESS >>>> [8.977s] >>>> [INFO] DSpace SOLR :: Local Customizations ............... SUCCESS >>>> [5.082s] >>>> [INFO] DSpace OAI-PMH .................................... SUCCESS >>>> [0.458s] >>>> [INFO] DSpace OAI-PMH :: Local Customizations ............ SUCCESS >>>> [6.059s] >>>> [INFO] DSpace Assembly and Configuration ................. SUCCESS >>>> [21.954s] >>>> [INFO] DSpace XML-UI Mirage2 Theme ....................... SUCCESS >>>> [0.187s] >>>> [INFO] >>>> ------------------------------------------------------------------------ >>>> [INFO] BUILD SUCCESS >>>> [INFO] >>>> ------------------------------------------------------------------------ >>>> [INFO] Total time: 2:08.781s >>>> [INFO] Finished at: Wed Mar 20 15:39:33 EDT 2019 >>>> [INFO] Final Memory: 88M/783M >>>> >>>> >>>> Then I've run the ant fresh_install command in the following location >>>> dspace/target/dspace-installer >>>> >>>> copy_webapps: >>>> [copy] Copying 2683 files to /home/dspace/webapps >>>> [copy] Copying 10 files to /home/dspace/webapps >>>> >>>> build_webapps_wars: >>>> >>>> check_geolite: >>>> >>>> init_geolite: >>>> >>>> update_geolite: >>>> [echo] Downloading: >>>> http://geolite.maxmind.com/download/geoip/database/GeoLiteCity.dat.gz >>>> [get] Getting: >>>> http://geolite.maxmind.com/download/geoip/database/GeoLiteCity.dat.gz >>>> [get] To: /home/dspace/config/GeoLiteCity.dat.gz >>>> [get] Error opening connection java.io.FileNotFoundException: >>>> http://geolite.maxmind.com/download/geoip/database/GeoLiteCity.dat.gz >>>> [get] Error opening connection java.io.FileNotFoundException: >>>> http://geolite.maxmind.com/download/geoip/database/GeoLiteCity.dat.gz >>>> [get] Error opening connection java.io.FileNotFoundException: >>>> http://geolite.maxmind.com/download/geoip/database/GeoLiteCity.dat.gz >>>> [get] Can't get >>>> http://geolite.maxmind.com/download/geoip/database/GeoLiteCity.dat.gz >>>> to /home/dspace/config/GeoLiteCity.dat.gz >>>> [echo] >>>> [echo] >>>> ==================================================================== >>>> [echo] WARNING : FAILED TO DOWNLOAD GEOLITE DATABASE FILE >>>> [echo] (Used for DSpace Solr Usage Statistics) >>>> [echo] >>>> [echo] Underlying Error: Can't get >>>> http://geolite.maxmind.com/download/geoip/database/GeoLiteCity.dat.gz >>>> to /home/dspace/config/GeoLiteCity.dat.gz >>>> [echo] >>>> [echo] In order to use DSpace Solr Usage Statistics, you will need >>>> to >>>> [echo] manually re-run: >>>> [echo] >>>> [echo] ant update_geolite >>>> [echo] >>>> [echo] OR >>>> [echo] >>>> [echo] You may manually install this file by following these steps: >>>> [echo] (1) Download the file from >>>> http://geolite.maxmind.com/download/geoip/database/GeoLiteCity.dat.gz >>>> [echo] (2) Unzip it to create a file named 'GeoLiteCity.dat' >>>> [echo] (3) Copy that file to '/home/dspace/config/GeoLiteCity.dat' >>>> [echo] >>>> [echo] >>>> ==================================================================== >>>> [echo] >>>> [echo] >>>> [echo] >>>> ==================================================================== >>>> [echo] The DSpace code has been installed. >>>> [echo] >>>> [echo] To complete installation, you should do the following: >>>> [echo] >>>> [echo] * Setup your Web servlet container (e.g. Tomcat) to look >>>> for your >>>> [echo] DSpace web applications in: /home/dspace/webapps/ >>>> [echo] >>>> [echo] OR, copy any web applications from /home/dspace/webapps/ >>>> to >>>> [echo] the appropriate place for your servlet container. >>>> [echo] (e.g. '$CATALINA_HOME/webapps' for Tomcat) >>>> [echo] >>>> [echo] * Start up your servlet container (e.g. Tomcat). DSpace >>>> now will >>>> [echo] initialize the database on the first startup. >>>> [echo] >>>> [echo] * Make an initial administrator account (an e-person) in >>>> DSpace: >>>> [echo] >>>> [echo] /home/dspace/bin/dspace create-administrator >>>> [echo] >>>> [echo] You should then be able to access your DSpace's 'home >>>> page': >>>> [echo] >>>> [echo] http://xxx.xxx.xxx.xxx:8090 >>>> [echo] >>>> [echo] >>>> ==================================================================== >>>> [echo] >>>> >>>> BUILD SUCCESSFUL >>>> Total time: 8 seconds >>>> >>>> >>>> I'm at a loss as to why apps will not load in tomcat. >>>> >>>> Thanks for any help. >>>> >>>> >>>> On Monday, March 18, 2019 at 2:45:07 PM UTC-4, Terry Brady wrote: >>>>> >>>>> For our installation, we create the following symlinks >>>>> >>>>> - /opt/tomcat8/webapps/xmlui -> dspace-install/webapps/xmlui >>>>> - /opt/tomcat8/webapps/ROOT -> xmlui >>>>> >>>>> If you cannot find an error in one of the dspace logs, did you also >>>>> check the catalina log file for tomcat? >>>>> >>>>> On Fri, Mar 15, 2019 at 1:26 PM <[email protected]> wrote: >>>>> >>>>>> Hi All, >>>>>> >>>>>> I'm installing Dspace version 5.9 in a centos 7 machine from source >>>>>> code. After running both mvn -U package and then doing an ant >>>>>> fresh_install, I move the xmlui folder to be the ROOT folder of tomcat >>>>>> but >>>>>> Dspace will not load. I'm not getting any errors when compiling, and no >>>>>> errors are showing up in the log files. Does anyone have an idea where I >>>>>> should look to troubleshoot? >>>>>> >>>>>> Thanks >>>>>> >>>>>> -- >>>>>> All messages to this mailing list should adhere to the DuraSpace Code >>>>>> of Conduct: https://duraspace.org/about/policies/code-of-conduct/ >>>>>> --- >>>>>> 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 [email protected]. >>>>>> To post to this group, send email to [email protected]. >>>>>> Visit this group at https://groups.google.com/group/dspace-tech. >>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>> >>>>> >>>>> >>>>> -- >>>>> Terry Brady >>>>> Applications Programmer Analyst >>>>> Georgetown University Library Information Technology >>>>> https://github.com/terrywbrady/info >>>>> 425-298-5498 (Seattle, WA) >>>>> >>>> -- >>>> All messages to this mailing list should adhere to the DuraSpace Code >>>> of Conduct: https://duraspace.org/about/policies/code-of-conduct/ >>>> --- >>>> 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 [email protected]. >>>> To post to this group, send email to [email protected]. >>>> Visit this group at https://groups.google.com/group/dspace-tech. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> >>> -- >>> >>> Tim Donohue >>> Technical Lead for DSpace & DSpaceDirect >>> DuraSpace.org | DSpace.org | DSpaceDirect.org >>> >>> > > -- > > Tim Donohue > Technical Lead for DSpace & DSpaceDirect > DuraSpace.org | DSpace.org | DSpaceDirect.org > > -- All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/ --- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
