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: [email protected] Skype: stefan.caunter Toll Free Direct: +1 800 280 6042 Toronto Canada On Thu, Oct 23, 2014 at 3:24 PM, Laszlo Danielisz < [email protected]> 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" <[email protected]> > 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 <[email protected]> > 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 > [email protected] > https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc >
_______________________________________________ varnish-misc mailing list [email protected] https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
