Mailing List Archive

Varnishlog -o bug
Hi,

When using varnishlog -o, log entries for cache misses appear on the
same line as the preceding log entry:

# varnishlog -o | grep 'VCL_call' | grep miss
12 VCL_call c recv lookup 12 VCL_call c miss fetch
15 VCL_call c recv lookup 15 VCL_call c miss fetch
15 VCL_call c recv lookup 15 VCL_call c miss fetch
12 VCL_call c recv lookup 12 VCL_call c miss fetch
15 VCL_call c recv lookup 15 VCL_call c miss fetch
15 VCL_call c recv lookup 15 VCL_call c miss fetch
^C

# varnishlog | grep 'VCL_call' | grep miss
16 VCL_call c miss
17 VCL_call c miss
16 VCL_call c miss
17 VCL_call c miss
21 VCL_call c miss
24 VCL_call c miss
^C

I am using Varnish 1.0.3 on FreeBSD/amd64, 6.2-RELEASE.

Plz fix k thx! :-)

Cheers,

--
Anders.
Varnishlog -o bug [ In reply to ]
Anders Nordby <anders at fupp.net> writes:
> When using varnishlog -o, log entries for cache misses appear on the
> same line as the preceding log entry:

It's not just cache misses - it appears to happen whenever two
VCL_call entries are logged in succession. I noticed it on friday,
but haven't had time to look into it yet.

DES
--
Dag-Erling Sm?rgrav
Senior Software Developer
Linpro AS - www.linpro.no
Varnishlog -o bug [ In reply to ]
Hi,

On Sat, Apr 21, 2007 at 11:57:52PM +0200, Dag-Erling Sm?rgrav wrote:
>> When using varnishlog -o, log entries for cache misses appear on the
>> same line as the preceding log entry:
> It's not just cache misses - it appears to happen whenever two
> VCL_call entries are logged in succession. I noticed it on friday,
> but haven't had time to look into it yet.

One more thing:

# varnishstat -1
Cannot open /tmp/_.vsl: No such file or directory
Segmentation fault: 11 (core dumped)

This is if varnish is not running.

Cheers,

--
Anders.
Varnishlog -o bug [ In reply to ]
des at linpro.no (Dag-Erling Sm?rgrav) writes:
> Anders Nordby <anders at fupp.net> writes:
> > When using varnishlog -o, log entries for cache misses appear on the
> > same line as the preceding log entry:
> It's not just cache misses - it appears to happen whenever two
> VCL_call entries are logged in succession. I noticed it on friday,
> but haven't had time to look into it yet.

The attached patch should fix it.

DES
--
Dag-Erling Sm?rgrav
Senior Software Developer
Linpro AS - www.linpro.no

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: varnishlog.diff
Url: http://projects.linpro.no/pipermail/varnish-misc/attachments/20070501/eca52a47/attachment.txt