Hi Jeff,
you're using the same transport address for the Graylog REST API on all 3
Graylog nodes. Is this intentional? I'm asking because that won't work in
the long run as Graylog nodes need to be able to communicate with each
other via the Graylog REST API and the announced transport address.
Cheers,
Jochen
On Friday, 13 May 2016 22:53:07 UTC+2, Jeff McCombs wrote:
>
> So here's a question.. looking at the node output from tokred vs mine..
>
> When you have a cluster of Graylog servers behind a load balancer.. do you
> configure the API transport address to the cluster IP, or the individual
> nodes? Could this be the cause of the following errors I'm also seeing?
>
> 2016-05-13T13:43:27.749-07:00 WARN [ProxiedResource] Node
> <3116ac6b-604f-4436-955c-1458cb489415> not found while trying to call
> org.graylog2.shared.rest.resources.system.RemoteMetricsResource on it.
> 2016-05-13T13:46:58.766-07:00 WARN [ProxiedResource] Node
> <3116ac6b-604f-4436-955c-1458cb489415> not found while trying to call
> org.graylog2.shared.rest.resources.system.RemoteMetricsResource on it.
> 2016-05-13T13:49:14.735-07:00 WARN [ProxiedResource] Node
> <3116ac6b-604f-4436-955c-1458cb489415> not found while trying to call
> org.graylog2.shared.rest.resources.system.RemoteMetricsResource on it.
>
> On Friday, May 13, 2016 at 1:50:17 PM UTC-7, Jeff McCombs wrote:
>>
>> Hi Jochen,
>>
>> I see the records for the nodes:
>>
>> graylog:PRIMARY> db.nodes.find()
>> { "_id" : ObjectId("57363bab05ee16689e192953"), "is_master" : false,
>> "hostname" : "gray01somewhere.com", "last_seen" : 1463172221,
>> "transport_address" : "http://graylog.somewhere.com:12900/";, "type" :
>> "SERVER", "node_id" : "00ac0ad1-b96f-46c0-a2bc-bc9e7a90777f" }
>> { "_id" : ObjectId("57363c0889479f6906e17de9"), "is_master" : false,
>> "hostname" : "gray02.somewhere.com", "last_seen" : 1463172221,
>> "transport_address" : "http://graylog.somewhere.com:12900/";, "type" :
>> "SERVER", "node_id" : "8536ee95-b9c7-4553-9022-d997da315755" }
>> { "_id" : ObjectId("57363c79b2d6491223d87222"), "is_master" : true,
>> "hostname" : "gray00.somewhere.com", "last_seen" : 1463172220,
>> "transport_address" : "http://graylog.somewhere.com:12900/";, "type" :
>> "SERVER", "node_id" : "3116ac6b-604f-4436-955c-1458cb489415" }
>>
>> Interestingly, when I shut down all but the master, it continues to spit
>> errors:
>>
>> /var/log/graylog-server/server.log
>> 2016-05-13T13:47:06.662-07:00 WARN [NodePingThread] Did not find meta
>> info of this node. Re-registering.
>> 2016-05-13T13:47:32.639-07:00 WARN [NodePingThread] Did not find meta
>> info of this node. Re-registering.
>>
>> mongo nodes query:
>> graylog:PRIMARY> db.nodes.find()
>> { "_id" : ObjectId("57363d64b2d6491223d87339"), "is_master" : true,
>> "hostname" : "gray00.somewhere.com", "last_seen" : 1463172464,
>> "transport_address" : "http://graylog.somewhere.com:12900/";, "type" :
>> "SERVER", "node_id" : "3116ac6b-604f-4436-955c-1458cb489415" }
>>
>> Thoughts?
>>
>> On Friday, May 13, 2016 at 2:16:17 AM UTC-7, Jochen Schalanda wrote:
>>>
>>> Hi Jeff,
>>>
>>> please check the "nodes" collection in MongoDB and that it contains
>>> valid node descriptors while Graylog is running.
>>>
>>> Cheers,
>>> Jochen
>>>
>>
--
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/19058234-385a-4282-a1d5-8bf800b5890a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
