Hi, 

We are running Graylog2 on  AWS, using Docker, and we are getting "No 
Graylog servers available. Cannot log in" & "0 of 1 nodes connected."

Discovered  Nodes : http://172.17.31.113:12900  VIA http:/127.0.0.1:12900

We are using only one elastic search node,  in shared mode with 
graylog-server (all in one machine).

With  curl -XGET 'http://localhost:9200/_cluster/health?pretty=true'   
using the default elasticsearch port  responds correctly.
{
  "cluster_name" : "graylog2",
  "status" : "yellow",
  "timed_out" : false,
  "number_of_nodes" : 1,
  "number_of_data_nodes" : 1,
  "active_primary_shards" : 4,
  "active_shards" : 4,
  "relocating_shards" : 0,
  "initializing_shards" : 0,
  "unassigned_shards" : 4,
  "delayed_unassigned_shards" : 0,
  "number_of_pending_tasks" : 0,
  "number_of_in_flight_fetch" : 0
}


But when doing curl -XGET 'http://localhost:12900/_cluster/health?pretty=true' 
  Port 12900 as elastic port node (12900) detected form graylog 

curl: (56) Recv failure: Connection reset by peer



When running the docker image didn't bind port 12900, as it is recommended 
only on  "Multi container 
setup". http://docs.graylog.org/en/latest/pages/installation/docker.html


Docker run commend:
 docker run -d --ulimit nofile=1024:64000 -p 443:443 -p 80:9000 -p 
12201:12201 -p 12201:12201/udp -e GRAYLOG_NODE_ID=**** -e     
GRAYLOG_SERVER_SECRET=***** -e GRAYLOG_USERNAME=***** -e 
GRAYLOG_TIMEZONE=Europe/Berlin -e GRAYLOG_RETENTION="--size=3 --indices=10" 
-e ES_MEMORY=2g -e GRAYLOG_PASSWORD=***** -v 
/graylog/data:/var/opt/graylog/data -v /graylog/logs:/var/log/graylog  -v 
/graylog/plugin:/opt/graylog/plugin -v 
/graylog/ca:/opt/graylog/conf/nginx/ca  --name=graylog2 
graylog2/allinone:latest


Why Graylog is looking at 12900 port and not at the default 9200?

Do we need to bind as well port 12900 (-p 12900:12900), even in shared mode?

What else maybe the problem of the error. Actually the error occurred after 
some hours (over night )  of not usage of the web-server, in general 
idleness of graylog.

Thank you very much,
Lefteris,

Error on web/application.log: 

 - [ERROR] - from org.graylog2.restclient.lib.ApiClient in 
servernodes-refresh-0 
API call timed out
java.util.concurrent.TimeoutException: null
        at 
com.ning.http.client.providers.netty.future.NettyResponseFuture.get(NettyResponseFuture.java:159)
 
~[com.ning.async-http-client-1.9.31.jar:na]
        at 
org.graylog2.restclient.lib.ApiClientImpl$ApiRequestBuilder.executeOnAll(ApiClientImpl.java:608)
 
~[org.graylog2.graylog2-rest-client--1.2.2-1.2.2.jar:na]
        at 
org.graylog2.restclient.lib.ServerNodesRefreshService.resolveConfiguredNodes(ServerNodesRefreshService.java:97)
 
[org.graylog2.graylog2-rest-client--1.2.2-1.2.2.jar:na]
        at 
org.graylog2.restclient.lib.ServerNodesRefreshService.access$400(ServerNodesRefreshService.java:42)
 
[org.graylog2.graylog2-rest-client--1.2.2-1.2.2.jar:na]
        at 
org.graylog2.restclient.lib.ServerNodesRefreshService$1.run(ServerNodesRefreshService.java:126)
 
[org.graylog2.graylog2-rest-client--1.2.2-1.2.2.jar:na]
        at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
[na:1.8.0_60]
        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) 
[na:1.8.0_60]
        at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
 
[na:1.8.0_60]
        at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
 
[na:1.8.0_60]
        at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 
[na:1.8.0_60]
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
[na:1.8.0_60]
        at java.lang.Thread.run(Thread.java:745) [na:1.8.0_60]


registry at elasticsearch/graylog2.log :

[2015-11-12 10:18:48,980][WARN ][transport                ] [Air-Walker] 
Received response for a request that has timed out, sent [42535ms] ago, 
timed out [12535ms] ago, action [internal:discovery/zen/fd/ping], node 
[[graylog2-server][YFUaBOwKQFCyaGuhEHNc-w][2df0a8a0d471][inet[/172.17.31.113:9350]]{client=true,
 
data=false, master=false}], id [45622]
[2015-11-12 10:22:34,692][WARN ][transport                ] [Air-Walker] 
Received response for a request that has timed out, sent [41653ms] ago, 
timed out [11640ms] ago, action [internal:discovery/zen/fd/ping], node 
[[graylog2-server][YFUaBOwKQFCyaGuhEHNc-w][2df0a8a0d471][inet[/172.17.31.113:9350]]{client=true,
 
data=false, master=false}], id [45652]
[2015-11-12 10:23:32,779][WARN ][transport                ] [Air-Walker] 
Received response for a request that has timed out, sent [48664ms] ago, 
timed out [18663ms] ago, action [internal:discovery/zen/fd/ping], node 
[[graylog2-server][YFUaBOwKQFCyaGuhEHNc-w][2df0a8a0d471][inet[/172.17.31.113:9350]]{client=true,
 
data=false, master=false}], id [45655]
[2015-11-12 10:24:39,336][WARN ][transport                ] [Air-Walker] 
Received response for a request that has timed out, sent [63709ms] ago, 
timed out [33587ms] ago, action [internal:discovery/zen/fd/ping], node 
[[graylog2-server][YFUaBOwKQFCyaGuhEHNc-w][2df0a8a0d471][inet[/172.17.31.113:9350]]{client=true,
 
data=false, master=false}], id [45657]
[2015-11-12 10:24:46,969][WARN ][transport                ] [Air-Walker] 
Received response for a request that has timed out, sent [41220ms] ago, 
timed out [11145ms] ago, action [internal:discovery/zen/fd/ping], node 
[[graylog2-server][YFUaBOwKQFCyaGuhEHNc-w][2df0a8a0d471][inet[/172.17.31.113:9350]]{client=true,
 
data=false, master=false}], id [45658]
[2015-11-12 10:25:05,861][INFO ][cluster.service          ] [Air-Walker] 
removed 
{[graylog2-server][YFUaBOwKQFCyaGuhEHNc-w][2df0a8a0d471][inet[/172.17.31.113:9350]]{client=true,
 
data=false, master=false},}, reason: 
zen-disco-node_failed([graylog2-server][YFUaBOwKQFCyaGuhEHNc-w][2df0a8a0d471][inet[/172.17.31.113:9350]]{client=true,
 
data=false, master=false}), reason failed to ping, tried [3] times, each 
with maximum [30s] timeout




-- 
You received this message because you are subscribed to the Google Groups 
"Graylog Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/graylog2/47f6125d-168d-4cf8-9155-1128a25e3e03%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to