incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pradeep Soundararajan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-1003) Failed to start management server with master build
Date Mon, 21 Jan 2013 07:34:13 GMT

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

Pradeep Soundararajan commented on CLOUDSTACK-1003:
---------------------------------------------------

Rohit, 
QA need complete tar to verify ASF master that is the reason I have used waf (internally)
time being to generate the complete package. 

I think I have resolved this packaging issue last Friday.  Rayees has to verify. 

The complete error:
ERROR [utils.component.ComponentLocator] (main:) Unable to load configuration for management-server
from components.xml
com.cloud.utils.exception.CloudRuntimeException: Unable to find class: org.apache.cloudstack.acl.StaticRoleBasedAPIAccessChecker


I see this ACL plugin has got refactored in ASF master and placed under plugins directory.


I was suspecting it is a packaging issue so introduced a 'build.xml' (plugins/acl/static-role-based/build.xml)
for acl like other plugins in order to make it available in packaging. Also, added this respective
jar in cloud.spec file and added acl entry under build-cloud-plugins.xml as well.

I am able to verify from the waf logs that this was getting packaged properly.

Please let me know if I am overlooked with something.


                
> Failed to start management server with master build
> ---------------------------------------------------
>
>                 Key: CLOUDSTACK-1003
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1003
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: API, Install and Setup
>    Affects Versions: 4.1.0
>         Environment: Centos 6.0.3
>            Reporter: Rayees Namathponnan
>            Assignee: Pradeep Soundararajan
>            Priority: Blocker
>         Attachments: catalina.out
>
>
> Observed below error in MS log
> INFO  [cloud.server.ConfigurationServerImpl] (main:) Processing updateSSLKeyStore
> INFO  [cloud.server.ConfigurationServerImpl] (main:) SSL keystore located at /etc/cloud/management/cloud.keystore
> INFO  [cloud.server.ConfigurationServerImpl] (main:) Processing updateKeyPairs
> INFO  [cloud.server.ConfigurationServerImpl] (main:) Systemvm keypairs not found in database.
Need to store them in the database
> INFO  [cloud.server.ConfigurationServerImpl] (main:) Going to update systemvm iso with
generated keypairs if needed
> INFO  [utils.component.ComponentLocator] (main:) Config file found at /etc/cloud/management/components.xml.
 Configuring management-server
> INFO  [utils.component.ComponentLocator] (main:) Found component: com.cloud.configuration.dao.ConfigurationDao
in com.cloud.configuration.dao.ConfigurationDaoImpl - Configuration configuration server
> ERROR [utils.component.ComponentLocator] (main:) Unable to load configuration for management-server
from components.xml
> com.cloud.utils.exception.CloudRuntimeException: Unable to find class: org.apache.cloudstack.acl.StaticRoleBasedAPIAccessChecker
> 	at com.cloud.utils.component.ComponentLocator$XmlHandler.fillInfo(ComponentLocator.java:1028)
> 	at com.cloud.utils.component.ComponentLocator$XmlHandler.startElement(ComponentLocator.java:1089)
> 	at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
> 	at org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(Unknown Source)
> 	at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unknown Source)
> 	at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
Source)
> 	at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)

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

Mime
View raw message