fast-data-dev icon indicating copy to clipboard operation
fast-data-dev copied to clipboard

Published 20 hours ago • verified publisher icon lensesio

Can't start zookeeper in docker

Open riveryong opened this issue 7 years ago • 9 comments

windows10, I give 6GB to docker, when I run: docker run --net=host landoop/fast-data-dev it is output:

C:\Users\frank>docker run --net=host landoop/fast-data-dev Starting services. This is Landoop’s fast-data-dev. Kafka 1.0.1-L0 (Landoop's Kafka Distribution). You may visit http://localhost:3030 in about a minute. 2018-07-20 06:27:10,001 CRIT Supervisor is running as root. Privileges were not dropped because no user is specified in the config file. If you intend to run as root, you can set user=root in the config file to avoid this message. 2018-07-20 06:27:10,001 INFO Included extra file "/etc/supervisord.d/01-zookeeper.conf" during parsing 2018-07-20 06:27:10,001 INFO Included extra file "/etc/supervisord.d/02-broker.conf" during parsing 2018-07-20 06:27:10,001 INFO Included extra file "/etc/supervisord.d/03-schema-registry.conf" during parsing 2018-07-20 06:27:10,001 INFO Included extra file "/etc/supervisord.d/04-rest-proxy.conf" during parsing 2018-07-20 06:27:10,001 INFO Included extra file "/etc/supervisord.d/05-connect-distributed.conf" during parsing 2018-07-20 06:27:10,001 INFO Included extra file "/etc/supervisord.d/06-caddy.conf" during parsing 2018-07-20 06:27:10,001 INFO Included extra file "/etc/supervisord.d/07-smoke-tests.conf" during parsing 2018-07-20 06:27:10,001 INFO Included extra file "/etc/supervisord.d/08-logs-to-kafka.conf" during parsing 2018-07-20 06:27:10,001 INFO Included extra file "/etc/supervisord.d/99-supervisord-sample-data.conf" during parsing 2018-07-20 06:27:10,013 INFO RPC interface 'supervisor' initialized 2018-07-20 06:27:10,013 CRIT Server 'unix_http_server' running without any HTTP authentication checking 2018-07-20 06:27:10,013 INFO supervisord started with pid 6 2018-07-20 06:27:11,016 INFO spawned: 'sample-data' with pid 165 2018-07-20 06:27:11,020 INFO spawned: 'zookeeper' with pid 166 2018-07-20 06:27:11,025 INFO spawned: 'caddy' with pid 168 2018-07-20 06:27:11,027 INFO spawned: 'broker' with pid 169 2018-07-20 06:27:11,029 INFO spawned: 'smoke-tests' with pid 170 2018-07-20 06:27:11,031 INFO spawned: 'connect-distributed' with pid 171 2018-07-20 06:27:11,036 INFO spawned: 'logs-to-kafka' with pid 173 2018-07-20 06:27:11,039 INFO spawned: 'schema-registry' with pid 174 2018-07-20 06:27:11,043 INFO spawned: 'rest-proxy' with pid 176 2018-07-20 06:27:12,121 INFO success: sample-data entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-07-20 06:27:12,121 INFO success: zookeeper entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-07-20 06:27:12,121 INFO success: caddy entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-07-20 06:27:12,122 INFO success: broker entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-07-20 06:27:12,122 INFO success: smoke-tests entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-07-20 06:27:12,122 INFO success: connect-distributed entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-07-20 06:27:12,122 INFO success: logs-to-kafka entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-07-20 06:27:12,122 INFO success: schema-registry entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-07-20 06:27:12,122 INFO success: rest-proxy entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-07-20 06:27:17,863 INFO exited: zookeeper (exit status 1; not expected) 2018-07-20 06:27:18,866 INFO spawned: 'zookeeper' with pid 534 2018-07-20 06:27:20,098 INFO success: zookeeper entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-07-20 06:27:22,427 INFO exited: zookeeper (exit status 1; not expected) 2018-07-20 06:27:23,099 INFO spawned: 'zookeeper' with pid 854 2018-07-20 06:27:24,122 INFO success: zookeeper entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-07-20 06:27:28,639 INFO exited: zookeeper (exit status 1; not expected) 2018-07-20 06:27:29,123 INFO spawned: 'zookeeper' with pid 1195 2018-07-20 06:27:30,148 INFO success: zookeeper entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-07-20 06:27:34,616 INFO exited: zookeeper (exit status 1; not expected) 2018-07-20 06:27:35,143 INFO spawned: 'zookeeper' with pid 1532 2018-07-20 06:27:37,108 INFO success: zookeeper entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-07-20 06:27:41,703 INFO exited: zookeeper (exit status 1; not expected) 2018-07-20 06:27:42,706 INFO spawned: 'zookeeper' with pid 1886 2018-07-20 06:27:44,203 INFO success: zookeeper entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-07-20 06:27:48,384 INFO exited: zookeeper (exit status 1; not expected) 2018-07-20 06:27:49,203 INFO spawned: 'zookeeper' with pid 2238 2018-07-20 06:27:50,225 INFO success: zookeeper entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-07-20 06:27:57,693 INFO exited: zookeeper (exit status 1; not expected) 2018-07-20 06:27:58,696 INFO spawned: 'zookeeper' with pid 2620 2018-07-20 06:28:00,230 INFO success: zookeeper entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-07-20 06:28:00,245 INFO exited: zookeeper (exit status 1; not expected) 2018-07-20 06:28:01,149 INFO spawned: 'zookeeper' with pid 2900 2018-07-20 06:28:01,762 INFO exited: zookeeper (exit status 1; not expected) 2018-07-20 06:28:02,768 INFO spawned: 'zookeeper' with pid 3178 2018-07-20 06:28:04,291 INFO success: zookeeper entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-07-20 06:28:11,787 INFO exited: zookeeper (exit status 1; not expected) 2018-07-20 06:28:12,792 INFO spawned: 'zookeeper' with pid 3818 2018-07-20 06:28:14,355 INFO success: zookeeper entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-07-20 06:28:17,377 INFO exited: zookeeper (exit status 1; not expected) 2018-07-20 06:28:17,911 INFO spawned: 'zookeeper' with pid 4131 2018-07-20 06:28:17,916 INFO exited: broker (exit status 1; not expected) 2018-07-20 06:28:18,918 INFO success: zookeeper entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-07-20 06:28:18,924 INFO spawned: 'broker' with pid 4380 2018-07-20 06:28:20,387 INFO success: broker entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-07-20 06:28:20,463 INFO exited: zookeeper (exit status 1; not expected) 2018-07-20 06:28:21,179 INFO spawned: 'zookeeper' with pid 4413 2018-07-20 06:28:22,401 INFO success: zookeeper entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-07-20 06:28:27,752 INFO exited: zookeeper (exit status 1; not expected) 2018-07-20 06:28:28,759 INFO spawned: 'zookeeper' with pid 4775 2018-07-20 06:28:30,429 INFO success: zookeeper entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-07-20 06:28:31,387 INFO exited: zookeeper (exit status 1; not expected) 2018-07-20 06:28:31,432 INFO spawned: 'zookeeper' with pid 5075 2018-07-20 06:28:32,468 INFO success: zookeeper entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-07-20 06:28:38,009 INFO exited: zookeeper (exit status 1; not expected) 2018-07-20 06:28:39,012 INFO spawned: 'zookeeper' with pid 5421 2018-07-20 06:28:40,507 INFO success: zookeeper entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-07-20 06:28:45,596 INFO exited: zookeeper (exit status 1; not expected) 2018-07-20 06:28:46,240 INFO spawned: 'zookeeper' with pid 5789 2018-07-20 06:28:47,243 INFO success: zookeeper entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2018-07-20 06:28:52,848 INFO exited: zookeeper (exit status 1; not expected) 2018-07-20 06:28:53,543 INFO spawned: 'zookeeper' with pid 6142 2018-07-20 06:28:54,572 INFO success: zookeeper entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

do any one has same problem?

riveryong avatar Jul 20 '18 06:07 riveryong

Hi @riveryong . Please check the logs ( zookeeper.log ) to understand why Zookeeper doesn't start. You'll find them at http://localhost:3030/logs/

andmarios avatar Jul 20 '18 09:07 andmarios

I got the same error. Can't connect to localhost:3030 - ERR_CONNECTION_REFUSED

charlesxucheng avatar Jul 30 '18 03:07 charlesxucheng

Hi @charlesxucheng, yours is a different issue. If you are on windows, probably docker didn't expose the port at localhost, so you have to find the address that docker uses.

andmarios avatar Aug 02 '18 05:08 andmarios

don't use --net=host as docker currently has problems with it on windows. try this instead: docker run --rm -p 3030:3030 -p 9092:9092 -p 8081:8081 -p 8083:8083 -p 8082:8082 -p 2181:2181 landoop/fast-data-dev

danield137 avatar Aug 28 '18 11:08 danield137

--net=host does not work for MacOs as well.

aprooks avatar Sep 01 '18 20:09 aprooks

same problem on linux. in addition to the command shown above, you have to change the advertised host, otherwise you won't be able to connect.

docker run --rm -e ADV_HOST=localhost -p 3030:3030 -p 9092:9092 -p 8081:8081 -p 8083:8083 -p 8082:8082 -p 2181:2181 landoop/fast-data-dev

birdayz avatar Oct 11 '18 12:10 birdayz

I had the same problem with Mac OSx 10.14.2 also. As advised by @danield137 and @aprooks I explicitly gave the following ports and it worked like a charm on http://127.0.0.1:3040/

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=127.0.0.1 landoop/fast-data-dev

surysharma avatar Dec 20 '18 23:12 surysharma

I had the same problem with Mac OSx 10.14.2 also. As advised by @danield137 and @aprooks I explicitly gave the following ports and it worked like a charm on http://127.0.0.1:3040/

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=127.0.0.1 landoop/fast-data-dev

This fix worked for me on my Mac OSx 10.12.6 as well. Thanks @surysharma !

joetortorelli avatar Jul 28 '19 04:07 joetortorelli

I had the same problem with Mac OSx 10.14.2 also. As advised by @danield137 and @aprooks I explicitly gave the following ports and it worked like a charm on http://127.0.0.1:3040/

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=127.0.0.1 landoop/fast-data-dev

I got the same issue, but for schema-registry to run lensesio/box, it's weird, everything was ok yesterday

2019-12-25 06:50:39,867 INFO exited: schema-registry (exit status 1; not expected) 2019-12-25 06:50:40,306 INFO spawned: 'schema-registry' with pid 1330 2019-12-25 06:50:41,463 INFO success: schema-registry entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

then I had to add -e REGISTRY_PORT=8081 -e BROKER_PORT=7092 to my command docker run -e ADV_HOST=127.0.0.1 -e EULA="https://dl.lenses.io/d/?id=xxx" --rm -p 3030:3030 -p 9092:9092 -p 2181:2181 -p 8081:8081 -e REGISTRY_PORT=8081 -e BROKER_PORT=7092 lensesio/box

phoenixnghi avatar Dec 25 '19 06:12 phoenixnghi