On Fri, Oct 7, 2011 at 2:54 PM, Per Buer <[email protected]> wrote: > On Fri, Oct 7, 2011 at 8:17 PM, Kurt Kraut <[email protected]> wrote: >> What do you think? Is it a bug? > > Okey. This is one of the reasons top-posting is bad. Tollef asked you for > varnishlog entry, which is the only sane input we can have in order to > actually tell you what is going on without it being total speculation.
I also noticed similar behavior with large files with Varnish 3.0.1. Today, when I tried to do large files.. Here's a wget run. 2011-10-07 17:18:59 (442 KB/s) - Connection closed at byte 28062437. Retrying. 2011-10-07 17:20:03 (486 KB/s) - Connection closed at byte 59268331. Retrying. 2011-10-07 17:21:07 (500 KB/s) - Connection closed at byte 90762224. Retrying. varnishlog craps out with the following message: 11 Debug c Write error, retval = 28062720, len = 107637870, errno = Success Indeed, wget does do Range: requests when the connection dies, but a different machine (OSX with curl and firefox) would end the download thinking the file was done. > I'm _guessing_ you are running into timeouts. But without a log entry, that's > only a guess. Could be timeouts, but I'm not sure why they would happen in this case. Here's the pure unbridled unadulterated vlog http://u.delta9.pl/k/drop/v-drops.vlog oh on a side note it seems maybe the 3.0 varnishlog format isn't compatible with the 2.x one? -- http://comotion.delta9.pl http://u.delta9.pl http://kacper.doesntexist.org Too much order is its own chaos. Employ no technique to gain supreme enlightment. _______________________________________________ varnish-misc mailing list [email protected] https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
