2017-06-06 81 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 
相關問題