You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 1, 2020. It is now read-only.
I'm trying to run the kafka container on a AWS docker machine, when the container starts it successfully starts zookeeper but fails to start kafka. Here is the console output:
> docker-machine create --driver amazonec2 --amazonec2-access-key $AWS_ACCESS_KEY_ID --amazonec2-secret-key $AWS_SECRET_ACCESS_KEY --amazonec2-vpc-id $VPC_ID --amazonec2-region $REGION aws01
>eval$(docker-machine env aws01)> docker run -p 2181:2181 -p 9092:9092 --env ADVERTISED_HOST=`docker-machine ip \`docker-machine active\`` --env ADVERTISED_PORT=9092 spotify/kafka
/usr/lib/python2.7/dist-packages/supervisor/options.py:296: UserWarning: Supervisord is running as root and it is searching forits configuration filein default locations (including its current working directory); you probably want to specify a "-c" argument specifying an absolute path to a configuration file for improved security.
'Supervisord is running as root and it is searching '
2015-11-20 10:47:03,112 CRIT Supervisor running as root (no user in config file)
2015-11-20 10:47:03,112 WARN Included extra file "/etc/supervisor/conf.d/kafka.conf" during parsing
2015-11-20 10:47:03,112 WARN Included extra file "/etc/supervisor/conf.d/zookeeper.conf" during parsing
2015-11-20 10:47:03,121 INFO RPC interface 'supervisor' initialized
2015-11-20 10:47:03,121 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2015-11-20 10:47:03,122 INFO supervisord started with pid 1
2015-11-20 10:47:04,124 INFO spawned: 'zookeeper' with pid 8
2015-11-20 10:47:04,125 INFO spawned: 'kafka' with pid 9
2015-11-20 10:47:04,171 INFO exited: kafka (exit status 1; not expected)
2015-11-20 10:47:05,172 INFO success: zookeeper entered RUNNING state, process has stayed up for> than 1 seconds (startsecs)
2015-11-20 10:47:05,173 INFO spawned: 'kafka' with pid 37
2015-11-20 10:47:05,196 INFO exited: kafka (exit status 1; not expected)
2015-11-20 10:47:07,200 INFO spawned: 'kafka' with pid 45
2015-11-20 10:47:07,224 INFO exited: kafka (exit status 1; not expected)
2015-11-20 10:47:10,228 INFO spawned: 'kafka' with pid 53
2015-11-20 10:47:10,251 INFO exited: kafka (exit status 1; not expected)
2015-11-20 10:47:11,252 INFO gave up: kafka entered FATAL state, too many start retries too quickly
Any idea what is causing this and how to fix it?
The text was updated successfully, but these errors were encountered:
It sounds like there was not enough memory for the JVM as the docker machine uses by default a t.micro. I had to use a larger instace --amazonec2-instance-type t2.medium.
I'm trying to run the kafka container on a AWS docker machine, when the container starts it successfully starts zookeeper but fails to start kafka. Here is the console output:
Any idea what is causing this and how to fix it?
The text was updated successfully, but these errors were encountered: