Schema upgrade failing (4.2.f->5.0.a)

[bopolissimus]

The content is 1.5TB and the database files on disk (mysql) are around 17GB (the database dump is around 5GB).  alfresco and /share are both fine in 4.2.f.  When I upgrade to 5.0.a though:

In catalina.out, everything is fine until the log fragment below.  How would I go about figuring out what is breaking the upgrade?

2015-06-08 17:14:23,907  INFO  [domain.schema.SchemaBootstrap] [localhost-startStop-1] Normalized schema dumped to file /opt/alfresco/alf_data/alf_intermediate/alfresco-5.0.a/tomcat/temp/Alfresco/Alfresco-schema-MySQLInnoDBDialect-pre-upgrade-jbpm_-7347609668881407787.xml.
2015-06-08 17:14:23,907  INFO  [domain.schema.SchemaBootstrap] [localhost-startStop-1] Normalized schema dumped to file /opt/alfresco/alf_data/alf_intermediate/alfresco-5.0.a/tomcat/temp/Alfresco/Alfresco-schema-MySQLInnoDBDialect-pre-upgrade-act_-8693489867129267228.xml.
2015-06-08 17:14:34,071  WARN  [domain.schema.SchemaBootstrap] [localhost-startStop-1] Schema validation found 11 potential problems, results written to: /opt/alfresco/alf_data/alf_intermediate/alfresco-5.0.a/tomcat/temp/Alfresco/Alfresco-MySQLInnoDBDialect-Validation-Pre-Upgrade-alf_-3924253480265907687.txt
2015-06-08 17:14:34,137  INFO  [domain.schema.SchemaBootstrap] [localhost-startStop-1] Compared database schema with reference schema (all OK): class path resource [alfresco/dbscripts/create/org.hibernate.dialect.MySQLInnoDBDialect/Schema-Reference-AVM.xml]
2015-06-08 17:14:34,337  INFO  [domain.schema.SchemaBootstrap] [localhost-startStop-1] Compared database schema with reference schema (all OK): class path resource [alfresco/dbscripts/create/org.hibernate.dialect.MySQLInnoDBDialect/Schema-Reference-JBPM.xml]
2015-06-08 17:14:34,603  WARN  [domain.schema.SchemaBootstrap] [localhost-startStop-1] Schema validation found 16 potential problems, results written to: /opt/alfresco/alf_data/alf_intermediate/alfresco-5.0.a/tomcat/temp/Alfresco/Alfresco-MySQLInnoDBDialect-Validation-Pre-Upgrade-act_-2214938116786478717.txt
2015-06-08 17:14:41,315  INFO  [domain.schema.SchemaBootstrap] [localhost-startStop-1] Normalized schema dumped to file /opt/alfresco/alf_data/alf_intermediate/alfresco-5.0.a/tomcat/temp/Alfresco/Alfresco-schema-MySQLInnoDBDialect-pre-upgrade-alf_-6051651724617343060.xml.
2015-06-08 17:14:41,316  INFO  [domain.schema.SchemaBootstrap] [localhost-startStop-1] Normalized schema dumped to file /opt/alfresco/alf_data/alf_intermediate/alfresco-5.0.a/tomcat/temp/Alfresco/Alfresco-schema-MySQLInnoDBDialect-pre-upgrade-avm_-5344869175157373630.xml.
2015-06-08 17:14:41,316  INFO  [domain.schema.SchemaBootstrap] [localhost-startStop-1] Normalized schema dumped to file /opt/alfresco/alf_data/alf_intermediate/alfresco-5.0.a/tomcat/temp/Alfresco/Alfresco-schema-MySQLInnoDBDialect-pre-upgrade-jbpm_-7459549657158174894.xml.
2015-06-08 17:14:41,316  INFO  [domain.schema.SchemaBootstrap] [localhost-startStop-1] Normalized schema dumped to file /opt/alfresco/alf_data/alf_intermediate/alfresco-5.0.a/tomcat/temp/Alfresco/Alfresco-schema-MySQLInnoDBDialect-pre-upgrade-act_-9178924772918145188.xml.
2015-06-08 17:14:46,319  ERROR [domain.schema.SchemaBootstrap] [localhost-startStop-1] Schema auto-update failed
org.alfresco.error.AlfrescoRuntimeException: 05080000 A previous schema upgrade failed or was not completed.  Revert to the original database before attempting the upgrade again.
   at org.alfresco.repo.domain.schema.SchemaBootstrap.onBootstrap(SchemaBootstrap.java:1702)
   at org.springframework.extensions.surf.util.AbstractLifecycleBean.onApplicationEvent(AbstractLifecycleBean.java:56)
   at org.alfresco.repo.management.SafeApplicationEventMulticaster.multicastEventInternal(SafeApplicationEventMulticaster.java:209)
   at org.alfresco.repo.management.SafeApplicationEventMulticaster.multicastEvent(SafeApplicationEventMulticaster.java:180)
   at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:303)
   at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:911)
   at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:428)
   at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:276)
   at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:197)
   at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:47)
   at org.alfresco.web.app.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:63)
   at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4973)
   at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5467)
   at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
   at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
   at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
   at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:632)
   at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:1073)
   at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1857)
   at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
   at java.util.concurrent.FutureTask.run(FutureTask.java:262)
   at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
   at java.lang.Thread.run(Thread.java:745)

[bopolissimus]

bumping up log4.logger.org.alfresco.repo.domain.schema in */alfresco/extension/custom-log4j.properties didn't do anything but that might be pilot error.  Just while debugging I'll update the log4j.properties from webapps (and remove the war file so it doesn't get redeployed). 

I'm also now looking at the generated

Alfresco-MySQLInnoDBDialect-Validation-Pre-Upgrade-alf_-[0-9]+.txt file and fixing issues I see.  I don't think I should be having any schema issues at all, but somehow I *am* having them, so will work through those.

[bopolissimus]

Ah, it looks like it wasn't looking where I thought it was for the custom-log4.properties file.  logging is better now.