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 at 12:34:49 AM UTC+10, Micha - wrote:
>
> 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 HTTP/1.1\r\nHost: dummy\r\n\r\n
>
> *Receive String:*
> Alive 
>
>
> Regards
> Micha
>
> Am Mittwoch, 13. April 2016 01:38:35 UTC+2 schrieb Marty:
>>
>> Hi Folks,
>>
>> Graylog V1.3.4
>>
>> Just wondering if anyone has integrated the Graylog LB state into the F5 
>> native http health check.
>> I can't get this to work when sending:
>>
>> GET /system/lbstatus HTTP/1.1
>>
>>
>> From the command line (using netcat) on the graylog node, this also 
>> fails. Just get a newline (no output).
>>
>> $ echo -e "GET /system/lbstatus HTTP/1.1\r\n" | nc 127.0.0.1 12900
>>
>> Using nc natively is OK, as seen below. Need to send <cr> twice, as shown.
>>
>> $ nc 127.0.0.1 12900
>> GET /system/lbstatus HTTP/1.1<cr>
>> <cr>
>> HTTP/1.1 200 OK
>> Content-Type: text/plain
>> X-Graylog-Node-ID: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxx
>> X-Runtime-Microseconds: 240 
>> Transfer-Encoding: chunked 
>>  
>> 5
>> ALIVE 
>> 0 
>> <ctrl c>
>>
>> Using curl is fine:
>>
>> S curl -w '\n' http://127.0.0.1:12900/system/lbstatus
>> ALIVE
>>
>> I got around this on the F5, by using curl with an external script.
>>
>> Just wondering if there is an issue or I'm doing something incorrect.
>>
>> Cheers,
>> Martin
>>
>

-- 
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/665163bf-84a8-4088-87ca-6b18f29905cd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to