Cannot connect to Ambari http://172.17.0.2:8080/api/v1/

[sequenceiq]

Cannot connect to Ambari http://172.17.0.2:8080/api/v1/

[matyix]

Can you send me startup command and the logs of the Docker container. I believe you are applying the server tag?
Did you built it from the Dockerfile, or pulling the image from Docker.io?

Btw, what is the host OS?

[thbeh]

Hi,

This is the commands I have used previously and the same last few days, as
per your blogs/github:

docker run -d -p 8080 -h amb0.mycorp.kom --name ambari-singlenode
sequenceiq/ambari --tag ambari-server=true

AMBARI_IP=$(docker inspect --format "{{.NetworkSettings.IPAddress}}"
ambari-singlenode)

docker run -it --rm sequenceiq/ambari-shell --ambari.host=$AMBARI_IP

The logs:-

2014/08/02 21:17:43 GET /v1.13/containers/json
[efc3c368] +job containers()
[efc3c368] -job containers() = OK (0)
2014/08/02 21:17:58 GET /v1.13/containers/json?all=1
[efc3c368] +job containers()
[efc3c368] -job containers() = OK (0)
2014/08/02 21:17:58 DELETE /v1.13/containers/f9cfe33d308f?force=1
[efc3c368] +job container_delete(f9cfe33d308f)
2014/08/02 21:18:03 Container
f9cfe33d308fdd3811b187930c716e64919ab0766e48cc5cb6e3725c9de7af36 failed to
exit within 5 seconds of SIGTERM - using the force
[efc3c368] +job
release_interface(f9cfe33d308fdd3811b187930c716e64919ab0766e48cc5cb6e3725c9de7af36)
[efc3c368] -job
release_interface(f9cfe33d308fdd3811b187930c716e64919ab0766e48cc5cb6e3725c9de7af36)
= OK (0)
[efc3c368] -job container_delete(f9cfe33d308f) = OK (0)
2014/08/02 21:18:03 DELETE /v1.13/containers/13888281cc63?force=1
[efc3c368] +job container_delete(13888281cc63)
2014/08/02 21:18:08 Container
13888281cc63894fcf832241be646161d37c7a7dd1cf2dfecb58a0edadaa2ffc failed to
exit within 5 seconds of SIGTERM - using the force
[efc3c368] +job
release_interface(13888281cc63894fcf832241be646161d37c7a7dd1cf2dfecb58a0edadaa2ffc)
[efc3c368] -job
release_interface(13888281cc63894fcf832241be646161d37c7a7dd1cf2dfecb58a0edadaa2ffc)
= OK (0)
[efc3c368] -job container_delete(13888281cc63) = OK (0)
2014/08/02 21:18:08 DELETE /v1.13/containers/15ff0021f170?force=1
[efc3c368] +job container_delete(15ff0021f170)
2014/08/02 21:18:13 Container
15ff0021f170984ae09169bbbef50cc009dd7e2db61b535ea9909bcb7c299d48 failed to
exit within 5 seconds of SIGTERM - using the force
[efc3c368] +job
release_interface(15ff0021f170984ae09169bbbef50cc009dd7e2db61b535ea9909bcb7c299d48)
[efc3c368] -job
release_interface(15ff0021f170984ae09169bbbef50cc009dd7e2db61b535ea9909bcb7c299d48)
= OK (0)
[efc3c368] -job container_delete(15ff0021f170) = OK (0)
2014/08/02 21:18:22 GET /v1.13/containers/json
[efc3c368] +job containers()
[efc3c368] -job containers() = OK (0)
2014/08/02 21:18:46 POST /v1.13/containers/create?name=ambari-singlenode
[efc3c368] +job create(ambari-singlenode)
[efc3c368] -job create(ambari-singlenode) = OK (0)
2014/08/02 21:18:46 POST
/v1.13/containers/e72b6d28ad0bc6850a8adda740f7ce86c4cb6e3a1b51f5b6fb45d67671af179a/start
[efc3c368] +job
start(e72b6d28ad0bc6850a8adda740f7ce86c4cb6e3a1b51f5b6fb45d67671af179a)
[efc3c368] +job
allocate_interface(e72b6d28ad0bc6850a8adda740f7ce86c4cb6e3a1b51f5b6fb45d67671af179a)
[efc3c368] -job
allocate_interface(e72b6d28ad0bc6850a8adda740f7ce86c4cb6e3a1b51f5b6fb45d67671af179a)
= OK (0)
[efc3c368] +job
allocate_port(e72b6d28ad0bc6850a8adda740f7ce86c4cb6e3a1b51f5b6fb45d67671af179a)
[efc3c368] -job
allocate_port(e72b6d28ad0bc6850a8adda740f7ce86c4cb6e3a1b51f5b6fb45d67671af179a)
= OK (0)
[efc3c368] -job
start(e72b6d28ad0bc6850a8adda740f7ce86c4cb6e3a1b51f5b6fb45d67671af179a) =
OK (0)
2014/08/02 21:19:02 GET /v1.13/containers/ambari-singlenode/json
[efc3c368] +job container_inspect(ambari-singlenode)
[efc3c368] -job container_inspect(ambari-singlenode) = OK (0)
2014/08/02 21:19:12 POST /v1.13/containers/create
[efc3c368] +job create()
[efc3c368] -job create() = OK (0)
2014/08/02 21:19:12 POST
/v1.13/containers/d6ba5593c01e14aff6925d01219a3681ea08ea66802b86ab465013f924b2a34e/attach?stderr=1&stdin=1&stdout=1&stream=1
[efc3c368] +job
container_inspect(d6ba5593c01e14aff6925d01219a3681ea08ea66802b86ab465013f924b2a34e)
[efc3c368] -job
container_inspect(d6ba5593c01e14aff6925d01219a3681ea08ea66802b86ab465013f924b2a34e)
= OK (0)
[efc3c368] +job
attach(d6ba5593c01e14aff6925d01219a3681ea08ea66802b86ab465013f924b2a34e)
2014/08/02 21:19:12 POST
/v1.13/containers/d6ba5593c01e14aff6925d01219a3681ea08ea66802b86ab465013f924b2a34e/start
[efc3c368] +job
start(d6ba5593c01e14aff6925d01219a3681ea08ea66802b86ab465013f924b2a34e)
[efc3c368] +job
allocate_interface(d6ba5593c01e14aff6925d01219a3681ea08ea66802b86ab465013f924b2a34e)
[efc3c368] -job
allocate_interface(d6ba5593c01e14aff6925d01219a3681ea08ea66802b86ab465013f924b2a34e)
= OK (0)
[efc3c368] -job
start(d6ba5593c01e14aff6925d01219a3681ea08ea66802b86ab465013f924b2a34e) =
OK (0)
2014/08/02 21:19:12 POST
/v1.13/containers/d6ba5593c01e14aff6925d01219a3681ea08ea66802b86ab465013f924b2a34e/resize?h=24&w=80
[efc3c368] +job
resize(d6ba5593c01e14aff6925d01219a3681ea08ea66802b86ab465013f924b2a34e,
24, 80)
[efc3c368] -job
resize(d6ba5593c01e14aff6925d01219a3681ea08ea66802b86ab465013f924b2a34e,
24, 80) = OK (0)
[efc3c368] +job
release_interface(d6ba5593c01e14aff6925d01219a3681ea08ea66802b86ab465013f924b2a34e)
[efc3c368] -job
release_interface(d6ba5593c01e14aff6925d01219a3681ea08ea66802b86ab465013f924b2a34e)
= OK (0)
[error] container.go:522
d6ba5593c01e14aff6925d01219a3681ea08ea66802b86ab465013f924b2a34e: Error
closing terminal: invalid argument
[efc3c368] -job
attach(d6ba5593c01e14aff6925d01219a3681ea08ea66802b86ab465013f924b2a34e) =
OK (0)
2014/08/02 21:19:22 POST
/v1.13/containers/d6ba5593c01e14aff6925d01219a3681ea08ea66802b86ab465013f924b2a34e/wait
[efc3c368] +job
wait(d6ba5593c01e14aff6925d01219a3681ea08ea66802b86ab465013f924b2a34e)
[efc3c368] -job
wait(d6ba5593c01e14aff6925d01219a3681ea08ea66802b86ab465013f924b2a34e) = OK
(0)
2014/08/02 21:19:22 GET
/v1.13/containers/d6ba5593c01e14aff6925d01219a3681ea08ea66802b86ab465013f924b2a34e/json
[efc3c368] +job
container_inspect(d6ba5593c01e14aff6925d01219a3681ea08ea66802b86ab465013f924b2a34e)
[efc3c368] -job
container_inspect(d6ba5593c01e14aff6925d01219a3681ea08ea66802b86ab465013f924b2a34e)
= OK (0)
2014/08/02 21:19:22 DELETE
/v1.13/containers/d6ba5593c01e14aff6925d01219a3681ea08ea66802b86ab465013f924b2a34e?v=1
[efc3c368] +job
container_delete(d6ba5593c01e14aff6925d01219a3681ea08ea66802b86ab465013f924b2a34e)
[efc3c368] -job
container_delete(d6ba5593c01e14aff6925d01219a3681ea08ea66802b86ab465013f924b2a34e)
= OK (0)

On Sat, Aug 2, 2014 at 1:54 PM, Janos Matyas [email protected]
wrote:

Can you send me startup command and the logs of the Docker container. I
believe you are applying the server tag.
Did you built it from the Dockerfile, or pulling the image from Docker.io?

—
Reply to this email directly or view it on GitHub
#6 (comment)
.

[lalyos]

Hi Beh,

I was able to track down the issue.

The Dockerfile contains this line:

RUN ambari-server setup --silent

which should in turn install and initialize postgresql. For some reason, the automated build on 31.aug failed to initialize the db. I was able to fix this, by not changing anything, just hitting the "build" button at : https://registry.hub.docker.com/u/sequenceiq/ambari/

[lalyos]

Make sure you have the latest ambari image:

docker pull sequenceiq/ambari

docker images -q sequenceiq/ambari
293d730a0623

Checking PSQL database

To check that the psql db is initialized you can run the following:

docker run --rm --entrypoint /bin/sh sequenceiq/ambari -c "cat /var/lib/pgsql/data/PG_VERSION"

It should report 8.4