[
https://issues.apache.org/jira/browse/CLOUDSTACK-4165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13732978#comment-13732978
]
Alena Prokharchyk commented on CLOUDSTACK-4165:
-----------------------------------------------
After adding more logging to SecurityChecker, found out the root cause of the
error:
ERROR [utils.component.ComponentContext] (Timer-2:) System integrity check
failed. Refuse to startup
java.lang.NullPointerException
at
com.cloud.upgrade.dao.Upgrade410to420.persistLegacyZones(Upgrade410to420.java:633)
at
com.cloud.upgrade.dao.Upgrade410to420.performDataMigration(Upgrade410to420.java:76)
at
com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:264)
at
com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:389)
at
com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:90)
at
com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:54)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
2013-08-07 17:00:45.970:INFO::Shutdown hook executing
2013-08-07 17:00:45.975:INFO::Stopped [email protected]:8080
2013-08-07 17:00:46.482:INFO:/client:Closing Spring root WebApplicationContext
Happens during legacy zones update
> 3.0.6 to ASF 4.2 Upgrade: Data Migration step of the Upgrade Fails
> ------------------------------------------------------------------
>
> Key: CLOUDSTACK-4165
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4165
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.2.0
> Reporter: Chandan Purushothama
> Assignee: Alena Prokharchyk
> Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: management-server.zip, mysqldumps.zip
>
>
> =================
> Steps to Reproduce:
> =================
> 1. Deployed a 3.0.6 Advanced Zone Setup with two VMWare Clusters with one
> host in each Cluster. Used NFS Primary Storage.
> 2. Upgraded the Setup using the Latest 4.2 Build.
> ===========
> Observations:
> ===========
> On Starting the Management Server after Upgrading the RPMs, I observed that
> the schema of the setup got upgraded but failed before data migration phase
> started.
> =======================
> On Management Server Log:
> =======================
> 2013-08-07 14:10:57,271 DEBUG [utils.db.ScriptRunner] (Timer-1:null) INSERT
> IGNORE INTO `cloud`.`configuration` VALUES ('Advanced', 'DEFAULT',
> 'management-server', 'eip.use.multiple.netscalers', 'false', 'Should be set
> to true, if there will be multiple NetScaler devices providing EIP service in
> a zone')
> 2013-08-07 14:10:57,272 DEBUG [utils.db.ScriptRunner] (Timer-1:null) INSERT
> IGNORE INTO `cloud`.`configuration` VALUES ('Snapshots', 'DEFAULT',
> 'SnapshotManager', 'snapshot.backup.rightafter', 'true', 'backup snapshot
> right after snapshot is taken')
> 2013-08-07 14:10:57,363 TRACE [db.Transaction.Connection] (Timer-1:null) txn:
> Not closing DB connection because we're still in a transaction.
> 2013-08-07 14:10:57,364 DEBUG [db.Transaction.Transaction] (Timer-1:null)
> Rolling back the transaction: Time = 5301 Name =
> -CloudStartupServlet$1.run:52-TimerThread.mainLoop:534-TimerThread.run:484;
> called by
> -Transaction.rollback:896-Transaction.removeUpTo:839-Transaction.close:663-DatabaseUpgradeChecker.upgrade:293-DatabaseUpgradeChecker.check:389-ComponentContext.initComponentsLifeCycle:90-CloudStartupServlet$1.run:54-TimerThread.mainLoop:534-TimerThread.run:484
> 2013-08-07 14:10:57,365 TRACE [db.Transaction.Connection] (Timer-1:null)
> Closing DB connection: dbconn162979043
> 2013-08-07 14:10:57,366 TRACE [utils.db.GlobalLock] (Timer-1:null) lock
> DatabaseUpgrade is returned to free state, total holding time :8969
> 2013-08-07 14:10:57,366 TRACE [utils.db.GlobalLock] (Timer-1:null) lock
> DatabaseUpgrade is released, lock count :0
> 2013-08-07 14:10:57,366 ERROR [utils.component.ComponentContext]
> (Timer-1:null) System integrity check failed. Refuse to startup
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
