leader-us
commented
7 years ago homestead docker conainter running error ,sames can't connect cassandra
17-10-2016 22:39:43.367 UTC Error dnscachedresolver.cpp:607: Failed to retrieve record for cassandra: Could not contact DNS servers 17-10-2016 22:40:51.998 UTC Status cassandra_store.cpp:181: Configuring store connection 17-10-2016 22:40:51.998 UTC Status cassandra_store.cpp:182: Hostname: cassandra 17-10-2016 22:40:51.998 UTC Status cassandra_store.cpp:183: Port: 9160 17-10-2016 22:40:51.998 UTC Status cassandra_store.cpp:211: Configuring store worker pool 17-10-2016 22:40:51.998 UTC Status cassandra_store.cpp:212: Threads: 10 17-10-2016 22:40:51.998 UTC Status cassandra_store.cpp:213: Max Queue: 0 17-10-2016 22:40:51.999 UTC Error dnscachedresolver.cpp:607: Failed to retrieve record for cassandra: Could not contact DNS servers 17-10-2016 22:42:01.164 UTC Status cassandra_store.cpp:181: Configuring store connection 17-10-2016 22:42:01.164 UTC Status cassandra_store.cpp:182: Hostname: cassandra 17-10-2016 22:42:01.164 UTC Status cassandra_store.cpp:183: Port: 9160 17-10-2016 22:42:01.164 UTC Status cassandra_store.cpp:211: Configuring store worker pool 17-10-2016 22:42:01.164 UTC Status cassandra_store.cpp:212: Threads: 10 17-10-2016 22:42:01.164 UTC Status cassandra_store.cpp:213: Max Queue: 0 17-10-2016 22:42:01.165 UTC Error dnscachedresolver.cpp:607: Failed to retrieve record for cassandra: Could not contact DNS servers
in container ,can connect it (kuberntes servivce name is cassandra )
root@clearwater-homestead:/# wget cassandra:9160 --2016-10-17 22:42:36-- http://cassandra:9160/ Resolving cassandra (cassandra)... 169.169.193.170 Connecting to cassandra (cassandra)|169.169.193.170|:9160... connected. HTTP request sent, awaiting response... No data received. Retrying.
eleanor-merry
ellis nginx can't be started by supervisord I find clearwater-infrastructure.conf (/etc/supervisor/conf.d/clearwater-infrastructure.conf ) has some problems, clearwater-group can't be started because supervisorctl can't connect supervisord [program:clearwater-infrastructure] command=bash -c '/etc/init.d/clearwater-auto-config-docker start && /etc/init.d/clearwater-infrastructure start && /etc/init.d/clearwater-etcd start && /etc/init.d/clearwater-cluster-manager start && supervisorctl start clearwater-group:_' startsecs=0 root@clearwater-ellis:/# *_supervisorctl unix:///var/run/supervisor.sock refused connection**
this guy (Yossibh) not use supervisorctl to start service ,so all service in supervisor can start ,but can't cotroll start sequnce , https://github.com/Yossibh/clearwater-docker/