I get the same error starting varnish with the default command line
(contained in /etc/default/varnish), like so:
varnishd -a :6081 -T localhost:6082 -f ../../etc/varnish/default.vcl
-S /etc/varnish/secret -s malloc,256m
where ../../etc/varnish/default.vcl contains the vcl file of a freshly
extracted varnish deb (retieved with aptitude).
Upon further research, I've found that this bug disappears when the
package is built with debug symbols, and in diagnostics mode like
so:
--enable-debugging-symbols --enable-diagnostics
/Rune
On Wed, Apr 3, 2013 at 4:17 PM, Stig Sandbeck Mathisen s...@debian.org wrote:
Hello,
Thanks for reporting an issue with varnish.
Does varnish start with the default vcl, or the default configuration?
--
Stig Sandbeck Mathisen s...@debian.org
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
