'Kafka broker fails inside Docker container without meaningful logs
When I launch Docker container with Kafka broker it fails sometimes, but I can't understand by logs what exactly happens, logs always are:
# docker-compose up broker-1
zookeeper-1 is up-to-date
Starting broker-1 ... done
Attaching to broker-1
broker-1 | ===> User
broker-1 | uid=1000(appuser) gid=1000(appuser) groups=1000(appuser)
broker-1 | ===> Configuring ...
broker-1 | ===> Running preflight checks ...
broker-1 | ===> Check if /var/lib/kafka/data is writable ...
broker-1 | ===> Check if Zookeeper is healthy ...
broker-1 | SLF4J: Class path contains multiple SLF4J bindings.
broker-1 | SLF4J: Found binding in [jar:file:/usr/share/java/cp-base-new/slf4j-log4j12-1.7.30.jar!/org/slf4j/impl/StaticLoggerBinder.class]
broker-1 | SLF4J: Found binding in [jar:file:/usr/share/java/cp-base-new/slf4j-simple-1.7.30.jar!/org/slf4j/impl/StaticLoggerBinder.class]
broker-1 | SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
broker-1 | SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
broker-1 | log4j:WARN No appenders could be found for logger (io.confluent.admin.utils.cli.ZookeeperReadyCommand).
broker-1 | log4j:WARN Please initialize the log4j system properly.
broker-1 | log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
broker-1 exited with code 1
So I have no idea where to read why it fails.
Also I had such problem with Kafka REST Proxy before and rason was misspell in config - put ':' instead '.' in IP address, something like '192.168.1:2:80'- that was the reason (fixed ofc after re-reading configs a lot), but logs was similar and unclear - just exit with code 1 and no meaningful reason.
Any ideas how to get real reason of failure in the logs?
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
Solution | Source |
---|