Support Questions

Find answers, ask questions, and share your expertise
Announcements
Celebrating as our community reaches 100,000 members! Thank you!

Cloudbreak install Mac OS

avatar

I've installed Cloudbreak locally on my Mac. cbd doctor looks good, the install went without a hitch, however the UI never loads. The only error i'm seeing in the logs is:

periscope_1 | 2015-10-16 18:11:30,020 [getThreadPoolExecutorFactoryBean-14] logExceptions:144 WARN o.h.e.j.s.SqlExceptionHelper - SQL Error: 0, SQLState: 08001

ambassador_1 | 2015/10/16 18:11:30 dns: read udp 127.0.0.1:53: connection refused

periscope_1 | 2015-10-16 18:11:30,020 [getThreadPoolExecutorFactoryBean-14]

logExceptions:146 ERROR o.h.e.j.s.SqlExceptionHelper - The connection attempt failed.

The only other thing I noticed is that the cbreak_ambassadorips_1 container is not running. It's state is Exit 0. Could this be an ip issue? I'm using my loopback (127.0.0.1) for the public and private ips in my Profile. Should it be a different setting perhaps?

I've also tried starting the container dbs too but that didn't change anything (cbd startdb).

Thanks in advance!

1 ACCEPTED SOLUTION

avatar
New Contributor

127.0.0.1 is not gonna work for PUBLIC_IP.

Please use `cbd init` to generate the initial Profile. Which will figure out the correct boot2docker ip.

So this is what you should have in your Profile:

export PUBLIC_IP=192.168.59.103

The output of `boot2docker ip` is **192.168.59.103** unless you have a non-standard boo2docker. So use this for PUBLIC_IP, (PRIVATE_IP can be removed from Profile

After changing the Profile, configuration files has to be generated again:

cbd regenerate

Now you can restart the containers:

cbd start

After a couple of minutes you can open the browser and log in, url and credential can be displayed:

cbd login

View solution in original post

4 REPLIES 4

avatar
New Contributor

I would try: cbd update && cbd doctor && cbd start

Then, you should be able to go to: http://192.168.59.103:3000

Credentials can be found via the following command: cbd env show|grep "UAA_DEFAULT_USER_PW\|UAA_DEFAULT_USER_EMAIL"

avatar
New Contributor

127.0.0.1 is not gonna work for PUBLIC_IP.

Please use `cbd init` to generate the initial Profile. Which will figure out the correct boot2docker ip.

So this is what you should have in your Profile:

export PUBLIC_IP=192.168.59.103

The output of `boot2docker ip` is **192.168.59.103** unless you have a non-standard boo2docker. So use this for PUBLIC_IP, (PRIVATE_IP can be removed from Profile

After changing the Profile, configuration files has to be generated again:

cbd regenerate

Now you can restart the containers:

cbd start

After a couple of minutes you can open the browser and log in, url and credential can be displayed:

cbd login

avatar

@lpapp@hortonworks.com

Thanks! The UI is now up on the public ip change but now I'm getting "Client cannot access resource server" when I try to login. The ambassadorips docker image still has a status of Exit 0 and has these errors:

ambassador_1 | 2015/10/20 00:53:10 dns: read udp 127.0.0.1:53: connection refused ambassador_1 | 2015/10/20 00:53:10 No backends! Closing the connection

Any other thoughts? I didn't see anything else running on port 53. Turning off the firewall didn't help either.

avatar

Reinstalled with 1.0.0 and it seemed to work