ChristianKniep
commented
8 years ago Hey Rasheed,
the zkui is not autostarted, https://github.com/qnib/docker-zkui/blob/master/etc/supervisord.d/zkui.ini#L4 but waits for zookeeper to become ready: https://github.com/qnib/docker-zkui/blob/master/opt/qnib/zkui/bin/start_zookeeper-update.sh#L15
I updated the repository to provide a docker-compose.yml file.
I beefed up the documentation: https://github.com/qnib/docker-zkui
Hey,
I ran the image on a container host (CentOS) - it did not complain about anything, as seen on docker logs. But I don't see anything listening on port 9090 as documented. Any idea?
Below is "netstat -an" output from the container:
Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 0.0.0.0:514 0.0.0.0:* LISTEN tcp6 0 0 :::514 :::* LISTEN tcp6 0 0 :::8301 :::* LISTEN tcp6 0 0 :::8400 :::* LISTEN tcp6 0 0 :::8500 :::* LISTEN tcp6 0 0 :::53 :::* LISTEN tcp6 0 0 ::1:8500 ::1:46277 ESTABLISHED tcp6 0 0 ::1:8500 ::1:46278 ESTABLISHED tcp6 0 0 ::1:46278 ::1:8500 ESTABLISHED tcp6 0 0 ::1:46277 ::1:8500 ESTABLISHED udp 0 0 0.0.0.0:514 0.0.0.0: udp6 0 0 :::514 ::: udp6 0 0 :::53 ::: udp6 0 0 :::8301 ::: Active UNIX domain sockets (servers and established) Proto RefCnt Flags Type State I-Node Path unix 2 [ ACC ] STREAM LISTENING 70981 /var/tmp/supervisor.sock.10 unix 3 [ ] DGRAM 71070 /dev/log unix 2 [ ] DGRAM 71322
Below is the docker logs output:
2015-11-13 17:29:25,682 CRIT Supervisor running as root (no user in config file) 2015-11-13 17:29:25,682 WARN Included extra file "/etc/supervisord.d/rsyslog_conf.ini" during parsing 2015-11-13 17:29:25,682 WARN Included extra file "/etc/supervisord.d/rsyslog.ini" during parsing 2015-11-13 17:29:25,682 WARN Included extra file "/etc/supervisord.d/zkui.ini" during parsing 2015-11-13 17:29:25,682 WARN Included extra file "/etc/supervisord.d/watchpsutil.ini" during parsing 2015-11-13 17:29:25,682 WARN Included extra file "/etc/supervisord.d/zkui_update.ini" during parsing 2015-11-13 17:29:25,682 WARN Included extra file "/etc/supervisord.d/diamond.ini" during parsing 2015-11-13 17:29:25,682 WARN Included extra file "/etc/supervisord.d/consul.ini" during parsing 2015-11-13 17:29:25,732 INFO RPC interface 'supervisor' initialized 2015-11-13 17:29:25,732 CRIT Server 'unix_http_server' running without any HTTP authentication checking 2015-11-13 17:29:25,732 INFO supervisord started with pid 10 2015-11-13 17:29:26,739 INFO spawned: 'diamond' with pid 13 2015-11-13 17:29:26,750 INFO spawned: 'zkui-update' with pid 14 2015-11-13 17:29:26,757 INFO spawned: 'consul' with pid 16 2015-11-13 17:29:26,760 INFO spawned: 'rsyslog-conf' with pid 17 2015-11-13 17:29:26,767 INFO spawned: 'rsyslog' with pid 18 2015-11-13 17:29:26,769 INFO spawned: 'watchpsutil' with pid 19 2015-11-13 17:29:26,778 INFO success: diamond entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2015-11-13 17:29:27,814 INFO success: zkui-update entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2015-11-13 17:29:27,814 INFO success: rsyslog entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2015-11-13 17:29:27,814 INFO success: watchpsutil entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2015-11-13 17:29:27,819 INFO exited: diamond (exit status 0; expected) 2015-11-13 17:29:31,942 INFO success: consul entered RUNNING state, process has stayed up for > than 5 seconds (startsecs) 2015-11-13 17:29:41,946 INFO success: rsyslog-conf entered RUNNING state, process has stayed up for > than 15 seconds (startsecs)
How to get it running as intended?
Thanks, Rasheed