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.

ERROR: ClusterDock installation

Re: ERROR: ClusterDock installation

Rising Star
I tend to blame devicemapper for most Docker problems. :) Try again with Ubuntu 14.04 or 16.04?

Re: ERROR: ClusterDock installation

New Contributor

I deleted /var/log/docker when retrying, so it should have a clean devicemapper.

 

Anyway, I ssh to node-1.cluster and here is what I saw in the log file for cloudera manager:

 

016-09-27 08:53:19,023 ERROR ParcelUpdateService:com.cloudera.parcel.components.ParcelDownloaderImpl: (9 skipped) Unable to retrieve remote parcel repository m

anifest

java.util.concurrent.ExecutionException: java.net.ConnectException: https://archive.cloudera.com/cdh5/parcels/5.8/manifest.json

        at com.ning.http.client.providers.netty.NettyResponseFuture.abort(NettyResponseFuture.java:297)

        at com.ning.http.client.providers.netty.NettyConnectListener.operationComplete(NettyConnectListener.java:104)

....

 

Caused by: java.net.ConnectException: https://archive.cloudera.com/cdh5/parcels/5.8/manifest.json

        at com.ning.http.client.providers.netty.NettyConnectListener.operationComplete(NettyConnectListener.java:100)

        ... 16 more

Caused by: java.nio.channels.UnresolvedAddressException

        at sun.nio.ch.Net.checkAddress(Net.java:127)

        at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:644)

        at org.jboss.netty.channel.socket.nio.NioClientSocketPipelineSink.connect(NioClientSocketPipelineSink.java:139)

        at org.jboss.netty.channel.socket.nio.NioClientSocketPipelineSink.eventSunk(NioClientSocketPipelineSink.java:102)

        at org.jboss.netty.handler.ssl.SslHandler.handleDownstream(SslHandler.java:467)

        at org.jboss.netty.handler.codec.oneone.OneToOneEncoder.handleDownstream(OneToOneEncoder.java:55)

        at org.jboss.netty.handler.codec.http.HttpClientCodec.handleDownstream(HttpClientCodec.java:97)

        at org.jboss.netty.handler.stream.ChunkedWriteHandler.handleDownstream(ChunkedWriteHandler.java:108)

        at org.jboss.netty.channel.Channels.connect(Channels.java:642)

        at org.jboss.netty.channel.AbstractChannel.connect(AbstractChannel.java:204)

        at org.jboss.netty.bootstrap.ClientBootstrap.connect(ClientBootstrap.java:230)

        at org.jboss.netty.bootstrap.ClientBootstrap.connect(ClientBootstrap.java:183)

        at com.ning.http.client.providers.netty.NettyAsyncHttpProvider.doConnect(NettyAsyncHttpProvider.java:999)

        ... 13 more

2016-09-27 08:53:56,229 INFO CMMetricsForwarder-0:com.cloudera.server.cmf.components.ClouderaManagerMetricsForwarder: (29 skipped) Failed to send metrics.

java.lang.reflect.UndeclaredThrowableException

        at com.sun.proxy.$Proxy103.writeMetrics(Unknown Source)

        at com.cloudera.server.cmf.components.ClouderaManagerMetricsForwarder.sendWithAvro(ClouderaManagerMetricsForwarder.java:325)

        at com.cloudera.server.cmf.components.ClouderaManagerMetricsForwarder.sendMetrics(ClouderaManagerMetricsForwarder.java:312)

        at com.cloudera.server.cmf.components.ClouderaManagerMetricsForwarder.run(ClouderaManagerMetricsForwarder.java:146)

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

        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)

 

Re: ERROR: ClusterDock installation

New Contributor

the problem is fixed by not using the default cdh cluster or node names.

 

clusterdock_run ./bin/start_cluster -n [new cluster name] cdh --primary-node=node1 --secondary-node=node{2..3}

 

I hope this would give you a hint as what the issue really is.

Re: ERROR: ClusterDock installation

Rising Star
Not sure. Assuming there aren't any existing containers or networks with those names already running, the names shouldn't matter much.

Re: ERROR: ClusterDock installation

Contributor

try to flush the 

/etc/hosts

with old entries the script added

and

gieve another name to the cluster

clusterdock_run ./bin/start_cluster -n mycluster000

it worked for me