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.

Exception when adding Cloudera Manager via the Cloudera Director web UI

SOLVED Go to solution

Exception when adding Cloudera Manager via the Cloudera Director web UI

New Contributor

Hi everyone,

 

I successfully set a Virtual Private Cloud on AWS and started an instance using the Cloudera Director AMI (ID ami-2957655e, created on October 16).

 

I logged into its Web panel, added an environment, and then attempted to add Cloudera Manager. I did not attempt to go as far as adding a cluster too, because I keep getting a bootstrap_failed error. This has happened a couple of times already, with the same error.

 

(OS: the tmplate for Manager and cluster instances uses an Amazon provisioned AMI running CentOS 6.5. The template uses t2.micro instances. Very small, I know, but this is excludsively to learn the workflow and how to use the interface. Once I see everything running smoothly, I will switch to larger sizes. What follows doesn't seem to be a memory issue anyway.)

 

I checked the /var/log/cloudera-director-server/application.log and I can see that the Director can SSH into the other instance, but then it throws this exception, something to do with Google's Guava library:

 

[2015-10-24 00:17:19] ERROR [pipeline-thread-1] - c.c.l.p.DatabasePipelineRunner: Pipeline 1efc9b36-50f9-4eca-874d-6a736779de59 suspended due to failure
java.lang.IllegalStateException: Optional.get() cannot be called on an absent value
        at com.google.common.base.Absent.get(Absent.java:42) ~[guava-15.0.jar!/:na]
        at com.cloudera.launchpad.inspector.LogInstalledPackagesAndRepositories.run(LogInstalledPackagesAndRepositories.java:37) ~[launchpad-inspector-1.5.0.jar!/:1.5.0]
        at com.cloudera.launchpad.inspector.LogInstalledPackagesAndRepositories.run(LogInstalledPackagesAndRepositories.java:23) ~[launchpad-inspector-1.5.0.jar!/:1.5.0]
        at com.cloudera.launchpad.pipeline.job.Job2.runUnchecked(Job2.java:31) ~[launchpad-pipeline-1.5.0.jar!/:1.5.0]
        at com.cloudera.launchpad.pipeline.job.Job2$$FastClassBySpringCGLIB$$54178502.invoke(<generated>) ~[spring-core-4.1.5.RELEASE.jar!/:1.5.0]
        at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204) ~[spring-core-4.1.5.RELEASE.jar!/:4.1.5.RELEASE]
        at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:717) ~[spring-aop-4.1.5.RELEASE.jar!/:4.1.5.RELEASE]
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157) ~[spring-aop-4.1.5.RELEASE.jar!/:4.1.5.RELEASE]
        at org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:97) ~[spring-aop-4.1.5.RELEASE.jar!/:4.1.5.RELEASE]
        at com.cloudera.launchpad.pipeline.PipelineJobProfiler$1.call(PipelineJobProfiler.java:55) ~[launchpad-pipeline-1.5.0.jar!/:1.5.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:51) ~[launchpad-pipeline-1.5.0.jar!/:1.5.0]
        at sun.reflect.GeneratedMethodAccessor125.invoke(Unknown Source) ~[na:na]
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.7.0_67]
        at java.lang.reflect.Method.invoke(Method.java:606) ~[na:1.7.0_67]
        at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621) ~[spring-aop-4.1.5.RELEASE.jar!/:4.1.5.RELEASE]
        at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:610) ~[spring-aop-4.1.5.RELEASE.jar!/:4.1.5.RELEASE]
        at org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:68) ~[spring-aop-4.1.5.RELEASE.jar!/:4.1.5.RELEASE]
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) ~[spring-aop-4.1.5.RELEASE.jar!/:4.1.5.RELEASE]
        at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:92) ~[spring-aop-4.1.5.RELEASE.jar!/:4.1.5.RELEASE]
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) ~[spring-aop-4.1.5.RELEASE.jar!/:4.1.5.RELEASE]
        at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:653) ~[spring-aop-4.1.5.RELEASE.jar!/:4.1.5.RELEASE]
        at com.cloudera.launchpad.inspector.LogInstalledPackagesAndRepositories$$EnhancerBySpringCGLIB$$5826f59a.runUnchecked(<generated>) ~[spring-core-4.1.5.RELEASE.jar!/:1.5.0]
        at com.cloudera.launchpad.pipeline.util.PipelineRunner$JobCallable.call(PipelineRunner.java:165) ~[launchpad-pipeline-1.5.0.jar!/:1.5.0]
        at com.cloudera.launchpad.pipeline.util.PipelineRunner$JobCallable.call(PipelineRunner.java:136) ~[launchpad-pipeline-1.5.0.jar!/:1.5.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:98) ~[launchpad-pipeline-1.5.0.jar!/:1.5.0]
        at com.cloudera.launchpad.pipeline.DatabasePipelineRunner.run(DatabasePipelineRunner.java:120) ~[launchpad-pipeline-database-1.5.0.jar!/:1.5.0]
        at com.cloudera.launchpad.ExceptionHandlingRunnable.run(ExceptionHandlingRunnable.java:57) [launchpad-common-1.5.0.jar!/:1.5.0]
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [na:1.7.0_67]
        at java.util.concurrent.FutureTask.run(FutureTask.java:262) [na:1.7.0_67]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [na:1.7.0_67]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [na:1.7.0_67]
        at java.lang.Thread.run(Thread.java:745) [na:1.7.0_67]
[2015-10-24 00:17:19] INFO  [pipeline-thread-1] - c.c.l.p.s.PipelineRepositoryService: Pipeline '1efc9b36-50f9-4eca-874d-6a736779de59': RUNNING -> SUSPENDED
[2015-10-24 00:17:19] INFO  [pipeline-thread-1] - c.c.l.d.DeploymentRepositoryService: Deployment 'Geomesa shepherd': BOOTSTRAP_FAILED -> BOOTSTRAP_FAILED

Any help is much appreciated.

 

If it is difficult to gauge what the problem is, maybe someone can suggest a tried and tested AMI that I could use for the template.

 

Thanks!

2 ACCEPTED SOLUTIONS

Accepted Solutions

Re: Exception when adding Cloudera Manager via the Cloudera Director web UI

Expert Contributor

With t2.micro the process of configuring Cloudera Manager will not be able to succeed. That instance type simply doesn't have enough memory for the main server process and all the management services. Our recommendation is to use m4.large or m4.xlarge. Also for Director itself you should use an instance like c3.large for best performance. 

 

Regarding the operation system our recommendation is to use the official releases either as community AMIs or from the AWS Marketplace:

https://aws.amazon.com/marketplace/seller-profile?id=16cb8b03-256e-4dde-8f34-1b0f377efe89 (for CentOS)

 

This documentation page contains some more instructions on how to find an AMI:

http://www.cloudera.com/content/www/en-us/documentation/director/latest/topics/director_deployment_a...

 

Also see Requirements and Supported Versions for additional information:

http://www.cloudera.com/content/www/en-us/documentation/director/latest/topics/director_deployment_r...

Re: Exception when adding Cloudera Manager via the Cloudera Director web UI

Expert Contributor

On eu-west-1 (Ireland) you could try the official CentOS 6.5 marketplace AMI with ID: ami-42718735 

https://aws.amazon.com/marketplace/pp/B00IOYDTV6 (you can find it by clicking on Continue and on the Manual Launch tab)

 

Another option is to use RHEL 6.6 HVM community AMI with ID: ami-cf3b47b8 

I found that by doing a search on the Community AMIs page for "rhel-6.6 hvm 2015". 

 

It's good that you are using AmazonProvidedDNS because that's easiest option to start with. 

12 REPLIES 12

Re: Exception when adding Cloudera Manager via the Cloudera Director web UI

Expert Contributor

With t2.micro the process of configuring Cloudera Manager will not be able to succeed. That instance type simply doesn't have enough memory for the main server process and all the management services. Our recommendation is to use m4.large or m4.xlarge. Also for Director itself you should use an instance like c3.large for best performance. 

 

Regarding the operation system our recommendation is to use the official releases either as community AMIs or from the AWS Marketplace:

https://aws.amazon.com/marketplace/seller-profile?id=16cb8b03-256e-4dde-8f34-1b0f377efe89 (for CentOS)

 

This documentation page contains some more instructions on how to find an AMI:

http://www.cloudera.com/content/www/en-us/documentation/director/latest/topics/director_deployment_a...

 

Also see Requirements and Supported Versions for additional information:

http://www.cloudera.com/content/www/en-us/documentation/director/latest/topics/director_deployment_r...

Re: Exception when adding Cloudera Manager via the Cloudera Director web UI

New Contributor

Thank you, Andrei. That was so fast!

 

I will do as you suggest, and then come back to mark the answer as correct if everything works.

Re: Exception when adding Cloudera Manager via the Cloudera Director web UI

New Contributor

I thought that it might be useful to also see some of the output before the exception:

 

[2015-10-24 00:17:16] INFO  [pipeline-thread-1] - c.cloudera.launchpad.sshj.SshJClient: Attempting SSH connection.
[2015-10-24 00:17:16] WARN  [reader] - c.c.l.sshj.TrustAnyHostKeyVerifier: Host key for 10.0.0.69 was automatically accepted
[2015-10-24 00:17:16] INFO  [io-thread-1] - ssh:10.0.0.69: CentOS release 6.5 (Final)
[2015-10-24 00:17:16] INFO  [io-thread-1] - ssh:10.0.0.69: Kernel \r on an \m
[2015-10-24 00:17:16] INFO  [io-thread-2] - ssh:10.0.0.69: bash: sudo: command not found
[2015-10-24 00:17:16] INFO  [io-thread-1] - ssh:10.0.0.69: bash: apt-get: command not found
[2015-10-24 00:17:16] INFO  [io-thread-1] - ssh:10.0.0.69: bash: zypper: command not found
[2015-10-24 00:17:17] INFO  [io-thread-1] - ssh:10.0.0.69: bash: java: command not found
[2015-10-24 00:17:17] INFO  [io-thread-1] - ssh:10.0.0.69: Python 2.6.6
[2015-10-24 00:17:17] INFO  [io-thread-2] - ssh:10.0.0.69: bash: sudo: command not found
[2015-10-24 00:17:17] WARN  [pipeline-thread-1] - c.c.l.i.OperatingSystemCapabilitiesInspector: 'sudo' command not found
[2015-10-24 00:17:17] INFO  [io-thread-2] - ssh:10.0.0.69: SELinux status:                 disabled
[2015-10-24 00:17:17] INFO  [io-thread-2] - ssh:10.0.0.69: bash: sudo: command not found
[2015-10-24 00:17:17] WARN  [pipeline-thread-1] - c.c.l.i.OperatingSystemCapabilitiesInspector: 'iptables-save' command not found
[2015-10-24 00:17:17] INFO  [io-thread-2] - ssh:10.0.0.69: ip-10-0-0-69.eu-west-1.compute.internal
[2015-10-24 00:17:17] INFO  [io-thread-2] - ssh:10.0.0.69: bash: nslookup: command not found
[2015-10-24 00:17:17] WARN  [pipeline-thread-1] - c.c.l.i.OperatingSystemCapabilitiesInspector: 'nslookup' command not found
[2015-10-24 00:17:19] INFO  [io-thread-2] - ssh:10.0.0.69: ip-10-0-0-69.eu-west-1.compute.internal
[2015-10-24 00:17:19] INFO  [io-thread-2] - ssh:10.0.0.69: 10.0.0.69
[2015-10-24 00:17:19] DEBUG [pipeline-thread-1] - c.c.l.i.OperatingSystemCapabilitiesInspector: FQDN reported is ip-10-0-0-69.eu-west-1.compute.internal
[2015-10-24 00:17:19] INFO  [pipeline-thread-1] - c.c.l.pipeline.util.PipelineRunner: << DatabaseValue{delegate=PersistentValueEntity{id=103, pipeline=1efc9b36-50f9-4eca-874d-6a736779de59,  ...
[2015-10-24 00:17:19] INFO  [pipeline-thread-1] - c.c.l.pipeline.util.PipelineRunner: >> LogInstalledPackagesAndRepositories/2 [PluggableComputeInstance{ipAddress=Optional.of(10.0.0.69), delegate=null} Instance{virtualInstance= ...
[2015-10-24 00:17:19] ERROR [pipeline-thread-1] - c.c.l.pipeline.util.PipelineRunner: Attempt to execute job failed
java.lang.IllegalStateException: Optional.get() cannot be called on an absent value

Cheers

Re: Exception when adding Cloudera Manager via the Cloudera Director web UI

Expert Contributor

That failing DNS could indicate either a problem with CentOS 6.5 AMI you are using or with the VPC DNS  settings.

 

Can you share the CentOS AMI ID? For VPC are you using AmazonProvidedDNS or a custom server? 

Re: Exception when adding Cloudera Manager via the Cloudera Director web UI

New Contributor

Here it is:

 

ID: ami-944a0be3

 

AMI Name: Amazon_CentOS_6-5-x86-64_1.0rev15_2015-Jun-29_12.39.00
 
I'm using AmazonProvidedDNS for VPC.

Re: Exception when adding Cloudera Manager via the Cloudera Director web UI

Expert Contributor

On eu-west-1 (Ireland) you could try the official CentOS 6.5 marketplace AMI with ID: ami-42718735 

https://aws.amazon.com/marketplace/pp/B00IOYDTV6 (you can find it by clicking on Continue and on the Manual Launch tab)

 

Another option is to use RHEL 6.6 HVM community AMI with ID: ami-cf3b47b8 

I found that by doing a search on the Community AMIs page for "rhel-6.6 hvm 2015". 

 

It's good that you are using AmazonProvidedDNS because that's easiest option to start with. 

Re: Exception when adding Cloudera Manager via the Cloudera Director web UI

New Contributor

Thanks!

 

That's what I just did. I'm waiting now for the bootstraping of the Manager, on exactly this AMI, in an t3.xlarge instance.

 

Just as a side note. Earlier, before I started writing on this forum, I started a separate installation of Cloudera Manager, via CLI, using a micro instance and that Amazon version of CentOS - just like in the earlier setup. It has finished successfuly now; I only need to give it  the IPs of workers.

Re: Exception when adding Cloudera Manager via the Cloudera Director web UI

New Contributor

The official CentOS 6.5 marketplace AMI with ID: ami-42718735, on a larger instance, and the Cloudera Manager was added successfully.

 

Thank you for your support!

Re: Exception when adding Cloudera Manager via the Cloudera Director web UI

Expert Contributor

That's great! Can you share more about your use case? What services are you planning to run part of the cluster? Is this going to be a long running cluster?