Error creating cluster with Cloudera Director getting: "Either anonymousId or userId must be provid"

[#1]

Hi,

I've been though the steps in the guides:

https://www.cloudera.com/documentation/director/1-5-x/topics/director_client_run.html

https://www.cloudera.com/documentation/director/latest/topics/director_simplecluster.html

to use Cloudera Director over AWS to create a cluster.

Using the Cloudera Director web approach and the Cloudera Director cliente approach.

In both situations Cloudera Director gets stucked at:

(Web)

Fails with red error screen

(Client)

Installing Cloudera Manager ...
* Starting ...

and if I see the log, in both cases appear:

[2018-08-01 09:18:27.486 +0000] ERROR [p-42f92896b75f-DefaultBootstrapDeploymentJob] - c.c.l.pipeline.util.PipelineRunner: Attempt to execute job failed

java.lang.IllegalStateException: Either anonymousId or userId must be provided.

            at com.segment.analytics.messages.MessageBuilder.build(MessageBuilder.java:198)

            at com.segment.analytics.Analytics.enqueue(Analytics.java:74)

            at com.cloudera.launchpad.api.jobs.DefaultBootstrapDeploymentJob.recordDeploymentAnalytics(DefaultBootstrapDeploymentJob.java:138)

            at com.cloudera.launchpad.api.jobs.DefaultBootstrapDeploymentJob.run(DefaultBootstrapDeploymentJob.java:64)

            at com.cloudera.launchpad.api.jobs.DefaultBootstrapDeploymentJob.run(DefaultBootstrapDeploymentJob.java:52)

            at com.cloudera.launchpad.pipeline.job.Job2.runUnchecked(Job2.java:31)

            at com.cloudera.launchpad.pipeline.job.Job2$$FastClassBySpringCGLIB$$54178502.invoke(<generated>)

            at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)

            at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:738)

            at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157)

            at org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:85)

            at com.cloudera.launchpad.pipeline.PipelineJobProfiler.profileJobRun(PipelineJobProfiler.java:60)

            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:606)

            at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:629)

            at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:618)

            at org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:70)

            at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)

            at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:92)

            at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)

            at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:673)

            at com.cloudera.launchpad.api.jobs.DefaultBootstrapDeploymentJob$$EnhancerBySpringCGLIB$$bef2a85b.runUnchecked(<generated>)

            at com.cloudera.launchpad.pipeline.util.PipelineRunner$JobCallable.call(PipelineRunner.java:201)

            at com.cloudera.launchpad.pipeline.util.PipelineRunner$JobCallable.call(PipelineRunner.java:172)

            at com.github.rholder.retry.AttemptTimeLimiters$NoAttemptTimeLimit.call(AttemptTimeLimiters.java:78)

            at com.github.rholder.retry.Retryer.call(Retryer.java:160)

            at com.cloudera.launchpad.pipeline.util.PipelineRunner.attemptMultipleJobExecutionsWithRetries(PipelineRunner.java:135)

            at com.cloudera.launchpad.pipeline.DatabasePipelineRunner.doRun(DatabasePipelineRunner.java:200)

            at com.cloudera.launchpad.pipeline.DatabasePipelineRunner.run(DatabasePipelineRunner.java:140)

            at com.cloudera.launchpad.ExceptionHandlingRunnable.run(ExceptionHandlingRunnable.java:57)

            at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)

            at java.util.concurrent.FutureTask.run(FutureTask.java:262)

            at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)

            at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)

            at java.lang.Thread.run(Thread.java:745)

Please someone knows what is happening? there is an open bug or something?

Thanks in advance!

[#2 · Accepted solution]

iasindev,

The symptoms you describe are due to a bug in the 2.8.0 standalone client. The standalone client commands are deprecated in 2.8.0 and unfortunately suffer from this bug.

In preference order, workarounds are:

1. Use the bootstrap-remote command with a Cloudera Director server. This is the preferred configuration.

or

2. Unset the segment analytics writeKey property for the cli by adding segment.analytics.writeKey: to /etc/cloudera-director-client/application.properties

or

3. Use the 2.7.1 standalone client. It does not suffer from this bug.

Good luck!

David

[#3 · Accepted solution]

iasindev,

The symptoms you describe are due to a bug in the 2.8.0 standalone client. The standalone client commands are deprecated in 2.8.0 and unfortunately suffer from this bug.

In preference order, workarounds are:

1. Use the bootstrap-remote command with a Cloudera Director server. This is the preferred configuration.

or

2. Unset the segment analytics writeKey property for the cli by adding segment.analytics.writeKey: to /etc/cloudera-director-client/application.properties

or

3. Use the 2.7.1 standalone client. It does not suffer from this bug.

Good luck!

David

[#4]

oh! there are a lot of options, thank you very much! I'm gonna try them thanks!

[#5]

Hi, 

I've tried the possibilities with mixed results:

1. Tried

worked at the beginning, but stopped suddenly with an error, and if I look at the director logs there was no error:

2. Tried

worked at the beginning but also failed at the end. This time there was registry at the director logs:

 

seems to be another bug this time with the Java installation at the Cloudera script, don't you think so?

3. Please can you tell from where can I download this previous version (2.7.1) ?

Thanks in advance!

[#6 · Accepted solution]

Hi iasindev,

For case #1, when using bootstrap-remote, most of the work is done on the associated Director server, so check the logs there for problems. It could be the same problem that surfaced in #2.

In #2, the error is occurring when Director is failing to access the CDH parcel repository over https. Are you hosting your own repository, or have you customized the Director truststore to no longer include common trusted certificates?

Older Director releases are available under https://archive.cloudera.com/director/ . Just drill down for your operating system to find the version you need.