Re: varnishncsa outage

nd c 1750343256 1315468371.652468920 1315468371.652515173 0.640084982 nan nan 12 StatSess c 127.0.0.1 57867 1 1 1 0 0 0 0 0 As you can see there is no RxRequest tag so df_m is not set. Varnishncsa crashed, as expected. -- Jean-Baptiste Quenot __

Re: varnishncsa outage

hat change (and the broken header patch) varnishncsa did not crash at all. All the best, -- Jean-Baptiste Quenot ___ varnish-dev mailing list varnish-dev@varnish-cache.org https://www.varnish-cache.org/lists/mailman/listinfo/varnish-dev

Re: varnishncsa outage

I notice another crash with varnishncsa, related to header processing: https://gist.github.com/1196892 AFAICT this is fixed in last commits "Ignore invalid HTTP headers" from Andreas Plesner Jacobsen in Varnish master branch. Can someone confirm? -- Jean-Bapti

Re: varnishncsa outage

vtqh_last = 0x0}} Please find attached a patch that checks for mandatory fields. Curiously the code was there but disabled. 2011/9/5 Tollef Fog Heen : > ]] Jean-Baptiste Quenot > > | It turns to be a good old "segmentation fault" crash, caused by the > | SLT_ReqEnd tag processi

Re: varnishncsa outage

It turns to be a good old "segmentation fault" crash, caused by the SLT_ReqEnd tag processing "time to first byte". Here is the gdb backtrace: https://gist.github.com/1188943 -- Jean-Baptiste Quenot ___ varnish-dev mailing list

Re: Assert error in WSLR() on SLT_HttpGarbage

bug? I also had similar "assert" crashes with varnish 2.1. 2011/9/2 Poul-Henning Kamp : > In message > > , Jean-Baptiste Quenot writes: > >>With 3.0.1 rc1 I get the following crashes frequently: >> >>https://gist.github.com/1188467 >> >>Is it

varnishncsa outage

on start. No core dump, no kernel message. I don't know if varnishncsa printed an error because when run as a daemon there is no error log (maybe using syslog for this would be more appropriate BTW). Your help will be appreciated, -- Jean-Baptiste Q

Assert error in WSLR() on SLT_HttpGarbage

Hello Varnish, With 3.0.1 rc1 I get the following crashes frequently: https://gist.github.com/1188467 Is it related to HTTP/1.0? I can't see a crash with HTTP/1.1. Any idea? -- Jean-Baptiste Quenot ___ varnish-dev mailing list varnish-dev@va

Re: Varnish 3.0.0 crash

Got the same crash with 3.0.1 rc1. I added CFLAGS+=-O0 to make your life easier. https://gist.github.com/1182132 -- Jean-Baptiste Quenot ___ varnish-dev mailing list varnish-dev@varnish-cache.org https://www.varnish-cache.org/lists/mailman/listinfo

[PATCH] Fix time_firstbyte bug in varnishncsa

works fine for logging the object age: %{Host}i %h %l %u %t "%r" %s %b "%{Referer}i" "%{User-agent}i" %{Varnish:time_firstbyte}x %{Age}o Cheers, -- Jean-Baptiste Quenot ___ varnish-dev mailing list varnish-dev@varnish

Re: varnishncsa 3.0.0 crash

Do you believe this is fixed by https://www.varnish-cache.org/trac/ticket/944 ? Cheers, -- Jean-Baptiste Quenot ___ varnish-dev mailing list varnish-dev@varnish-cache.org https://www.varnish-cache.org/lists/mailman/listinfo/varnish-dev

Re: Debug symbols broken in debian package

2011/7/18 Stig Sandbeck Mathisen : > I think you left some pieces out, but I got the general idea. :) Ooops indeed I thought the extra varnish-dbg package was coming from the stock debian package, but I just realized it's a patch I added myself a long time ago. Thanks! -- Jean-Baptist

Re: Varnish 3.0.0 crash

OK here is the crash log with proper debug symbols: https://gist.github.com/1086698 Time for me to get back to 2.1. -- Jean-Baptiste Quenot ___ varnish-dev mailing list varnish-dev@varnish-cache.org https://www.varnish-cache.org/lists/mailman

Re: varnishncsa 3.0.0 crash

clean_logline(lp); break; } lp->df_ttfb = strdup(ttfb); t = l; localtime_r(&t, &lp->df_t); /* got it all */ lp->complete = 1; break; } Removing %{Varnish:time_firstbyte}x from log format does not help, st

Re: varnishncsa 3.0.0 crash

r/log/varnishncsa.log -D -P /var/run/varnishncsa/varnishncsa.pid -F '%{Host}i %h %l %u %t "%r" %s %b "%{Referer}i" "%{User-agent}i" %{Varnish:time_firstbyte}x %{Varnish:age}x' Cheers, -- Jean-Baptiste Quenot ___

varnishncsa 3.0.0 crash

98 #3 0x7f0371387f63 in VSL_Dispatch () from /usr/lib/libvarnishapi.so.1 #4 0x00402d74 in main (argc=10, argv=) at varnishncsa.c:830 -- Jean-Baptiste Quenot ___ varnish-dev mailing list varnish-dev@varnish-cache.org https://www.varnish-cache.org/lists/ma

Debug symbols broken in debian package

Hi there, To whom it may concern, the Debian and Ubuntu packages for Varnish do not build the debug symbols correctly. Here is a patch to fix this issue: http://dl.dropbox.com/u/5836407/Patches/VarnishDeb_3.0.0-Fix-packaging-of-debug-symbols.patch Best regards, -- Jean-Baptiste Quenot

Re: Varnish 3.0.0 crash

"/var/tmp/%p.core" in the kernel, otherwise no core was generated. I can't manage to load debug symbols from libvarnish1... -- Jean-Baptiste Quenot ___ varnish-dev mailing list varnish-dev@varnish-cache.org https://www.varnish-cache.org/li

Varnish 3.0.0 crash

you need a gdb backtrace or something? -- Jean-Baptiste Quenot ___ varnish-dev mailing list varnish-dev@varnish-cache.org https://www.varnish-cache.org/lists/mailman/listinfo/varnish-dev

varnishlog -o option

RxURL '^/$' -- Jean-Baptiste Quenot ___ varnish-dev mailing list varnish-dev@varnish-cache.org https://www.varnish-cache.org/lists/mailman/listinfo/varnish-dev

Re: Varnish 3.0 NCSA log format missing object age

patch of varnish 2.1, I don't know why this field was omitted during 3.0 development. Best regards, -- Jean-Baptiste Quenot ___ varnish-dev mailing list varnish-dev@varnish-cache.org https://www.varnish-cache.org/lists/mailman/listinfo/varnish-dev

Varnish 3.0 NCSA log format missing object age

acts to monitor, but I'd like to have a formal definition for them. Thanks in advance, and keep up the good job. -- Jean-Baptiste Quenot ___ varnish-dev mailing list varnish-dev@varnish-cache.org http://www.varnish-cache.org/lists/mailman/listinfo/varnish-dev

Spurious TODO in varnishncsa.c 3.0 beta1

For the sake of completeness, there is a TODO in varnishncsa.c: * TODO:- Log in any format one wants But this is actually implemented with the -F option. Best regards, -- Jean-Baptiste Quenot ___ varnish-dev mailing list varnish-dev

Re: Assert error in WSLR()

Can I safely ignore this error, or shall I dig further to find the cause? 2011/4/15 Jean-Baptiste Quenot : > Hi there, > > Since upgrading from Varnish 2.0.6 to Varnish 2.1.3 (both with the > Apache LogFormat patch applied) I get this error in production: > > Apr 15 11:54:31

Assert error in WSLR()

shd[11313]: Child (20985) said Apr 15 11:54:32 gw1 varnishd[11313]: Child (20985) said Child starts Apr 15 11:54:32 gw1 varnishd[11313]: Child (20985) said managed to mmap 53687091200 bytes of 53687091200 Does it ring a bell to you? Thanks in advance, -- Jean-Baptiste Quenot __

Is request time available in VCL?

mation available in VCL? Thanks in advance, -- Jean-Baptiste Quenot ___ varnish-dev mailing list varnish-dev@varnish-cache.org http://www.varnish-cache.org/lists/mailman/listinfo/varnish-dev

Re: Size of GET URI?

I finally found the shm_reclen setting by issuing a "git grep truncate" in the source code :-) And it lead me to this ticket http://www.varnish-cache.org/trac/ticket/528 I added "-p shm_reclen=65535" to the command line, it works as expected. Cheers, --

Size of GET URI?

Hi there, I'm using Varnish 2.0.6 on Ubuntu, and wonder why my GET URIs are truncated to 256 bytes in the output of varnishlog and varnishncsa? Is it possible to tune this? Thanks in advance, -- Jean-Baptiste Quenot ___ varnish-dev mailing

Panic message: Assert error in STV_alloc() even with a small object

mall one. This is varnish 2.0.6 running on a 64-bit version of Ubuntu 9.04, with a patch to support Apache LogFormat. What's wrong? Shall I update to 2.1.3, although I don't see anything related to this problem in the changelog? Thanks in advance, -- Jean-Baptiste Quenot [1] http://varnish-cache.org/ticket/503 ___ varnish-dev mailing list varnish-dev@varnish-cache.org http://lists.varnish-cache.org/mailman/listinfo/varnish-dev

Re: production of Varnish Documentation

;        it structurally into the more capable formats. > > In other words: we are talking about the "ReStructuredText" of the > Python project. +1 I use RST+Docutils with Sphinx (a tool to build the documentation with just a simple