varnish load balance - HLS

Stefan Caunter stef at scaleengine.com
Wed Oct 29 19:54:33 CET 2014


If you do

varnishlog > log.txt

and run a request

you should see what is happening.

Unless you can get us some output to analyze, there is not much we can do
to help.





----

Stefan Caunter

On Sat, Oct 25, 2014 at 2:26 PM, Laszlo Danielisz <
laszlo.danielisz at yahoo.com> wrote:

> I can't get any m3u8 files from varnish.
> I'm using round-robin and I have one varnish for now.
>   From:"Stefan Caunter" <stef at scaleengine.com>
> Date:Sat, Oct 25, 2014 at 10:30
> Subject:Re: varnish load balance - HLS
>
> Do you get m3u8 list from a varnish? It's basic HTTP object caching. Do
> all varnishes return the same result/headers? What is the LB algorithm?
>
>
>
> ----
>
> Stefan Caunter
> ScaleEngine Inc.
>
> E: stefan.caunter at scaleengine.com
> Skype: stefan.caunter
> Toll Free Direct: +1 800 280 6042
> Toronto Canada
>
> On Fri, Oct 24, 2014 at 3:47 PM, Laszlo Danielisz <
> laszlo.danielisz at yahoo.com> wrote:
>
>> Yes, I can reach the .m3u8 and .ts files from wowza with curl/wget
>>
>>
>>   On Friday, October 24, 2014 4:20 AM, Stefan Caunter <
>> stef at scaleengine.com> wrote:
>>
>>
>> Alright, is wowza set to be an HTTP origin? Can you get a .ts list from
>> one varnish if you hit it directly?
>>
>>
>>
>> ----
>>
>> Stefan Caunter
>> ScaleEngine Inc.
>>
>> E: stefan.caunter at scaleengine.com
>> Skype: stefan.caunter
>> Toll Free Direct: +1 800 280 6042
>> Toronto Canada
>>
>> On Thu, Oct 23, 2014 at 3:24 PM, Laszlo Danielisz <
>> laszlo.danielisz at yahoo.com> wrote:
>>
>> If I access Wowza directly I get the proper response, the streams are
>> working from all four of the back ends.
>>  From:"Stefan Caunter" <stef at scaleengine.com>
>> Date:Thu, Oct 23, 2014 at 18:45
>> Subject:Re: varnish load balance - HLS
>>
>> On Thu, Oct 23, 2014 at 10:27 AM, Andreas Plesner Jacobsen <apj at mutt.dk>
>> wrote:
>> > On Thu, Oct 23, 2014 at 06:30:07AM -0700, Laszlo Danielisz wrote:
>> >>
>> >> I'm sending the varnishlog, I could not find anything about the
>> request in it.
>> >
>> > Either you have very high timeouts in varnish or you're not hitting
>> varnish.
>> > This looks like varnish 3, so try disabling log collation with
>> varnishlog -O
>> >
>> >> What is interesting is that varnish reports the backends sick after a
>> couple
>> >> seconds BUT with "HTTP 200 OK", while the .url defined in the probe is
>> still
>> >> up.
>> >
>> > Did you configure a 0 second timeout for those probes?
>>
>> Can we get some confirmation that curl request to the backend produces
>> valid response? If wowza is not set to respond correctly to request,
>> varnish is not the place to start troubleshooting.
>>
>>
>> ----
>>
>> Stefan Caunter
>>
>>
>> _______________________________________________
>> varnish-misc mailing list
>> varnish-misc at varnish-cache.org
>> https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
>>
>>
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-misc/attachments/20141029/9289c539/attachment.html>


More information about the varnish-misc mailing list