Getting the below error when starting the docker about fast-data-dev HOT 6 CLOSED

I have given wrong IP. Its up and running now. Thanks for your help @andmarios @Antwnis

from fast-data-dev.

Doesn't fast-data-dev work correctly? It is normal for schema registry and rest proxy to fail a couple times at startup since zookeeper and kafka broker aren't up yet.

Unfortunately supervisor, the tool we use to manage the services running in the container, doesn't provide a way to delay some services. So all services (in this case zookeeper, broker, schema registry and rest proxy) have to start together.

from fast-data-dev.

Hi @nkravi

From this section of the logs it seems that rest-proxy started 100msec before the schema-registry - so the process exited (in the 2nd line).

Then supervisord tried to restart it on the 4th line. So far everything looks OK

Can you paste the entire log starting from the beginning ?

from fast-data-dev.

Here is the entire log
When i visit http://172.32.16.139:3040 I see nothing
docker run --rm -it \

       -p 3181:3181 -p 3040:3040 -p 7081:7081 \
       -p 7082:7082 -p 7083:7083 -p 7092:7092 \
       -e ZK_PORT=3181 -e WEB_PORT=3040 -e REGISTRY_PORT=8081 \
       -e REST_PORT=7082 -e CONNECT_PORT=7083 -e BROKER_PORT=7092 \
       -e ADV_HOST=172.32.16.139 \
       landoop/fast-data-dev

Setting advertised host to 172.32.16.139.
Operating system RAM available is 3637 MiB, which is less than the lowest
recommended of 5120 MiB. Your system performance may be seriously impacted.
Starting services.
This is landoop’s fast-data-dev. Kafka 0.10.1.1, Confluent OSS 3.1.2.
You may visit http://172.32.16.139:3040 in about a minute.
2017-05-02 22:02:49,843 CRIT Supervisor running as root (no user in config file)
2017-05-02 22:02:49,843 WARN No file matches via include "/etc/supervisord.d/*.conf"
2017-05-02 22:02:49,846 INFO supervisord started with pid 5
2017-05-02 22:02:50,848 INFO spawned: 'sample-data' with pid 82
2017-05-02 22:02:50,850 INFO spawned: 'zookeeper' with pid 83
2017-05-02 22:02:50,851 INFO spawned: 'caddy' with pid 84
2017-05-02 22:02:50,853 INFO spawned: 'broker' with pid 85
2017-05-02 22:02:50,854 INFO spawned: 'smoke-tests' with pid 86
2017-05-02 22:02:50,856 INFO spawned: 'connect-distributed' with pid 88
2017-05-02 22:02:50,857 INFO spawned: 'logs-to-kafka' with pid 89
2017-05-02 22:02:50,859 INFO spawned: 'schema-registry' with pid 90
2017-05-02 22:02:50,864 INFO spawned: 'rest-proxy' with pid 91
2017-05-02 22:02:52,124 INFO success: sample-data entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-05-02 22:02:52,124 INFO success: zookeeper entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-05-02 22:02:52,124 INFO success: caddy entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-05-02 22:02:52,124 INFO success: broker entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-05-02 22:02:52,125 INFO success: smoke-tests entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-05-02 22:02:52,125 INFO success: connect-distributed entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-05-02 22:02:52,125 INFO success: logs-to-kafka entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-05-02 22:02:52,125 INFO success: schema-registry entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-05-02 22:02:52,125 INFO success: rest-proxy entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-05-02 22:02:54,814 INFO exited: schema-registry (exit status 1; not expected)
2017-05-02 22:02:54,926 INFO spawned: 'schema-registry' with pid 227
2017-05-02 22:02:55,118 INFO exited: rest-proxy (exit status 1; not expected)
2017-05-02 22:02:55,142 INFO spawned: 'rest-proxy' with pid 259
2017-05-02 22:02:56,312 INFO success: schema-registry entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-05-02 22:02:56,312 INFO success: rest-proxy entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-05-02 22:03:53,759 INFO exited: logs-to-kafka (exit status 0; expected)
2017-05-02 22:05:58,534 INFO exited: smoke-tests (exit status 9; not expected)

from fast-data-dev.

Where does 172.32.16.139 come from? It seems a bit not standard address for docker on Mac, nor Windows. This is where I would start in order to find out why the web interface doesn't open. This part of fast-data-dev should always work.

Also you seem a bit low on RAM, which could affect kafka's operation —but still, the web UI should work.

from fast-data-dev.

Glad you figured it out!

from fast-data-dev.