Hi,
I tried installation of Ubuntu MS with non-oss 8 Ubuntu Build. Management
server is failed to start with below exception:
2012-10-10 20:01:51,624 INFO [utils.component.ComponentLocator] (main:null)
Found component: com.cloud.ha.Investigator in
com.cloud.ha.CheckOnAgentInvestigator - SimpleInvestigator
2012-10-10 20:01:51,624 DEBUG [utils.component.ComponentLocator] (main:null)
Looking for class com.cloud.ha.VmwareInvestigator
2012-10-10 20:01:51,626 ERROR [utils.component.ComponentLocator] (main:null)
Unable to load configuration for management-server from components.xml
com.cloud.utils.exception.CloudRuntimeException: Unable to find class:
com.cloud.ha.VmwareInvestigator
at
com.cloud.utils.component.ComponentLocator$XmlHandler.fillInfo(ComponentLocator.java:997)
at
com.cloud.utils.component.ComponentLocator$XmlHandler.startElement(ComponentLocator.java:1058)
at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:504)
at
com.sun.org.apache.xerces.internal.parsers.AbstractXMLDocumentParser.emptyElement(AbstractXMLDocumentParser.java:182)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:1320)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2732)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:625)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:488)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:819)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:748)
at
com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:123)
at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1208)
at
com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:525)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:392)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:328)
at
com.cloud.utils.component.ComponentLocator.parse2(ComponentLocator.java:177)
at
com.cloud.utils.component.ComponentLocator.parse(ComponentLocator.java:234)
at
com.cloud.utils.component.ComponentLocator.getLocatorInternal(ComponentLocator.java:836)
at
com.cloud.utils.component.ComponentLocator.getLocator(ComponentLocator.java:874)
at
com.cloud.servlet.CloudStartupServlet.init(CloudStartupServlet.java:48)
at javax.servlet.GenericServlet.init(GenericServlet.java:212)
at
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1206)
at
org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1026)
at
org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4421)
at
org.apache.catalina.core.StandardContext.start(StandardContext.java:4734)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:799)
at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:779)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:601)
at
org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1079)
at
org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:1002)
at
org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:506)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1317)
at
org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:324)
at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1065)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:840)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1057)
at
org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463)
at
org.apache.catalina.core.StandardService.start(StandardService.java:525)
at
org.apache.catalina.core.StandardServer.start(StandardServer.java:754)
at org.apache.catalina.startup.Catalina.start(Catalina.java:595)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at
org.apache.commons.daemon.support.DaemonLoader.start(DaemonLoader.java:243)
Thanks and Regards,
Sailaja.M
-----Original Message-----
From: Sudha Ponnaganti [mailto:[email protected]]
Sent: Wednesday, October 10, 2012 7:47 PM
To: [email protected]
Subject: RE: [ASFCS40] Status for 4.0.0?
Yeah - your changes are validated on RHEL and Ubuntu is in progress.
Still will wait for Wido's changes and do one more validation again.
We are not repeating validation on OSS builds. Let us know if you made changes
for that packaging as well!
-----Original Message-----
From: Rohit Yadav [mailto:[email protected]]
Sent: Wednesday, October 10, 2012 7:04 AM
To: [email protected]
Subject: Re: [ASFCS40] Status for 4.0.0?
Regards,
Rohit Yadav
http://github.com/bhaisaab
On 10-Oct-2012, at 6:44 PM, Chip Childers <[email protected]> wrote:
> All,
>
> It appears that we have a couple of changes being made since I last
> looked last night:
>
> 1 - Rohit and Wido are making some modifications to the AWSAPI
> packaging. Guys - are we done?
>From my side awsapi packaging is done. I think QA is finished with the testing
>too, any one from QA, thumbs up?
>
> 2 - There is now a build job named "nightly-smoke-4.0" that is
> failing. What is it? Since it's new, is it's failure something that
> should block creating the release? FYI - our release process includes
> confirming that all jenkins.cs.o builds for the release branch are
> clear.
Have asked Prasanna to look into that.