subject:"\[dspace\-tech\] 6.0 upgrade"

Re: [dspace-tech] 6.0 upgrade

2016-12-15 Thread Hardy Pottinger

I think it might be time to step back and just try to get Tomcat to start
at all, without DSpace deployed. Try to start it with the stock context and
no webaps. If that works, try deploying Psi Probe [1]

--Hardy

[1] https://github.com/psi-probe/psi-probe/wiki/InstallationApacheTomcat


On Dec 14, 2016 11:05 AM, "Larry Hansard" 
wrote:

> It only has 2 lines:
>
> [dspace@digrepository logs]$ more localhost.2016-12-14.log
> 14-Dec-2016 10:23:37.049 INFO [localhost-startStop-1]
> org.apache.catalina.core.ApplicationContext.log No Spring
> WebApplicationInitializer types detected on classpath
> 14-Dec-2016 10:23:42.988 INFO [localhost-startStop-1]
> org.apache.catalina.core.ApplicationContext.log Initializing Spring root
> WebApplicationContext
>
> On Wednesday, December 14, 2016 at 10:53:34 AM UTC-6, Mark Wood wrote:
>>
>> I've seen cases where the relevant information was in another Tomcat
>> log.  Here, I also get logs named localhost-$DATE.log.  (Not the same as
>> localhost_access-$DATE.log)  I would look around in Tomcat's log directory
>> to see if there is anything else covering the same time span, and what
>> might be found in it.
>>
> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to dspace-tech@googlegroups.com.
> Visit this group at https://groups.google.com/group/dspace-tech.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] 6.0 upgrade

2016-12-14 Thread Larry Hansard

It only has 2 lines:

[dspace@digrepository logs]$ more localhost.2016-12-14.log
14-Dec-2016 10:23:37.049 INFO [localhost-startStop-1] 
org.apache.catalina.core.ApplicationContext.log No Spring 
WebApplicationInitializer types detected on classpath
14-Dec-2016 10:23:42.988 INFO [localhost-startStop-1] 
org.apache.catalina.core.ApplicationContext.log Initializing Spring root 
WebApplicationContext

On Wednesday, December 14, 2016 at 10:53:34 AM UTC-6, Mark Wood wrote:
>
> I've seen cases where the relevant information was in another Tomcat log.  
> Here, I also get logs named localhost-$DATE.log.  (Not the same as 
> localhost_access-$DATE.log)  I would look around in Tomcat's log directory 
> to see if there is anything else covering the same time span, and what 
> might be found in it.
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] 6.0 upgrade

2016-12-14 Thread Larry Hansard

Here is the dspace log file:

2016-12-14 10:23:40,876 INFO  org.dspace.storage.rdbms.DatabaseUtils @
Loading Flyway DB migrations from: filesystem:/dspace/etc/postgres,
classpath:org.dspace.storage.rdbms.sqlmigration.postgres,
classpath:org.dspace.storage.rdbms.migr
ation
2016-12-14 10:23:40,901 INFO
 org.flywaydb.core.internal.util.VersionPrinter @ Flyway 4.0.3 by Boxfuse
2016-12-14 10:23:40,913 INFO
 org.flywaydb.core.internal.dbsupport.DbSupportFactory @ Database:
jdbc:postgresql://localhost:5432/dspace (PostgreSQL 9.4)
2016-12-14 10:23:41,018 INFO  org.dspace.storage.rdbms.DatabaseUtils @
DSpace database schema is up to date
2016-12-14 10:23:41,041 INFO  org.dspace.event.EventServiceImpl @
EventService dispatcher pool initialized
2016-12-14 10:23:41,198 INFO  org.hibernate.annotations.common.Version @
HCANN01: Hibernate Commons Annotations {4.0.2.Final}
2016-12-14 10:23:41,204 INFO  org.hibernate.Version @ HHH000412: Hibernate
Core {4.2.21.Final}
2016-12-14 10:23:41,207 INFO  org.hibernate.cfg.Environment @ HHH000206:
hibernate.properties not found
2016-12-14 10:23:41,208 INFO  org.hibernate.cfg.Environment @ HHH21:
Bytecode provider name : javassist
2016-12-14 10:23:41,234 INFO  org.hibernate.cfg.Configuration @ HHH44:
Configuring from URL: file:/dspace/config/hibernate.cfg.xml
2016-12-14 10:23:41,571 INFO  org.hibernate.cfg.Configuration @ HHH41:
Configured SessionFactory: null
2016-12-14 10:23:41,751 INFO  org.hibernate.dialect.Dialect @ HHH000400:
Using dialect:
org.dspace.storage.rdbms.hibernate.postgres.DSpacePostgreSQL82Dialect
2016-12-14 10:23:41,764 INFO
 org.hibernate.engine.jdbc.internal.LobCreatorBuilder @ HHH000424:
Disabling contextual LOB creation as createClob() method threw error :
java.lang.reflect.InvocationTargetException
2016-12-14 10:23:41,772 INFO  org.hibernate.type.BasicTypeRegistry @
HHH000270: Type registration [pg-uuid] overrides previous :
org.hibernate.type.PostgresUUIDType@29f853be
2016-12-14 10:23:41,772 INFO  org.hibernate.type.BasicTypeRegistry @
HHH000270: Type registration [java.util.UUID] overrides previous :
org.hibernate.type.UUIDBinaryType@297f5cd6
2016-12-14 10:23:42,006 WARN  org.hibernate.mapping.RootClass @ HHH39:
Composite-id class does not override hashCode():
org.dspace.eperson.Group2GroupCache
2016-12-14 10:23:42,007 WARN  org.hibernate.mapping.RootClass @ HHH38:
Composite-id class does not override equals():
org.dspace.checker.MostRecentChecksum
2016-12-14 10:23:42,007 WARN  org.hibernate.mapping.RootClass @ HHH39:
Composite-id class does not override hashCode():
org.dspace.checker.MostRecentChecksum
2016-12-14 10:23:42,013 INFO
 org.hibernate.engine.transaction.internal.TransactionFactoryInitiator @
HHH000399: Using default transaction strategy (direct JDBC transactions)
2016-12-14 10:23:42,018 INFO
 org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory @ HHH000397:
Using ASTQueryTranslatorFactory
2016-12-14 10:23:42,162 WARN  net.sf.ehcache.config.ConfigurationFactory @
No configuration found. Configuring ehcache from ehcache-failsafe.xml
 found in the classpath:
jar:file:/usr/local/apache-tomcat-8.5.9/webapps/jspui/WEB-INF/lib/
ehcache-core-2.4.3.jar!/ehcache-failsafe.xml
2016-12-14 10:23:42,171 WARN  net.sf.ehcache.CacheManager @ Creating a new
instance of CacheManager using the diskStorePath
"/usr/local/apache-tomcat-8.5.9/temp" which is already used by an existing
CacheManager.
The source of the configuration was
net.sf.ehcache.config.generator.ConfigurationSource$DefaultConfigurationSource@62434e34.
The diskStore path for this CacheManager will be set to
/usr/local/apache-tomcat-8.5.9/temp/ehcache_auto_created_1481732622171.
To avoid this warning consider using the CacheManager factory methods to
create a singleton CacheManager or specifying a separate ehcache
configuration (ehcache.xml) for each CacheManager instance.
2016-12-14 10:23:42,173 INFO  org.hibernate.cache.spi.UpdateTimestampsCache
@ HHH000250: Starting update timestamps cache at region:
org.hibernate.cache.spi.UpdateTimestampsCache
2016-12-14 10:23:42,176 WARN
 org.hibernate.cache.ehcache.AbstractEhcacheRegionFactory @ HHH020003:
Could not find a specific ehcache configuration for cache named
[org.hibernate.cache.spi.UpdateTimestampsCache]; using defaults.
2016-12-14 10:23:42,206 INFO
 org.hibernate.cache.internal.StandardQueryCache @ HHH000248: Starting
query cache at region: org.hibernate.cache.internal.StandardQueryCache
2016-12-14 10:23:42,206 WARN
 org.hibernate.cache.ehcache.AbstractEhcacheRegionFactory @ HHH020003:
Could not find a specific ehcache configuration for cache named
[org.hibernate.cache.internal.StandardQueryCache]; using defaults.
2016-12-14 10:23:42,225 WARN
 org.hibernate.cache.ehcache.AbstractEhcacheRegionFactory @ HHH020003:
Could not find a specific ehcache configuration for cache named
[org.dspace.content.MetadataSchema]; using defaults.
2016-12-14 10:23:42,428 WARN
 org.hibernate.cache.ehcache.AbstractEhcacheRegionFactory @

Re: [dspace-tech] 6.0 upgrade

2016-12-14 Thread Mark Wood

I've seen cases where the relevant information was in another Tomcat log.  
Here, I also get logs named localhost-$DATE.log.  (Not the same as 
localhost_access-$DATE.log)  I would look around in Tomcat's log directory 
to see if there is anything else covering the same time span, and what 
might be found in it.

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] 6.0 upgrade

2016-12-14 Thread Hardy Pottinger

OK. And the dspace log file at $DSPACE_INSTALL_DIR/log/dspace.log.TODAY?
Anything interesting in there?

On Wed, Dec 14, 2016 at 10:46 AM, Larry Hansard 
wrote:

> I started with 7 and it stopped at the same place in the catalina.out
> file.
>
>
> On Wednesday, December 14, 2016 at 10:40:27 AM UTC-6, Hardy Pottinger
> wrote:
>>
>> Hmm... I assume that after that last line of output Tomcat just hangs?
>> You might try Tomcat 7 instead of Tomcat 8, just to give you a comparison.
>> I do know people have successfully used Tomcat 8 with Dspace 6, but I
>> myself have not.
>>
>> --Hardy
>>
>> On Wed, Dec 14, 2016 at 10:26 AM, Larry Hansard 
>> wrote:
>>
>> It always stop at the same point:
>>
>> 14-Dec-2016 10:23:12.629 INFO [main] 
>> org.apache.catalina.startup.VersionLoggerListener.log
>> Server version:Apache Tomcat/8.5.9
>> 14-Dec-2016 10:23:12.633 INFO [main] 
>> org.apache.catalina.startup.VersionLoggerListener.log
>> Server built:  Dec 5 2016 20:18:12 UTC
>> 14-Dec-2016 10:23:12.633 INFO [main] 
>> org.apache.catalina.startup.VersionLoggerListener.log
>> Server number: 8.5.9.0
>> 14-Dec-2016 10:23:12.634 INFO [main] 
>> org.apache.catalina.startup.VersionLoggerListener.log
>> OS Name:   Linux
>> 14-Dec-2016 10:23:12.634 INFO [main] 
>> org.apache.catalina.startup.VersionLoggerListener.log
>> OS Version:2.6.32-642.11.1.el6.x86_64
>> 14-Dec-2016 10:23:12.634 INFO [main] 
>> org.apache.catalina.startup.VersionLoggerListener.log
>> Architecture:  amd64
>> 14-Dec-2016 10:23:12.634 INFO [main] 
>> org.apache.catalina.startup.VersionLoggerListener.log
>> Java Home: /usr/java/jdk1.8.0/jre
>> 14-Dec-2016 10:23:12.634 INFO [main] 
>> org.apache.catalina.startup.VersionLoggerListener.log
>> JVM Version:   1.8.0-b132
>> 14-Dec-2016 10:23:12.635 INFO [main] 
>> org.apache.catalina.startup.VersionLoggerListener.log
>> JVM Vendor:Oracle Corporation
>> 14-Dec-2016 10:23:12.635 INFO [main] 
>> org.apache.catalina.startup.VersionLoggerListener.log
>> CATALINA_BASE: /usr/local/apache-tomcat-8.5.9
>> 14-Dec-2016 10:23:12.635 INFO [main] 
>> org.apache.catalina.startup.VersionLoggerListener.log
>> CATALINA_HOME: /usr/local/apache-tomcat-8.5.9
>> 14-Dec-2016 10:23:12.636 INFO [main] 
>> org.apache.catalina.startup.VersionLoggerListener.log
>> Command line argument: -Djava.util.logging.config.fil
>> e=/usr/local/apache-tomcat-8.5.9/conf/logging.properties
>> 14-Dec-2016 10:23:12.636 INFO [main] 
>> org.apache.catalina.startup.VersionLoggerListener.log
>> Command line argument: -Djava.util.logging.manager=or
>> g.apache.juli.ClassLoaderLogManager
>> 14-Dec-2016 10:23:12.636 INFO [main] 
>> org.apache.catalina.startup.VersionLoggerListener.log
>> Command line argument: -Djdk.tls.ephemeralDHKeySize=2048
>> 14-Dec-2016 10:23:12.637 INFO [main] 
>> org.apache.catalina.startup.VersionLoggerListener.log
>> Command line argument: -Djava.protocol.handler.pkgs=o
>> rg.apache.catalina.webresources
>> 14-Dec-2016 10:23:12.637 INFO [main] 
>> org.apache.catalina.startup.VersionLoggerListener.log
>> Command line argument: -Dcatalina.base=/usr/local/apache-tomcat-8.5.9
>> 14-Dec-2016 10:23:12.638 INFO [main] 
>> org.apache.catalina.startup.VersionLoggerListener.log
>> Command line argument: -Dcatalina.home=/usr/local/apache-tomcat-8.5.9
>> 14-Dec-2016 10:23:12.638 INFO [main] 
>> org.apache.catalina.startup.VersionLoggerListener.log
>> Command line argument: -Djava.io.tmpdir=/usr/local/ap
>> ache-tomcat-8.5.9/temp
>> 14-Dec-2016 10:23:12.638 INFO [main] 
>> org.apache.catalina.core.AprLifecycleListener.lifecycleEvent
>> The APR based Apache Tomcat Native library which allows optimal performance
>> in production environments was not found on the java.library.p
>> ath: /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
>> 14-Dec-2016 10:23:13.053 INFO [main] org.apache.coyote.AbstractProtocol.init
>> Initializing ProtocolHandler ["http-nio-8080"]
>> 14-Dec-2016 10:23:13.106 INFO [main] 
>> org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector
>> Using a shared selector for servlet write/read
>> 14-Dec-2016 10:23:13.111 INFO [main] org.apache.coyote.AbstractProtocol.init
>> Initializing ProtocolHandler ["ajp-nio-8009"]
>> 14-Dec-2016 10:23:13.115 INFO [main] 
>> org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector
>> Using a shared selector for servlet write/read
>> 14-Dec-2016 10:23:13.115 INFO [main] 
>> org.apache.catalina.startup.Catalina.load
>> Initialization processed in 1450 ms
>> 14-Dec-2016 10:23:13.178 INFO [main] 
>> org.apache.catalina.core.StandardService.startInternal
>> Starting service Catalina
>> 14-Dec-2016 10:23:13.178 INFO [main] 
>> org.apache.catalina.core.StandardEngine.startInternal
>> Starting Servlet Engine: Apache Tomcat/8.5.9
>> 14-Dec-2016 10:23:13.212 INFO [localhost-startStop-1]
>> org.apache.catalina.startup.HostConfig.deployDirectory

Re: [dspace-tech] 6.0 upgrade

2016-12-14 Thread Larry Hansard

I started with 7 and it stopped at the same place in the catalina.out file. 
 


On Wednesday, December 14, 2016 at 10:40:27 AM UTC-6, Hardy Pottinger wrote:
>
> Hmm... I assume that after that last line of output Tomcat just hangs? You 
> might try Tomcat 7 instead of Tomcat 8, just to give you a comparison. I do 
> know people have successfully used Tomcat 8 with Dspace 6, but I myself 
> have not.
>
> --Hardy
>
> On Wed, Dec 14, 2016 at 10:26 AM, Larry Hansard  > wrote:
>
> It always stop at the same point:
>
> 14-Dec-2016 10:23:12.629 INFO [main] 
> org.apache.catalina.startup.VersionLoggerListener.log Server version:   
>  Apache Tomcat/8.5.9
> 14-Dec-2016 10:23:12.633 INFO [main] 
> org.apache.catalina.startup.VersionLoggerListener.log Server built: 
>  Dec 5 2016 20:18:12 UTC
> 14-Dec-2016 10:23:12.633 INFO [main] 
> org.apache.catalina.startup.VersionLoggerListener.log Server number:   
>   8.5.9.0
> 14-Dec-2016 10:23:12.634 INFO [main] 
> org.apache.catalina.startup.VersionLoggerListener.log OS Name: 
>   Linux
> 14-Dec-2016 10:23:12.634 INFO [main] 
> org.apache.catalina.startup.VersionLoggerListener.log OS Version:   
>  2.6.32-642.11.1.el6.x86_64
> 14-Dec-2016 10:23:12.634 INFO [main] 
> org.apache.catalina.startup.VersionLoggerListener.log Architecture: 
>  amd64
> 14-Dec-2016 10:23:12.634 INFO [main] 
> org.apache.catalina.startup.VersionLoggerListener.log Java Home:   
>   /usr/java/jdk1.8.0/jre
> 14-Dec-2016 10:23:12.634 INFO [main] 
> org.apache.catalina.startup.VersionLoggerListener.log JVM Version: 
>   1.8.0-b132
> 14-Dec-2016 10:23:12.635 INFO [main] 
> org.apache.catalina.startup.VersionLoggerListener.log JVM Vendor:   
>  Oracle Corporation
> 14-Dec-2016 10:23:12.635 INFO [main] 
> org.apache.catalina.startup.VersionLoggerListener.log CATALINA_BASE:   
>   /usr/local/apache-tomcat-8.5.9
> 14-Dec-2016 10:23:12.635 INFO [main] 
> org.apache.catalina.startup.VersionLoggerListener.log CATALINA_HOME:   
>   /usr/local/apache-tomcat-8.5.9
> 14-Dec-2016 10:23:12.636 INFO [main] 
> org.apache.catalina.startup.VersionLoggerListener.log Command line 
> argument: 
> -Djava.util.logging.config.file=/usr/local/apache-tomcat-8.5.9/conf/logging.properties
> 14-Dec-2016 10:23:12.636 INFO [main] 
> org.apache.catalina.startup.VersionLoggerListener.log Command line 
> argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
> 14-Dec-2016 10:23:12.636 INFO [main] 
> org.apache.catalina.startup.VersionLoggerListener.log Command line 
> argument: -Djdk.tls.ephemeralDHKeySize=2048
> 14-Dec-2016 10:23:12.637 INFO [main] 
> org.apache.catalina.startup.VersionLoggerListener.log Command line 
> argument: -Djava.protocol.handler.pkgs=org.apache.catalina.webresources
> 14-Dec-2016 10:23:12.637 INFO [main] 
> org.apache.catalina.startup.VersionLoggerListener.log Command line 
> argument: -Dcatalina.base=/usr/local/apache-tomcat-8.5.9
> 14-Dec-2016 10:23:12.638 INFO [main] 
> org.apache.catalina.startup.VersionLoggerListener.log Command line 
> argument: -Dcatalina.home=/usr/local/apache-tomcat-8.5.9
> 14-Dec-2016 10:23:12.638 INFO [main] 
> org.apache.catalina.startup.VersionLoggerListener.log Command line 
> argument: -Djava.io.tmpdir=/usr/local/apache-tomcat-8.5.9/temp
> 14-Dec-2016 10:23:12.638 INFO [main] 
> org.apache.catalina.core.AprLifecycleListener.lifecycleEvent The APR based 
> Apache Tomcat Native library which allows optimal performance in production 
> environments was not found on the java.library.p
> ath: /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
> 14-Dec-2016 10:23:13.053 INFO [main] 
> org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler 
> ["http-nio-8080"]
> 14-Dec-2016 10:23:13.106 INFO [main] 
> org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector 
> Using a shared selector for servlet write/read
> 14-Dec-2016 10:23:13.111 INFO [main] 
> org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler 
> ["ajp-nio-8009"]
> 14-Dec-2016 10:23:13.115 INFO [main] 
> org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector 
> Using a shared selector for servlet write/read
> 14-Dec-2016 10:23:13.115 INFO [main] 
> org.apache.catalina.startup.Catalina.load Initialization processed in 1450 
> ms
> 14-Dec-2016 10:23:13.178 INFO [main] 
> org.apache.catalina.core.StandardService.startInternal Starting service 
> Catalina
> 14-Dec-2016 10:23:13.178 INFO [main] 
> org.apache.catalina.core.StandardEngine.startInternal Starting Servlet 
> Engine: Apache Tomcat/8.5.9
> 14-Dec-2016 10:23:13.212 INFO [localhost-startStop-1] 
> org.apache.catalina.startup.HostConfig.deployDirectory Deploying web 
> application directory /usr/local/apache-tomcat-8.5.9/webapps/swordv2
> 14-Dec-2016 10:23:23.387 INFO [localhost-startStop-1] 
> org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned 
> for TLDs yet contained no TLDs. Enable

Re: [dspace-tech] 6.0 upgrade

2016-12-14 Thread Hardy Pottinger

Hmm... I assume that after that last line of output Tomcat just hangs? You
might try Tomcat 7 instead of Tomcat 8, just to give you a comparison. I do
know people have successfully used Tomcat 8 with Dspace 6, but I myself
have not.

--Hardy

On Wed, Dec 14, 2016 at 10:26 AM, Larry Hansard  wrote:

> It always stop at the same point:
>
> 14-Dec-2016 10:23:12.629 INFO [main] 
> org.apache.catalina.startup.VersionLoggerListener.log
> Server version:Apache Tomcat/8.5.9
> 14-Dec-2016 10:23:12.633 INFO [main] 
> org.apache.catalina.startup.VersionLoggerListener.log
> Server built:  Dec 5 2016 20:18:12 UTC
> 14-Dec-2016 10:23:12.633 INFO [main] 
> org.apache.catalina.startup.VersionLoggerListener.log
> Server number: 8.5.9.0
> 14-Dec-2016 10:23:12.634 INFO [main] 
> org.apache.catalina.startup.VersionLoggerListener.log
> OS Name:   Linux
> 14-Dec-2016 10:23:12.634 INFO [main] 
> org.apache.catalina.startup.VersionLoggerListener.log
> OS Version:2.6.32-642.11.1.el6.x86_64
> 14-Dec-2016 10:23:12.634 INFO [main] 
> org.apache.catalina.startup.VersionLoggerListener.log
> Architecture:  amd64
> 14-Dec-2016 10:23:12.634 INFO [main] 
> org.apache.catalina.startup.VersionLoggerListener.log
> Java Home: /usr/java/jdk1.8.0/jre
> 14-Dec-2016 10:23:12.634 INFO [main] 
> org.apache.catalina.startup.VersionLoggerListener.log
> JVM Version:   1.8.0-b132
> 14-Dec-2016 10:23:12.635 INFO [main] 
> org.apache.catalina.startup.VersionLoggerListener.log
> JVM Vendor:Oracle Corporation
> 14-Dec-2016 10:23:12.635 INFO [main] 
> org.apache.catalina.startup.VersionLoggerListener.log
> CATALINA_BASE: /usr/local/apache-tomcat-8.5.9
> 14-Dec-2016 10:23:12.635 INFO [main] 
> org.apache.catalina.startup.VersionLoggerListener.log
> CATALINA_HOME: /usr/local/apache-tomcat-8.5.9
> 14-Dec-2016 10:23:12.636 INFO [main] 
> org.apache.catalina.startup.VersionLoggerListener.log
> Command line argument: -Djava.util.logging.config.
> file=/usr/local/apache-tomcat-8.5.9/conf/logging.properties
> 14-Dec-2016 10:23:12.636 INFO [main] 
> org.apache.catalina.startup.VersionLoggerListener.log
> Command line argument: -Djava.util.logging.manager=org.apache.juli.
> ClassLoaderLogManager
> 14-Dec-2016 10:23:12.636 INFO [main] 
> org.apache.catalina.startup.VersionLoggerListener.log
> Command line argument: -Djdk.tls.ephemeralDHKeySize=2048
> 14-Dec-2016 10:23:12.637 INFO [main] 
> org.apache.catalina.startup.VersionLoggerListener.log
> Command line argument: -Djava.protocol.handler.pkgs=org.apache.catalina.
> webresources
> 14-Dec-2016 10:23:12.637 INFO [main] 
> org.apache.catalina.startup.VersionLoggerListener.log
> Command line argument: -Dcatalina.base=/usr/local/apache-tomcat-8.5.9
> 14-Dec-2016 10:23:12.638 INFO [main] 
> org.apache.catalina.startup.VersionLoggerListener.log
> Command line argument: -Dcatalina.home=/usr/local/apache-tomcat-8.5.9
> 14-Dec-2016 10:23:12.638 INFO [main] 
> org.apache.catalina.startup.VersionLoggerListener.log
> Command line argument: -Djava.io.tmpdir=/usr/local/
> apache-tomcat-8.5.9/temp
> 14-Dec-2016 10:23:12.638 INFO [main] org.apache.catalina.core.
> AprLifecycleListener.lifecycleEvent The APR based Apache Tomcat Native
> library which allows optimal performance in production environments was not
> found on the java.library.p
> ath: /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
> 14-Dec-2016 10:23:13.053 INFO [main] org.apache.coyote.AbstractProtocol.init
> Initializing ProtocolHandler ["http-nio-8080"]
> 14-Dec-2016 10:23:13.106 INFO [main] org.apache.tomcat.util.net.
> NioSelectorPool.getSharedSelector Using a shared selector for servlet
> write/read
> 14-Dec-2016 10:23:13.111 INFO [main] org.apache.coyote.AbstractProtocol.init
> Initializing ProtocolHandler ["ajp-nio-8009"]
> 14-Dec-2016 10:23:13.115 INFO [main] org.apache.tomcat.util.net.
> NioSelectorPool.getSharedSelector Using a shared selector for servlet
> write/read
> 14-Dec-2016 10:23:13.115 INFO [main] org.apache.catalina.startup.Catalina.load
> Initialization processed in 1450 ms
> 14-Dec-2016 10:23:13.178 INFO [main] 
> org.apache.catalina.core.StandardService.startInternal
> Starting service Catalina
> 14-Dec-2016 10:23:13.178 INFO [main] 
> org.apache.catalina.core.StandardEngine.startInternal
> Starting Servlet Engine: Apache Tomcat/8.5.9
> 14-Dec-2016 10:23:13.212 INFO [localhost-startStop-1]
> org.apache.catalina.startup.HostConfig.deployDirectory Deploying web
> application directory /usr/local/apache-tomcat-8.5.9/webapps/swordv2
> 14-Dec-2016 10:23:23.387 INFO [localhost-startStop-1]
> org.apache.jasper.servlet.TldScanner.scanJars 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.
>  INFO

Re: [dspace-tech] 6.0 upgrade

2016-12-14 Thread Hardy Pottinger

Hi, Larry... can you share with us the contents of
$CATALINA_HOME/logs/catalina.out? It will be helpful to see *why* Tomcat
isn't starting. Sometimes is as simple as a permissions/file ownership
issue. The catalina.out log file will help you.

--Hardy

On Wed, Dec 14, 2016 at 10:13 AM, Larry Hansard 
wrote:

> I'm still having issues with the 6.0 upgrade.  Tomcat will not start.  The
> database looks like it upgraded okay.  Will it work if I do a fresh_install
> instead of an upgrade then reload the postgres database from a current
> backup?
>
> Do I use "pg_dump dspace >filename"?
>
> Here is the database info:
>
> [dspace@digrepository ~]$ /dspace/bin/dspace database info
>
> Database Type: postgres
> Database URL: jdbc:postgresql://localhost:5432/dspace
> Database Schema: public
> Database Username: dspace
> Database Software: PostgreSQL version 9.4.10
> Database Driver: PostgreSQL Native Driver version PostgreSQL 9.4.1211
> PostgreSQL 'pgcrypto' extension installed/up-to-date? true (version=1.1)
>
> ++--
> +-+-+
> | Version| Description  |
> Installed on| State   |
> ++--
> +-+-+
> | 1.1| Initial DSpace 1.1 database schema   |
> |  | 1.2| Upgrade to DSpace 1.2 schema |
> |  | 1.3| Upgrade to DSpace 1.3 schema |
> |  | 1.3.9  | Drop constraint for DSpace 1 4 schema|
> |  | 1.4| Upgrade to DSpace 1.4 schema |
> |  | 1.5| Upgrade to DSpace 1.5 schema |
> |  | 1.5.9  | Drop constraint for DSpace 1 6 schema|
> |  | 1.6| Upgrade to DSpace 1.6 schema |
> |  | 1.7| Upgrade to DSpace 1.7 schema |
> |  | 1.8| Upgrade to DSpace 1.8 schema |
> |  | 3.0| Upgrade to DSpace 3.x schema |
> |  | 4.0| Initializing from DSpace 4.0 database schema |
> 2015-12-14 14:15:23 | Success |
> | 4.9.2015.10.26 | DS-2818 registry update  |
> | Ignored |
> | 5.0.2014.08.08 | DS-1945 Helpdesk Request a Copy  |
> 2015-12-14 14:15:23 | Success |
> | 5.0.2014.09.25 | DS 1582 Metadata For All Objects drop constraint |
> 2015-12-14 14:15:24 | Success |
> | 5.0.2014.09.26 | DS-1582 Metadata For All Objects |
> 2015-12-14 14:15:24 | Success |
> | 5.6.2016.08.23 | DS-3097  |
> 2016-12-09 15:15:01 | Success |
> | 6.0.2015.03.06 | DS 2701 Dso Uuid Migration   |
> 2016-12-09 15:15:01 | Success |
> | 6.0.2015.03.07 | DS-2701 Hibernate migration  |
> 2016-12-09 15:15:01 | Success |
> | 6.0.2015.08.31 | DS 2701 Hibernate Workflow Migration |
> 2016-12-09 15:15:17 | Success |
> | 6.0.2016.01.03 | DS-3024  |
> 2016-12-09 15:15:17 | Success |
> | 6.0.2016.01.26 | DS 2188 Remove DBMS Browse Tables|
> 2016-12-09 15:15:17 | Success |
> | 6.0.2016.02.25 | DS-3004-slow-searching-as-admin  |
> 2016-12-09 15:15:17 | Success |
> | 6.0.2016.04.01 | DS-1955 Increase embargo reason  |
> 2016-12-09 15:15:17 | Success |
> | 6.0.2016.04.04 | DS-3086-OAI-Performance-fix  |
> 2016-12-09 15:15:17 | Success |
> | 6.0.2016.04.14 | DS-3125-fix-bundle-bitstream-delete-rights   |
> 2016-12-09 15:15:18 | Success |
> | 6.0.2016.05.10 | DS-3168-fix-requestitem item id column   |
> 2016-12-09 15:15:18 | Success |
> | 6.0.2016.07.21 | DS-2775  |
> 2016-12-09 15:15:18 | Success |
> | 6.0.2016.07.26 | DS-3277 fix handle assignment|
> 2016-12-09 15:15:18 | Success |
> | 6.0.2016.08.23 | DS-3097  |
> 2016-12-09 15:15:18 | Success |
> ++--
> +-+-+
>
> Thanks -- Larry
>
> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to dspace-tech@googlegroups.com.
> Visit this group at https://groups.google.com/group/dspace-tech.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are

Re: [dspace-tech] 6.0 upgrade

Re: [dspace-tech] 6.0 upgrade

Re: [dspace-tech] 6.0 upgrade

Re: [dspace-tech] 6.0 upgrade

Re: [dspace-tech] 6.0 upgrade

Re: [dspace-tech] 6.0 upgrade

Re: [dspace-tech] 6.0 upgrade

Re: [dspace-tech] 6.0 upgrade

8 matches

Site Navigation

Mail list logo

Footer information