Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Wed, 1 May 2013 23:40:16 +0000 (UTC)
From: "Prachi Damle (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12644735.1366926595864.257654.1367451616748@arcas>
In-Reply-To: <JIRA.12644735.1366926595864@arcas>
References: <JIRA.12644735.1366926595864@arcas>
Subject: [jira] [Commented] (CLOUDSTACK-2197) Management Server unable to
 start up
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CLOUDSTACK-2197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13647079#comment-13647079 ] 

Prachi Damle commented on CLOUDSTACK-2197:
------------------------------------------

I think this issue is same as: https://issues.apache.org/jira/browse/CLOUDSTACK-2201

Kishan has fixed CLOUDSTACK-2201, please can we retest this with a new latest master build to see if it fixes this issue as well?

                
> Management Server unable to start up
> ------------------------------------
>
>                 Key: CLOUDSTACK-2197
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2197
>             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
>         Environment: MS    ACS  4.2  	Revision: 099677a1244cd55fb98d3c40ee7881223dd9ac7c 
> build   4/25/2013   9:31  AM   
>            Reporter: angeline shen
>            Priority: Blocker
>             Fix For: 4.2.0
>
>         Attachments: management-server.log.gz
>
>
> MS   ACS  4.2  Revision: 099677a1244cd55fb98d3c40ee7881223dd9ac7c 
> build   4/25/2013   9:31  AM   
> 2013-04-25 14:05:59,818 INFO  [utils.component.ComponentContext] (main:null) Setup Spring Application context
> 2013-04-25 14:06:00,395 DEBUG [utils.crypt.EncryptionSecretKeyChecker] (main:null) Encryption Type: file
> 2013-04-25 14:06:08,556 INFO  [cloud.serializer.GsonHelper] (main:null) Default Builder inited.
> 2013-04-25 14:06:10,177 INFO  [cloudstack.discovery.ApiDiscoveryServiceImpl] (main:null) Api Discovery Service: Annotation, docstrings, api relation graph processed in 783.947921 ms
> 2013-04-25 14:06:11,240 INFO  [hypervisor.vmware.VmwareServerDiscoverer] (main:null) VmwareServerDiscoverer is constructed
> 2013-04-25 14:06:11,583 INFO  [web.context.ContextLoader] (main:null) Root WebApplicationContext: initialization completed in 15956 ms
> 2013-04-25 14:06:11,677 INFO  [cloud.utils.LogUtils] (main:null) log4j configuration found at /etc/cloudstack/management/log4j-cloud.xml
> 2013-04-25 14:06:11,713 INFO  [factory.annotation.AutowiredAnnotationBeanPostProcessor] (main:null) JSR-330 'javax.inject.Inject' annotation found and supported for autowiring
> 2013-04-25 14:06:28,994 INFO  [utils.component.ComponentContext] (Timer-1:null) Running SystemIntegrityChecker encryptionSecretKeyChecker
> 2013-04-25 14:06:28,998 DEBUG [utils.crypt.EncryptionSecretKeyChecker] (Timer-1:null) Encryption Type: file
> 2013-04-25 14:06:28,998 WARN  [utils.crypt.EncryptionSecretKeyChecker] (Timer-1:null) Encryption already enabled, is check() called twice?
> 2013-04-25 14:06:28,999 INFO  [utils.component.ComponentContext] (Timer-1:null) Running SystemIntegrityChecker databaseIntegrityChecker
> 2013-04-25 14:06:28,999 INFO  [cloud.upgrade.DatabaseIntegrityChecker] (Timer-1:null) Grabbing lock to check for database integrity.
> 2013-04-25 14:06:29,012 INFO  [cloud.upgrade.DatabaseIntegrityChecker] (Timer-1:null) Performing database integrity check
> 2013-04-25 14:06:29,156 DEBUG [cloud.upgrade.DatabaseIntegrityChecker] (Timer-1:null) No duplicate hosts with the same local storage found in database
> 2013-04-25 14:06:29,159 DEBUG [upgrade.dao.VersionDaoImpl] (Timer-1:null) Checking to see if the database is at a version before it was the version table is created
> 2013-04-25 14:06:29,303 INFO  [utils.component.ComponentContext] (Timer-1:null) Running SystemIntegrityChecker managementServerNode
> 2013-04-25 14:06:29,303 INFO  [utils.component.ComponentContext] (Timer-1:null) Running SystemIntegrityChecker premiumDatabaseUpgradeChecker
> 2013-04-25 14:06:29,303 INFO  [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) Grabbing lock to check for database upgrade.
> 2013-04-25 14:06:29,304 DEBUG [upgrade.dao.VersionDaoImpl] (Timer-1:null) Checking to see if the database is at a version before it was the version table is created
> 2013-04-25 14:06:29,311 INFO  [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) DB version = 4.0.0 Code Version = 4.2.0-SNAPSHOT
> 2013-04-25 14:06:29,311 INFO  [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) Database upgrade must be performed from 4.0.0 to 4.2.0-SNAPSHOT
> 2013-04-25 14:06:29,311 ERROR [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) The end upgrade version is actually at 4.1.0 but our management server code version is at 4.2.0-SNAPSHOT
> 2013-04-25 14:06:29,316 ERROR [utils.component.ComponentContext] (Timer-1:null) System integrity check failed. Refuse to startup
> (END) 

--
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