排除DCHQ主机故障

时间:2016-01-29 21:38:38

标签: containers

我已经运行DCHQ.io(On-Prem)几个月了,没有任何重大问题。

My Container Hosts环境如下所示:

DCHQ-VM-主机
RAM:14gb / CPU 4 / 100gb存储
10.21.38.165
host0 这是DCHQ所在的地方

多克尔-VM-1
RAM:8gb / CPU 2
10.21.36.201
主机1
托管LB容器的地方

多克尔-金属-2
RAM 96gb / CPU 12
10.21.39.71
主机2
托管APP容器的地方

多克尔 - 金属 - 4
RAM 96gb / CPU 12
10.21.38.170
主机4
托管数据库容器的地方

今天,在尝试为工作中的POC部署 3层Java(ApacheHTTP - Tomcat - MySQL)应用程序模板时,host-4已脱机。

几天前,我将host-1从BM计算机转换为VM。因此,我从DCHQ中删除了该主机,并使用相同的名称(host-1)将其添加回来,但这次是作为不同ESX服务器上的VM。不确定这是否与host-4有关,抛出下面的错误。因此,不能部署涉及host-4的模板,因此我将使用host-1和host-2进行部署。

我尝试重新启动主机-4,在DCHQ UI中停用/激活主机-4并在主机4上重新启动代理但无效。

我的最后一招是在主机4上删除并重新安装客户端,但我想先在此处发布。我也通过电子邮件发送DCHQ支持这个问题。

DCHQ日志显示以下错误:

2016-01-29 15:56:31.026  INFO 1217 --- [pool-3-thread-2] c.d.a.o.impl.ImagePullQueueProcessor     : Processing pull req
2016-01-29 15:56:31.028  INFO 1217 --- [pool-3-thread-2] c.d.a.o.impl.TemplateOperationsImpl      : Received pull request for image [mysql:latest] registry [null]
2016-01-29 15:56:31.028  INFO 1217 --- [pool-3-thread-2] c.d.a.o.impl.DockerClientBuilderUtil     : Using public repo since username [null] or password is empty
2016-01-29 15:56:31.043 ERROR 1217 --- [pool-15-thread-1] c.g.d.core.async.ResultCallbackTemplate  : Error during callback

org.apache.http.conn.HttpHostConnectException: Connect to 127.0.0.1:10624 [/127.0.0.1] failed: Connection refused
        at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:151)
        at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:353)
        at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:380)
        at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236)
        at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:184)
        at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:88)
        at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110)
        at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
        at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:71)
        at com.github.dockerjava.jaxrs.connector.ApacheConnector.apply(ApacheConnector.java:443)
        at org.glassfish.jersey.client.ClientRuntime.invoke(ClientRuntime.java:246)
        at org.glassfish.jersey.client.JerseyInvocation$2.call(JerseyInvocation.java:683)
        at org.glassfish.jersey.internal.Errors.process(Errors.java:315)
        at org.glassfish.jersey.internal.Errors.process(Errors.java:297)
        at org.glassfish.jersey.internal.Errors.process(Errors.java:228)
        at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:424)
        at org.glassfish.jersey.client.JerseyInvocation.invoke(JerseyInvocation.java:679)
        at org.glassfish.jersey.client.JerseyInvocation$Builder.method(JerseyInvocation.java:435)
        at org.glassfish.jersey.client.JerseyInvocation$Builder.post(JerseyInvocation.java:338)
        at com.github.dockerjava.jaxrs.async.POSTCallbackNotifier.response(POSTCallbackNotifier.java:29)
        at com.github.dockerjava.jaxrs.async.AbstractCallbackNotifier.call(AbstractCallbackNotifier.java:45)
        at com.github.dockerjava.jaxrs.async.AbstractCallbackNotifier.call(AbstractCallbackNotifier.java:22)
        at java.util.concurrent.FutureTask.run(FutureTask.java:262)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run(Thread.java:745)
Caused by: java.net.ConnectException: Connection refused
        at java.net.PlainSocketImpl.socketConnect(Native Method)
        at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
        at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
        at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
        at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
        at java.net.Socket.connect(Socket.java:579)
        at org.apache.http.conn.socket.PlainConnectionSocketFactory.connectSocket(PlainConnectionSocketFactory.java:74)
        at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:134)
        ... 25 common frames omitted

2016-01-29 15:56:31.044 ERROR 1217 --- [pool-3-thread-2] c.d.a.o.impl.TemplateOperationsImpl      : Error pulling image [mysql] response logs []
2016-01-29 15:56:31.046  INFO 1217 --- [pool-3-thread-2] c.d.a.o.impl.ImagePullQueueProcessor     : Finished processing pull req
2016-01-29 15:58:39.687  WARN 1217 --- [pool-3-thread-1] c.d.a.o.impl.SysInfoMonitorService       : org.apache.http.conn.HttpHostConnectException: Connect to 127.0.0.1:10624 [/127.0.0.1] failed: Connection refused
2016-01-29 15:58:39.688 ERROR 1217 --- [pool-3-thread-2] c.d.a.o.impl.MachineOperationsImpl       : org.apache.http.conn.HttpHostConnectException: Connect to 127.0.0.1:10624 [/127.0.0.1] failed: Connection refused

提前谢谢你,

1 个答案:

答案 0 :(得分:0)

感谢您报告此问题。请随时在我们的问题跟踪器上报告此事。 https://github.com/dchqinc/dchq-on-premise-issue-tracker/issues

请确保application.properties文件中的信息未更改。确保服务器密钥与DCHQ UI为host-4显示的内容相匹配。

   vi /opt/dchq/config/application.properties

然后您可以重新启动代理:

   service dchq stop
   ps -ef | grep dchq
   ## forcefully kill any DCHQ process that may not have stopped otherwise using kill -9
   service dchq start

最后 - 你能否从UI测试连接?这将有助于我们缩小问题范围。

有关部署Docker Compose应用程序的任何帮助,请参阅我们的文档:http://dchq.co/docker-compose.html