Mailing List Archive

Varnish failing to detect valid probe page
I am having a problem with Varnish 3.x probe page from a SpringBoot application (1.4). Varnish is failing to detect the probe page (returns 503 SERVICE NOT AVAILABLE) and consequently fails to route.
When I manually ping the probe URL, it works fine, but Varnish is flagging the probe page as being down.
Removing the probe page, everything works fine.
Pointing to a static probe page (my.css) or any other static or dynamic URL fails.
Looking at the logs, the response header looks like this:
HTTP/1.1 200
Content-Type: text/plain;charset=utf-8
Content-Length: 72
Date: Wed, 01 Feb 2017 15:20:48 GMT
Proxy-Connection: Keep-Alive
Connection: Keep-Alive

Comparing this to other working (non Spring Boot) applications, the only difference is that the working applications have an OK after the response, and the bad ones don't: HTTP/1.1 200 OK Does that mean anything?
For example, here is a good one:
HTTP/1.1 200 OK
Date: Wed, 01 Feb 2017 14:04:18 GMT
Last-Modified: Fri, 11 Nov 2016 22:00:02 GMT
Content-Type: text/css
Content-Length: 129
Server: Jetty(9.3.z-SNAPSHOT)
Proxy-Connection: Keep-Alive
Connection: Keep-Alive

Not sure where else to look! Any clues?

Victor Grazi

Desk: +1-212-298-4445 (Internal: 74445)
Mobile: +1-917-251-1247
Blackberry Phone: +1-347-726-0338
victor.grazi@nomura.com<mailto:victor.grazi@nomura.com>

NOMURA – GM/FID Core IT
Worldwide Plaza - 8th Floor
309 West 49th Street (8th Ave)
New York, NY 10019





PLEASE READ: This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please delete it and all copies from your system, destroy any hard copies and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Nomura Holding America Inc., Nomura Securities International, Inc, and their respective subsidiaries each reserve the right to monitor all e-mail communications through its networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorized to state the views of such entity. Unless otherwise stated, any pricing information in this message is indicative only, is subject to change and does not constitute an offer to deal at any price quoted. Any reference to the terms of executed transactions should be treated as preliminary only and subject to our formal written confirmation.
Re: Varnish failing to detect valid probe page [ In reply to ]
You found the issue:
https://github.com/varnishcache/varnish-cache/issues/2069

This is "fixed" in master. But maybe you can fix your backend?

--
Guillaume Quintard

--
Guillaume Quintard

On Wed, Feb 1, 2017 at 6:22 PM, <Victor.Grazi@nomura.com> wrote:

> I am having a problem with Varnish 3.x probe page from a SpringBoot
> application (1.4). Varnish is failing to detect the probe page (returns 503
> SERVICE NOT AVAILABLE) and consequently fails to route.
>
> When I manually ping the probe URL, it works fine, but Varnish is flagging
> the probe page as being down.
>
> Removing the probe page, everything works fine.
>
> Pointing to a static probe page (my.css) or any other static or dynamic
> URL fails.
>
> Looking at the logs, the response header looks like this:
>
> HTTP/1.1 200
>
> Content-Type: text/plain;charset=utf-8
>
> Content-Length: 72
>
> Date: Wed, 01 Feb 2017 15:20:48 GMT
>
> Proxy-Connection: Keep-Alive
>
> Connection: Keep-Alive
>
>
>
> Comparing this to other working (non Spring Boot) applications, the only
> difference is that the working applications have an OK after the response,
> and the bad ones don't: HTTP/1.1 200 OK Does that mean anything?
>
> For example, here is a good one:
>
> HTTP/1.1 200 OK
>
> Date: Wed, 01 Feb 2017 14:04:18 GMT
>
> Last-Modified: Fri, 11 Nov 2016 22:00:02 GMT
>
> Content-Type: text/css
>
> Content-Length: 129
>
> Server: Jetty(9.3.z-SNAPSHOT)
>
> Proxy-Connection: Keep-Alive
>
> Connection: Keep-Alive
>
>
>
> Not sure where else to look! Any clues?
>
>
>
> Victor Grazi
>
>
>
> Desk: +1-212-298-4445 <(212)%20298-4445> (Internal: 74445)
>
> Mobile: +1-917-251-1247 <(917)%20251-1247>
>
> Blackberry Phone: +1-347-726-0338 <(347)%20726-0338>
>
> victor.grazi@nomura.com
>
>
>
> *NOMURA – GM/FID Core IT*
>
> Worldwide Plaza - 8th Floor
> 309 West 49th Street (8th Ave)
>
> New York, NY 10019
>
>
>
>
>
>
>
> PLEASE READ: This message is for the named person's use only. It may
> contain confidential, proprietary or legally privileged information. No
> confidentiality or privilege is waived or lost by any mistransmission. If
> you receive this message in error, please delete it and all copies from
> your system, destroy any hard copies and notify the sender. You must not,
> directly or indirectly, use, disclose, distribute, print, or copy any part
> of this message if you are not the intended recipient. Nomura Holding
> America Inc., Nomura Securities International, Inc, and their respective
> subsidiaries each reserve the right to monitor all e-mail communications
> through its networks. Any views expressed in this message are those of the
> individual sender, except where the message states otherwise and the sender
> is authorized to state the views of such entity. Unless otherwise stated,
> any pricing information in this message is indicative only, is subject to
> change and does not constitute an offer to deal at any price quoted. Any
> reference to the terms of executed transactions should be treated as
> preliminary only and subject to our formal written confirmation.
>
> _______________________________________________
> varnish-misc mailing list
> varnish-misc@varnish-cache.org
> https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
>