2017-06-06 68 views
0

我在GCE上使用ELK堆栈。一切正常运行。但后来我安装了NGINX,后来卸载了它。在此之后,Kibana无法启动NGINX后启动。Kibana 4.6.x无法在Google计算引擎上启动

Elasticsearch版本:2.4.5 Kibana版本:4.6

Kibana标准输出日志:

{"type":"log","@timestamp":"2017-06-06T08:13:06Z","tags":["status","plugin:[email protected]","info"],"pid":364,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"} {"type":"log","@timestamp":"2017-06-06T08:13:07Z","tags":["status","plugin:[email protected]","info"],"pid":364,"state":"yellow","message":"Status changed from uninitialized to yellow - Waiting for Elasticsearch","prevState":"uninitialized","prevMsg":"uninitialized"} {"type":"log","@timestamp":"2017-06-06T08:13:07Z","tags":["status","plugin:[email protected]","info"],"pid":364,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"} {"type":"log","@timestamp":"2017-06-06T08:13:07Z","tags":["status","plugin:[email protected]","info"],"pid":364,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"} {"type":"log","@timestamp":"2017-06-06T08:13:07Z","tags":["status","plugin:[email protected]","info"],"pid":364,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"} {"type":"log","@timestamp":"2017-06-06T08:13:07Z","tags":["status","plugin:[email protected]","info"],"pid":364,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"} {"type":"log","@timestamp":"2017-06-06T08:13:07Z","tags":["status","plugin:[email protected]","info"],"pid":364,"state":"green","message":"Status changed from yellow to green - Kibana index ready","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"} {"type":"log","@timestamp":"2017-06-06T08:13:07Z","tags":["status","plugin:[email protected]","info"],"pid":364,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"} {"type":"log","@timestamp":"2017-06-06T08:13:07Z","tags":["status","plugin:[email protected]","info"],"pid":364,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"} {"type":"log","@timestamp":"2017-06-06T08:13:07Z","tags":["fatal"],"pid":364,"level":"fatal","message":"listen EADDRNOTAVAIL 104.155.222.239:5601","error":{"message":"listen EADDRNOTAVAIL 104.155.222.239:5601","name":"Error","stack":"Error: listen EADDRNOTAVAIL 104.155.222.239:5601\n at Object.exports._errnoException (util.js:1026:11)\n at exports._exceptionWithHostPort (util.js:1049:20)\n at Server._listen2 (net.js:1244:19)\n at listen (net.js:1293:10)\n at net.js:1403:9\n at _combinedTickCallback (internal/process/next_tick.js:77:11)\n at process._tickCallback (internal/process/next_tick.js:98:9)","code":"EADDRNOTAVAIL"}}

没有在端口5601上运行,它是由防火墙。

回答

0

根据日志中的最后几条消息,它看起来像Kibana试图监听以下IP/PORT组合104.155.222.239:5601,这就是错误代码为EADDRNOTAVAIL的原因。

既然你提供非常少量的信息,这些东西你可以验证:

  1. 验证IP地址104.155.222.239是实例的IP地址。这看起来像一个公共IP地址。如果您使用的是短暂的公共(即外部)IP地址,请注意,地址可能会在实例重新启动之间发生变化。您可能必须从Google Compute Engine获取静态IP地址以避免此问题,或正确确定外部IP地址并将其传递到您的程序。

  2. 确认没有进程在端口5601上侦听。

您可以运行以下命令打印监听端口上的所有进程:

lsof -i:26625 
相关问题