[graylog2] Re: 'did not find meta info for this node' error, but not timesync related?

2016-05-17 Thread Jeff McCombs
red elasticsearch configs (up to 18G instead of 2G) cleared the issue. On Thursday, May 12, 2016 at 1:17:23 PM UTC-7, Jeff McCombs wrote: > > Hi gang, > > > I'm running into a strange problem where my graylog nodes are > complaining about not being able to find their meta info: &

Re: [graylog2] Re: 'did not find meta info for this node' error, but not timesync related?

2016-05-17 Thread Jeff McCombs
("573b6dbfb2d64909218a56b8"), "is_master" : false, "hostname" : "gray00.somewhere.com", "last_seen" : 1463512537, "transport_address" : "http://10.201.137.208:12900/;, "type" : "SERVER", "node_id" : &q

Re: [graylog2] Re: 'did not find meta info for this node' error, but not timesync related?

2016-05-17 Thread Jeff McCombs
iguring_webif.html#configuration-options). > > The rest_listen_uri (or rest_transport_uri) should always be an address > which the Graylog nodes in a given cluster can access. > > Cheers, > Jochen > > On Tuesday, 17 May 2016 17:49:54 UTC+2, Jeff McCombs wrote: >> >&g

Re: [graylog2] Re: 'did not find meta info for this node' error, but not timesync related?

2016-05-17 Thread Jeff McCombs
e 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 a

[graylog2] Re: 'did not find meta info for this node' error, but not timesync related?

2016-05-13 Thread Jeff McCombs
oteMetricsResource 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"

[graylog2] Re: 'did not find meta info for this node' error, but not timesync related?

2016-05-13 Thread Jeff McCombs
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",

[graylog2] 3-node cluster, strangeness "did not find meta info" and webUI oddities

2016-05-13 Thread Jeff McCombs
Hi gang, I'm running into a strange problem where my graylog nodes are complaining about not being able to find their meta info: 2016-05-12T11:50:09.691-07:00 WARN [NodePingThread] Did not find meta info of this node. Re-registering. 2016-05-12T11:50:12.878-07:00 WARN [NodePingThread] Did

[graylog2] "did not find meta info of this node." error

2016-05-13 Thread Jeff McCombs
I'd be grateful if anyone could help point me in the right direction for this... Here's the issue: I've got a 3-node setup sitting behind an F5 as a POC... After about 5-10 minutes of all three nodes up and running, I start to see occasional "blips" in the web UI and the following entries in

[graylog2] 'did not find meta info for this node' error, but not timesync related?

2016-05-12 Thread Jeff McCombs
Hi gang, I'm running into a strange problem where my graylog nodes are complaining about not being able to find their meta info: 2016-05-12T11:50:09.691-07:00 WARN [NodePingThread] Did not find meta info of this node. Re-registering. 2016-05-12T11:50:12.878-07:00 WARN [NodePingThread]