Re: "Whitescreen" issue with varnish 1.0.2-2 (debian etch)

2007-05-16 Thread Dag-Erling Smørgrav
Denis Brækhus <[EMAIL PROTECTED]> writes: > I wanted to update the VarnishOnDebian wiki page with a small note on > this situation, but it seems I need to be granted edit permissions? Done. DES -- Dag-Erling Smørgrav Senior Software Developer Linpro AS - www.linpro.no ___

Re: "Whitescreen" issue with varnish 1.0.2-2 (debian etch)

2007-05-16 Thread Denis Brækhus
- Ingvar Hagelund <[EMAIL PROTECTED]> wrote: > Rumors says 1.0.4 is on the stairs, banging at the door. It will > probably include an update to the Debian package. > I don't know if changes/updates will trickle into etch over the time. > Stig, Lars? For that to happen someone would have to bac

Re: "Whitescreen" issue with varnish 1.0.2-2 (debian etch)

2007-05-16 Thread Ingvar Hagelund
* Kenneth Rørvik >> I saw the same problems with 1.0.2 on redhat - empty documents >> returned after a while, possibly related to filling up the disk backend file. * Denis Brækhus >> 1.0.3 fixed it here, I didn't look deeper into it. > > 1.0.3 worked here too. I always intended to run 1.0.3, but

Re: "Whitescreen" issue with varnish 1.0.2-2 (debian etch)

2007-05-16 Thread Denis Brækhus
- Kenneth Rørvik <[EMAIL PROTECTED]> wrote: > I saw the same problems with 1.0.2 on redhat - empty documents > returned > after a while, possibly related to filling up the disk backend file. > > 1.0.3 fixed it here, I didn't look deeper into it. 1.0.3 worked here too. I always intended to ru

Re: "Whitescreen" issue with varnish 1.0.2-2 (debian etch)

2007-05-15 Thread Kenneth Rørvik
I saw the same problems with 1.0.2 on redhat - empty documents returned after a while, possibly related to filling up the disk backend file. 1.0.3 fixed it here, I didn't look deeper into it. -- Kenneth Rørvik, IT HiO Tlf 22 45 20 83 [EMAIL PROTECTED] ___

"Whitescreen" issue with varnish 1.0.2-2 (debian etch)

2007-05-15 Thread Denis Brækhus
Hi all, I have begun testing varnish on our main server pool, and the initial tests worked smoothly. However as soon as I put the box under load (gave it a slice of our production traffic) it started "fumbling" requests. I know it's not a very good description, but I have a hard time understand