cloudera / clusterdock

Apache License 2.0
70 stars 57 forks source link

Cloudera Manager UI URL suppressed? #6

Closed randyzwitch closed 8 years ago

randyzwitch commented 8 years ago

From the Cloudera blog post:

Once the cluster is running and the health of your CDH services is validated, you can access the cluster through the Cloudera Manager UI (the address and port number are shown at the end of the startup process).

But there's no URL...

HQSMD-150442:clusterdock rzwitc200$ clusterdock_run ./bin/start_cluster -n testing cdh --primary-node=node-1 --secondary-nodes='node-{2..4}'
Password:
INFO:clusterdock.cluster:Successfully started node-3.testing (IP address: 192.168.124.4).
INFO:clusterdock.cluster:Successfully started node-4.testing (IP address: 192.168.124.5).
INFO:clusterdock.cluster:Successfully started node-2.testing (IP address: 192.168.124.3).
INFO:clusterdock.cluster:Successfully started node-1.testing (IP address: 192.168.124.2).
INFO:clusterdock.cluster:Started cluster in 7.95 seconds.
INFO:clusterdock.topologies.cdh.actions:Changing server_host to node-1.testing in /etc/cloudera-scm-agent/config.ini...
INFO:clusterdock.topologies.cdh.actions:Removing files (/var/lib/cloudera-scm-agent/uuid, /dfs*/dn/current/*) from hosts (node-3.testing, node-4.testing)...
INFO:clusterdock.topologies.cdh.actions:Restarting CM agents...
cloudera-scm-agent is already stopped
Starting cloudera-scm-agent: [  OK  ]
Stopping cloudera-scm-agent: [  OK  ]
Stopping cloudera-scm-agent: [  OK  ]
Stopping cloudera-scm-agent: [  OK  ]
Starting cloudera-scm-agent: [  OK  ]
Starting cloudera-scm-agent: [  OK  ]
Starting cloudera-scm-agent: [  OK  ]
INFO:clusterdock.topologies.cdh.actions:Waiting for Cloudera Manager server to come online...
INFO:clusterdock.topologies.cdh.actions:Detected Cloudera Manager server after 53.09 seconds.
INFO:clusterdock.topologies.cdh.actions:CM server is now accessible at http://moby:32768
INFO:clusterdock.topologies.cdh.cm:Detected CM API v13.
INFO:clusterdock.topologies.cdh.cm_utils:Adding hosts (Ids: b8a3bb40-06b3-4996-9fe4-419bd5be6c86, 75fd93d3-cc37-4af7-8756-cdbd987c5b21) to Cluster 1 (clusterdock)...
INFO:clusterdock.topologies.cdh.cm_utils:Creating secondary node host template...
INFO:clusterdock.topologies.cdh.cm_utils:Sleeping for 30 seconds to ensure that parcels are activated...
INFO:clusterdock.topologies.cdh.cm_utils:Applying secondary host template...
INFO:clusterdock.topologies.cdh.cm_utils:Updating database configurations...
INFO:clusterdock.topologies.cdh.cm:Updating NameNode references in Hive metastore...
INFO:clusterdock.topologies.cdh.actions:Deploying client configuration...
INFO:clusterdock.topologies.cdh.actions:Starting cluster...
INFO:clusterdock.topologies.cdh.actions:Starting Cloudera Management service...
INFO:clusterdock.topologies.cdh.cm:Beginning service health validation...
INFO:clusterdock.topologies.cdh.cm:Validated that all services started (time: 85.51 s).
INFO:clusterdock.topologies.cdh.actions:We'd love to know what you think of our CDH topology for clusterdock! Please direct any feedback to our community forum at http://tiny.cloudera.com/hadoop-101-forum.
INFO:start_cluster:CDH cluster started in 07 min, 09 sec.
dimaspivak commented 8 years ago
cdh.actions:CM server is now accessible at http://moby:32768

I'll add a line with the URL at the end, too. Good catch. :)

randyzwitch commented 8 years ago

Thanks, I saw the Moby reference...but that doesn't actually open anything (for me, on OSX)

This site can’t be reached

*moby*’s server DNS address could not be found.

   - Search Google for moby 32768
   <https://www.google.com/search?q=moby%2032768>

ERR_NAME_NOT_RESOLVED

On Mon, Aug 8, 2016 at 10:27 AM, Dima Spivak <notifications@github.com>
wrote:

> cdh.actions:CM server is now accessible at http://moby:32768
>
> I'll add a line with the URL at the end, too. Good catch. :)
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/cloudera/clusterdock/issues/6#issuecomment-238254641>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ACooI70JHju5hTEuk9fOT89yfphGS_QWks5qdzzZgaJpZM4JfGCL>
> .
>
dimaspivak commented 8 years ago

Yeah, if using Docker for Mac, Docker runs in a Linux VM, which means another level of indirection for hostnames. Try using localhost as the hostname with that same port, does that show up?

randyzwitch commented 8 years ago

localhost:32768 did it, thanks for humoring me!

One last suggestion: if you are going to print out the URL to the Terminal, maybe also print out that admin:admin is the default u:pw

On Mon, Aug 8, 2016 at 10:38 AM, Dima Spivak notifications@github.com wrote:

Yeah, if using Docker for Mac, Docker runs in a Linux VM, which means another level of indirection for hostnames. Try using localhost as the hostname with that same port, does that show up?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/cloudera/clusterdock/issues/6#issuecomment-238257923, or mute the thread https://github.com/notifications/unsubscribe-auth/ACooIzNnatQLQ5o04xNlyUJBYjYSvHOaks5qdz9XgaJpZM4JfGCL .

dimaspivak commented 8 years ago

Another great suggestion, Randy. You're officially my favorite unwitting beta tester. :)

On Monday, August 8, 2016, Randy Zwitch notifications@github.com wrote:

localhost:32768 did it, thanks for humoring me!

One last suggestion: if you are going to print out the URL to the Terminal, maybe also print out that admin:admin is the default u:pw

On Mon, Aug 8, 2016 at 10:38 AM, Dima Spivak <notifications@github.com javascript:_e(%7B%7D,'cvml','notifications@github.com');> wrote:

Yeah, if using Docker for Mac, Docker runs in a Linux VM, which means another level of indirection for hostnames. Try using localhost as the hostname with that same port, does that show up?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <https://github.com/cloudera/clusterdock/issues/6#issuecomment-238257923 , or mute the thread https://github.com/notifications/unsubscribe-auth/ ACooIzNnatQLQ5o04xNlyUJBYjYSvHOaks5qdz9XgaJpZM4JfGCL .

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/cloudera/clusterdock/issues/6#issuecomment-238259027, or mute the thread https://github.com/notifications/unsubscribe-auth/AFzozMSlwiF4SL-PeeZ3c5yKTNol928Lks5qd0AlgaJpZM4JfGCL .