Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Director fails to bootstrap cloudera manager - command GlobalHostInstall fails

SOLVED Go to solution

Director fails to bootstrap cloudera manager - command GlobalHostInstall fails

New Contributor

I am trying to test out the Cloudera Navigator product on the Google Cloud Compute infrastructure. As part of that effort, I have been able to install Cloudera Director.

 

Now, I am trying to install the Cloudera Manager (and eventually a Hadoop/Spark cluster) using the Cloudera Director UI.

 

I am using the RHEL 6.7 image for the VM hosting the cloudera director, and my instance template (used for cloudera manager) is also set to use rhel6.

 

The Cloudera Manager installation is currently failing. On the UI of Cloudera Director, all I am seeing is an error message saying "bootstrap failed".

 

From the Application.log (available in /var/log/cloudera-director-server) I see the following error message.

 

 

 

[2016-02-16 21:39:06] INFO [pipeline-thread-1] - c.c.l.b.UnboundedWaitForApiCommand: Waiting for ApiCommand{id=21, name=GlobalHostInstall, startTime=Tue Feb 16 21:39:06 UTC 2016, endTime=null, active=true, success=null, resultMessage=null,
serviceRef=null, roleRef=null, hostRef=null, parent=null}
[2016-02-16 21:39:21] ERROR [pipeline-thread-1] - c.c.l.b.c.BootstrapClouderaManagerAgent: Command GlobalHostInstall with ID 21 failed after 5 tries. Details: ApiCommand{id=21, name=GlobalHostInstall, startTime=Tue Feb 16 21:39:06 UTC 2016, endTime=Tue Feb 16 21:39:16 UTC 2016, active=false, success=false, resultMessage=Command completed with 0/1 successful subcommands, serviceRef=null, roleRef=null, hostRef=null, parent=null}
[2016-02-16 21:39:21] ERROR [pipeline-thread-1] - c.c.l.pipeline.util.PipelineRunner: Attempt to execute job failed
com.cloudera.launchpad.pipeline.UnrecoverablePipelineError: Cloudera Manager agent installation failed on instance '10.240.0.62' after 5 tries.
at com.cloudera.launchpad.bootstrap.cluster.BootstrapClouderaManagerAgent$WaitForSuccessOrRetryOnFailure.run(BootstrapClouderaManagerAgent.java:256) ~[launchpad-bootstrap-2.0.0.jar!/:2.0.0]
at com.cloudera.launchpad.bootstrap.cluster.BootstrapClouderaManagerAgent$WaitForSuccessOrRetryOnFailure.run(BootstrapClouderaManagerAgent.java:225) ~[launchpad-bootstrap-2.0.0.jar!/:2.0.0]
at com.cloudera.launchpad.pipeline.job.Job4.runUnchecked(Job4.java:33) ~[launchpad-pipeline-2.0.0.jar!/:2.0.0]
at com.cloudera.launchpad.pipeline.job.Job4$$FastClassBySpringCGLIB$$54178504.invoke(<generated>) ~[spring-core-4.1.6.RELEASE.jar!/:2.0.0]
at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204) ~[spring-core-4.1.6.RELEASE.jar!/:4.1.6.RELEASE]
at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:717) ~[spring-aop-4.1.6.RELEASE.jar!/:4.1.6.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157) ~[spring-aop-4.1.6.RELEASE.jar!/:4.1.6.RELEASE]
at org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:97) ~[spring-aop-4.1.6.RELEASE.jar!/:4.1.6.RELEASE]
at com.cloudera.launchpad.pipeline.PipelineJobProfiler$1.call(PipelineJobProfiler.java:67) ~[launchpad-pipeline-2.0.0.jar!/:2.0.0]
at com.codahale.metrics.Timer.time(Timer.java:101) ~[metrics-core-3.1.0.jar!/:3.1.0]
at com.cloudera.launchpad.pipeline.PipelineJobProfiler.profileJobRun(PipelineJobProfiler.java:63) ~[launchpad-pipeline-2.0.0.jar!/:2.0.0]
at sun.reflect.GeneratedMethodAccessor126.invoke(Unknown Source) ~[na:na]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_66]
at java.lang.reflect.Method.invoke(Method.java:497) ~[na:1.8.0_66]
at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621) ~[spring-aop-4.1.6.RELEASE.jar!/:4.1.6.RELEASE]
at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:610) ~[spring-aop-4.1.6.RELEASE.jar!/:4.1.6.RELEASE]
at org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:68) ~[spring-aop-4.1.6.RELEASE.jar!/:4.1.6.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) ~[spring-aop-4.1.6.RELEASE.jar!/:4.1.6.RELEASE]
at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:92) ~[spring-aop-4.1.6.RELEASE.jar!/:4.1.6.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) ~[spring-aop-4.1.6.RELEASE.jar!/:4.1.6.RELEASE]
at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:653) ~[spring-aop-4.1.6.RELEASE.jar!/:4.1.6.RELEASE]
at com.cloudera.launchpad.bootstrap.cluster.BootstrapClouderaManagerAgent$WaitForSuccessOrRetryOnFailure$$EnhancerBySpringCGLIB$$b10acb52.runUnchecked(<generated>) ~[spring-core-4.1.6.RELEASE.jar!/:2.0.0]
at com.cloudera.launchpad.pipeline.util.PipelineRunner$JobCallable.call(PipelineRunner.java:159) [launchpad-pipeline-2.0.0.jar!/:2.0.0]
at com.cloudera.launchpad.pipeline.util.PipelineRunner$JobCallable.call(PipelineRunner.java:130) [launchpad-pipeline-2.0.0.jar!/:2.0.0]
at com.github.rholder.retry.AttemptTimeLimiters$NoAttemptTimeLimit.call(AttemptTimeLimiters.java:78) [guava-retrying-1.0.6.jar!/:na]
at com.github.rholder.retry.Retryer.call(Retryer.java:110) [guava-retrying-1.0.6.jar!/:na]
at com.cloudera.launchpad.pipeline.util.PipelineRunner.attemptMultipleJobExecutionsWithRetries(PipelineRunner.java:99) [launchpad-pipeline-2.0.0.jar!/:2.0.0]
at com.cloudera.launchpad.pipeline.DatabasePipelineRunner.run(DatabasePipelineRunner.java:125) [launchpad-pipeline-database-2.0.0.jar!/:2.0.0]
at com.cloudera.launchpad.ExceptionHandlingRunnable.run(ExceptionHandlingRunnable.java:57) [launchpad-common-2.0.0.jar!/:2.0.0]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_66]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [na:1.8.0_66]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_66]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_66]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_66]
[2016-02-16 21:39:21] ERROR [pipeline-thread-1] - c.c.l.p.DatabasePipelineRunner: Encountered an unrecoverable error
com.cloudera.launchpad.pipeline.UnrecoverablePipelineError: Cloudera Manager agent installation failed on instance '10.240.0.62' after 5 tries.
at com.cloudera.launchpad.bootstrap.cluster.BootstrapClouderaManagerAgent$WaitForSuccessOrRetryOnFailure.run(BootstrapClouderaManagerAgent.java:256) ~[launchpad-bootstrap-2.0.0.jar!/:2.0.0]
at com.cloudera.launchpad.bootstrap.cluster.BootstrapClouderaManagerAgent$WaitForSuccessOrRetryOnFailure.run(BootstrapClouderaManagerAgent.java:225) ~[launchpad-bootstrap-2.0.0.jar!/:2.0.0]
at com.cloudera.launchpad.pipeline.job.Job4.runUnchecked(Job4.java:33) ~[launchpad-pipeline-2.0.0.jar!/:2.0.0]
at com.cloudera.launchpad.pipeline.job.Job4$$FastClassBySpringCGLIB$$54178504.invoke(<generated>) ~[spring-core-4.1.6.RELEASE.jar!/:2.0.0]
at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204) ~[spring-core-4.1.6.RELEASE.jar!/:4.1.6.RELEASE]
at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:717) ~[spring-aop-4.1.6.RELEASE.jar!/:4.1.6.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157) ~[spring-aop-4.1.6.RELEASE.jar!/:4.1.6.RELEASE]
at org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:97) ~[spring-aop-4.1.6.RELEASE.jar!/:4.1.6.RELEASE]
at com.cloudera.launchpad.pipeline.PipelineJobProfiler$1.call(PipelineJobProfiler.java:67) ~[launchpad-pipeline-2.0.0.jar!/:2.0.0]
at com.codahale.metrics.Timer.time(Timer.java:101) ~[metrics-core-3.1.0.jar!/:3.1.0]
at com.cloudera.launchpad.pipeline.PipelineJobProfiler.profileJobRun(PipelineJobProfiler.java:63) ~[launchpad-pipeline-2.0.0.jar!/:2.0.0]
at sun.reflect.GeneratedMethodAccessor126.invoke(Unknown Source) ~[na:na]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_66]
at java.lang.reflect.Method.invoke(Method.java:497) ~[na:1.8.0_66]
at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621) ~[spring-aop-4.1.6.RELEASE.jar!/:4.1.6.RELEASE]
at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:610) ~[spring-aop-4.1.6.RELEASE.jar!/:4.1.6.RELEASE]
at org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:68) ~[spring-aop-4.1.6.RELEASE.jar!/:4.1.6.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) ~[spring-aop-4.1.6.RELEASE.jar!/:4.1.6.RELEASE]
at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:92) ~[spring-aop-4.1.6.RELEASE.jar!/:4.1.6.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) ~[spring-aop-4.1.6.RELEASE.jar!/:4.1.6.RELEASE]
at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:653) ~[spring-aop-4.1.6.RELEASE.jar!/:4.1.6.RELEASE]
at com.cloudera.launchpad.bootstrap.cluster.BootstrapClouderaManagerAgent$WaitForSuccessOrRetryOnFailure$$EnhancerBySpringCGLIB$$b10acb52.runUnchecked(<generated>) ~[spring-core-4.1.6.RELEASE.jar!/:2.0.0]
at com.cloudera.launchpad.pipeline.util.PipelineRunner$JobCallable.call(PipelineRunner.java:159) ~[launchpad-pipeline-2.0.0.jar!/:2.0.0]
at com.cloudera.launchpad.pipeline.util.PipelineRunner$JobCallable.call(PipelineRunner.java:130) ~[launchpad-pipeline-2.0.0.jar!/:2.0.0]
at com.github.rholder.retry.AttemptTimeLimiters$NoAttemptTimeLimit.call(AttemptTimeLimiters.java:78) ~[guava-retrying-1.0.6.jar!/:na]
at com.github.rholder.retry.Retryer.call(Retryer.java:110) ~[guava-retrying-1.0.6.jar!/:na]
at com.cloudera.launchpad.pipeline.util.PipelineRunner.attemptMultipleJobExecutionsWithRetries(PipelineRunner.java:99) ~[launchpad-pipeline-2.0.0.jar!/:2.0.0]
at com.cloudera.launchpad.pipeline.DatabasePipelineRunner.run(DatabasePipelineRunner.java:125) ~[launchpad-pipeline-database-2.0.0.jar!/:2.0.0]
at com.cloudera.launchpad.ExceptionHandlingRunnable.run(ExceptionHandlingRunnable.java:57) [launchpad-common-2.0.0.jar!/:2.0.0]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_66]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [na:1.8.0_66]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_66]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_66]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_66]
[2016-02-16 21:39:21] ERROR [pipeline-thread-1] - c.c.l.p.DatabasePipelineRunner: Pipeline '91780dcc-d908-4f0e-b1be-6b1b632476c6' failed
at com.cloudera.launchpad.bootstrap.cluster.BootstrapClouderaManagerAgent$WaitForSuccessOrRetryOnFailure$$EnhancerBySpringCGLIB$$b10acb52
at com.cloudera.launchpad.bootstrap.cluster.BootstrapClouderaManagerAgent.HostInstall:1
 

1 ACCEPTED SOLUTION

Accepted Solutions

Re: Director fails to bootstrap cloudera manager - command GlobalHostInstall fails

New Contributor

Thanks dhan. Looks like your solution worked. I was able to deploy the Cloudera Manager (haven't tried using it yet though) - just that the install succeeded.

 

I have a few notes for the other community folks -

 

1. Instead of the image URL dhan provided, I used the following URL -

    https://www.googleapis.com/compute/v1/projects/rhel-cloud/global/images/rhel-6-v20160211

 

    This seems to be the latest RHEL 6 image.

 

    Checking the My Console > Compute Engine > Images > <open the image link> > Equivalent Rest link gives you the image path.

 

2. I was monitoring the /var/log/cloudera-director-server/application.log during this install process.

    When saving the instance template with the above mentioned image URL, I noticed this log entry which says -

 

[2016-02-17 19:18:20] INFO [qtp239217021-45] - c.c.d.g.c.GoogleComputeInstanceTemplateConfigurationValidator: path parameter: Invalid path 'google.compute.imageAliases.https://www.googleapis.com/compute/v1/projects/rhel-cloud/global/images
/rhel-6-v20160211': Token not allowed in path expression: ':' (you can double-quote this token if you really want it here)

 

    However, if you actually try to use "" around the image URL, some sort of validation fails and the UI does not allow you to save the instance template.

 

   Ignoring the log (i.e. using the full URL without the quotes) however seemed to be innocuous (for now).

5 REPLIES 5

Re: Director fails to bootstrap cloudera manager - command GlobalHostInstall fails

New Contributor

I can upload the entire application.log file if that helps.

 

Let me know how you guys prefer to access that log.

Re: Director fails to bootstrap cloudera manager - command GlobalHostInstall fails

Expert Contributor

This is likely caused by an issue with the version 1.0.1 of the director-google-plugin.

 

See Known Issues under the heading "Incorrect yum repo definitions for Google Compute Engine RHEL images"

 

The workaround is to specify the complete image URL for https://www.googleapis.com/compute/v1/projects/rhel-cloud/global/images/rhel-6-v20160119 instead of using the rhel6 alias.

 

A fix for this issue is expected to be included in the next release of the director-google-plugin and Director.

 

Re: Director fails to bootstrap cloudera manager - command GlobalHostInstall fails

New Contributor

Thanks dhan. Looks like your solution worked. I was able to deploy the Cloudera Manager (haven't tried using it yet though) - just that the install succeeded.

 

I have a few notes for the other community folks -

 

1. Instead of the image URL dhan provided, I used the following URL -

    https://www.googleapis.com/compute/v1/projects/rhel-cloud/global/images/rhel-6-v20160211

 

    This seems to be the latest RHEL 6 image.

 

    Checking the My Console > Compute Engine > Images > <open the image link> > Equivalent Rest link gives you the image path.

 

2. I was monitoring the /var/log/cloudera-director-server/application.log during this install process.

    When saving the instance template with the above mentioned image URL, I noticed this log entry which says -

 

[2016-02-17 19:18:20] INFO [qtp239217021-45] - c.c.d.g.c.GoogleComputeInstanceTemplateConfigurationValidator: path parameter: Invalid path 'google.compute.imageAliases.https://www.googleapis.com/compute/v1/projects/rhel-cloud/global/images
/rhel-6-v20160211': Token not allowed in path expression: ':' (you can double-quote this token if you really want it here)

 

    However, if you actually try to use "" around the image URL, some sort of validation fails and the UI does not allow you to save the instance template.

 

   Ignoring the log (i.e. using the full URL without the quotes) however seemed to be innocuous (for now).

Re: Director fails to bootstrap cloudera manager - command GlobalHostInstall fails

Expert Contributor

Thanks for the followup. It's really helpful for the community to see the resolution that you have reached.

 

I've opened up an issue internally to investigate the log message and validation with quotes. I agree that the log message is innocuous.

Highlighted

Re: Director fails to bootstrap cloudera manager - command GlobalHostInstall fails

New Contributor

After getting past this error, we are running into this error;

https://community.cloudera.com/t5/Cloudera-Manager-Installation/Issues-installing-Cloudera-Manager-5...

[org.apache.oozie.service.ShareLibService], Not able to cache sharelib. An Admin needs to install the sharelib with oozie-setup.sh and issue the 'oozie admin' CLI command to update the sharelib