[graylog2] Re: Load Balancer health check with Big-IP F5

2016-06-08 Thread Stefan
Hi Marty Graylog 2.0.1. We have tls enabled for the REST API. If I try to connect and check the lbstatus using telnet I always get a "Connection closed by foreign host." back. Do you maybe have an idea how to solve this? Thank you and kind regards, Stefan Am Freitag, 15. April 2016 15:04:10

[graylog2] Re: Load Balancer health check with Big-IP F5

2016-04-15 Thread Micha -
Hi Marty, at the moment i just using one Node so i still wasn't place one of our F5 Clusters in front of Graylog. I just tested the monitor via telnet like i always do for new monitors. f5ve]# telnet graylogserver 12900 Trying graylogserver... Connected to graylogserver . Escape character is

[graylog2] Re: Load Balancer health check with Big-IP F5

2016-04-15 Thread Marty
Hi Micha, Totally understand and was configuring the F5 as you've shown. Its just that I don't seem to get an answer (ALIVE), confusing, hence script and curl. Will try again. This method always works for yourself without fail ? Thanks for your help. Cheers, Marty On Thursday, April 14, 2016

[graylog2] Re: Load Balancer health check with Big-IP F5

2016-04-15 Thread Marty
Hi Jochen, Thanks for the clarification (as per rfc). It just seems intermittent, when using echo and piped to nc. I don't always get an answer, via this way. Cheers, Marty On Wednesday, April 13, 2016 at 8:18:49 PM UTC+10, Jochen Schalanda wrote: > > Hi Marty, > > the second CRLF is required

[graylog2] Re: Load Balancer health check with Big-IP F5

2016-04-13 Thread Micha -
Hi Martin, For tthis monitor you dont't need an external Monitor on the F5 Just Configure the monitor like one of that, and it should work AS HTTP/1.0 *Send String:* GET /system/lbstatus HTTP/1.0\r\n\r\n *Receive String:* Alive OR as HTTP/1.1 *Send String:* GET /system/lbstatus

[graylog2] Re: Load Balancer health check with Big-IP F5

2016-04-13 Thread Jochen Schalanda
Hi Marty, the second CRLF is required by the HTTP/1.0 and HTTP/1.1 protocols, so it's not broken but simply as specified (see https://tools.ietf.org/html/rfc7230#section-3 for details). If you really want to use netcat for that stuff instead of a proper HTTP client like curl, you'll have