Varnish Listen problem ipv6 and ipv4
Hallo, i have a problem with Varnish 2.0.4 when i will start varnish with -A :80 then varnish will only Listen on ipv6. have anybody a idee who i can win round varnish? Thomas ___ varnish-misc mailing list varnish-misc@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-misc
Re: Sub-second granularity logs
]] Niall O'Higgins | Which shmrecord are we talking about ? | | I have only started looking through the existing shmlog tags to see | exactly what corresponds to our needs, but basically we are looking | for millisecond accuracy at each of these points: | | - When the cache received the request from the client | - When the request header was forwarded by the cache | - When the first byte of the response header was recieved back | - When the end of the response header was received or detected | - When the first byte of the response body was received or detected | - When the cache finished sending the response back to the client At least some of those are already available, as explained in http://varnish.projects.linpro.no/wiki/Varnishlog -- Tollef Fog Heen Redpill Linpro -- Changing the game! t: +47 21 54 41 73 ___ varnish-misc mailing list varnish-misc@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-misc
Re: Cookies being sent back with a cached response
]] Cosimo Streppone [...] | Then looking at varnishlog output, and grepping for Cookie, | I saw this (unrelated?): | | 90 TxHeader b Cookie: session=bf6ac86feaed6b23bef66a8f44097eac42cf24 | ... | | How can this ever happen? | The backends that serve the request never output cookies, and even if they | did, it would be Set-Cookie: anyway... I'm confused. This means Varnish is sending a header (TxHeader) to the backend (b), with a Cookie: session=… set. Anything received from a backend is RxHeader and b. I would guess at you having something, somewhere setting an erronous domain-wide cookie. Possibly in Javascript. -- Tollef Fog Heen Redpill Linpro -- Changing the game! t: +47 21 54 41 73 ___ varnish-misc mailing list varnish-misc@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-misc
Re: Excluding url's from varnishhist
]] Paul Dowman | Hi, | I'm having trouble figuring out how to exclude certain URL's from | varnishhist. I want to exclude static files, e.g. urls that match a pattern | like /\.png|\.gif|\.js|\.css|\.ico/ (because these don't cause much load on | the back-end, I want to see only the requests that would hit my app | servers). | | I know about the -X regex argument, but it doesn't seem to do what I want. | Actually I don't really understand what it does, the man page says that it | excludes log entries that match a pattern, but as far as I can tell it | doesn't match URL's. | | What's the right way to do this? There's currently no way to do this, I'm afraid. varnishtop -b -i TxURL gives you the URLs, but not any timing information. -- Tollef Fog Heen Redpill Linpro -- Changing the game! t: +47 21 54 41 73 ___ varnish-misc mailing list varnish-misc@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-misc
Re: Varnish Listen problem ipv6 and ipv4
]] Thomas Fragstein Hi, | when i will start varnish with -A :80 then varnish will only Listen | on ipv6. It's -a, not -A, but I'm guessing you're using that already. | have anybody a idee who i can win round varnish? Make sure you don't have anything else listening on ipv4 port 80? Also, which platform are you on? -- Tollef Fog Heen Redpill Linpro -- Changing the game! t: +47 21 54 41 73 ___ varnish-misc mailing list varnish-misc@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-misc
Re: Excluding url's from varnishhist
Tollef Fog Heen wrote: ]] Paul Dowman | Hi, | I'm having trouble figuring out how to exclude certain URL's from | varnishhist. I want to exclude static files, e.g. urls that match a pattern | like /\.png|\.gif|\.js|\.css|\.ico/ (because these don't cause much load on | the back-end, I want to see only the requests that would hit my app | servers). | | I know about the -X regex argument, but it doesn't seem to do what I want. | Actually I don't really understand what it does, the man page says that it | excludes log entries that match a pattern, but as far as I can tell it | doesn't match URL's. | | What's the right way to do this? There's currently no way to do this, I'm afraid. varnishtop -b -i TxURL gives you the URLs, but not any timing information. I realise it'd produce slightly different information, but you could create a separate backend director for files that match this regex, then look at varnishncsa for those particular backends... ___ varnish-misc mailing list varnish-misc@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-misc
Re: Cookies being sent back with a cached response
On Thu, 08 Oct 2009 10:21:48 +0200, Tollef Fog Heen tfh...@redpill-linpro.com wrote: | Then looking at varnishlog output, and grepping for Cookie, | I saw this (unrelated?): | | 90 TxHeader b Cookie: session=bf6ac86feaed6b23bef66a8f44097eac42cf24 | ... | | How can this ever happen? | The backends that serve the request never output cookies, and even if they | did, it would be Set-Cookie: anyway... I'm confused. This means Varnish is sending a header (TxHeader) to the backend (b), with a Cookie: session=… set. Anything received from a backend is RxHeader and b. Ok, it starts to make sense. Thanks for you clarification. -- Cosimo ___ varnish-misc mailing list varnish-misc@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-misc
Re: if-none-match status
]] Joe Williams | I am just curious in the status of if-none-match support from the | commit logs and this mailing list email | (http://www.mail-archive.com/varnish-misc@projects.linpro.no/msg02738.html) | it looks like its been committed. As was asked in the | aforementioned email are there any examples of how to use/configure/etc | this new feature? It's used by clients, there are no bits to configure. -- Tollef Fog Heen Redpill Linpro -- Changing the game! t: +47 21 54 41 73 ___ varnish-misc mailing list varnish-misc@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-misc
Re: performance scalability of a multi-core
I think we might want to roll our own strftime in TIM_format rather than relying on the madness that is described above and that is POSIX. madness: Now, that was funny :) -- Rogério Schneider MSN: stoc...@hotmail.com GTalk: stoc...@gmail.com Skype: stockrt http://stockrt.github.com ___ varnish-misc mailing list varnish-misc@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-misc
Re: Varnish Listen problem ipv6 and ipv4
Hi, oh sorry, yes is -a not the upper A and yes no other processes listen on port 80. ok i have only one process that listen ob 127.0.01:80. The Plattform is Debian 5.0 amd64 when i start the varnish with an ipv4 address it will bind to this (0.0.0.0:80 is also ok) but i start -a :80 then varnish only bind to :::80 and the protocol is ipv6 it will not listen ob ipv4 thx for help Thomas Tollef Fog Heen schrieb: ]] Thomas Fragstein Hi, | when i will start varnish with -A :80 then varnish will only Listen | on ipv6. It's -a, not -A, but I'm guessing you're using that already. | have anybody a idee who i can win round varnish? Make sure you don't have anything else listening on ipv4 port 80? Also, which platform are you on? ___ varnish-misc mailing list varnish-misc@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-misc
Re: Varnish Listen problem ipv6 and ipv4
Hallo Volks, thx for food for thought the problem was the process on 127.0.0.1:80 bye Thomas Thomas Fragstein schrieb: Hi, oh sorry, yes is -a not the upper A and yes no other processes listen on port 80. ok i have only one process that listen ob 127.0.01:80. The Plattform is Debian 5.0 amd64 when i start the varnish with an ipv4 address it will bind to this (0.0.0.0:80 is also ok) but i start -a :80 then varnish only bind to :::80 and the protocol is ipv6 it will not listen ob ipv4 thx for help Thomas Tollef Fog Heen schrieb: ]] Thomas Fragstein Hi, | when i will start varnish with -A :80 then varnish will only Listen | on ipv6. It's -a, not -A, but I'm guessing you're using that already. | have anybody a idee who i can win round varnish? Make sure you don't have anything else listening on ipv4 port 80? Also, which platform are you on? ___ varnish-misc mailing list varnish-misc@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-misc ___ varnish-misc mailing list varnish-misc@projects.linpro.no http://projects.linpro.no/mailman/listinfo/varnish-misc
Panic message: Assert error in VSL(), shmlog.c line 157
Varnish was running fine for months. It no longer starts and I see these errors
on the systems logs. This was compiled by me.
Thanks
Version:
[r...@web2 varnish-2.0.4]# /usr/local/sbin/varnishd -V
varnishd (varnish-2.0.4)
Copyright (c) 2006-2009 Linpro AS / Verdens Gang AS
Platform:
[r...@web2 varnish-2.0.4]# uname -a
Linux web2.trunity.net 2.6.18-128.7.1.el5 #1 SMP Mon Aug 24 08:21:56 EDT 2009
x86_64 x86_64 x86_64 GNU/Linux
Sep 17 22:37:52 web2 varnishd[27525]: Child (27526) Panic message: Assert error
in VSL(), shmlog.c line 157: Condition(loghead-ptr loghead-size) not
true. thread = (cache-worker)sp = 0x2aaaeb37b008 { fd = 13, id = 13, xid =
0, client = 10.4.4.5:34351, step = STP_FIRST, handling = error, ws =
0x2aaaeb37b078 { id = sess, {s,f,r,e} =
{0x2aaaeb37b808,,+15,(nil),+16384}, }, worker = 0x49de8be0 { }, },
Sep 17 22:37:52 web2 varnishd[27630]: Child (27631) died signal=6
Sep 17 22:37:52 web2 varnishd[27630]: Child (27631) Panic message: Assert error
in VSL(), shmlog.c line 157: Condition(loghead-ptr loghead-size) not
true. thread = (cache-worker)sp = 0x2aaaeb37b008 { fd = 13, id = 13, xid =
0, client = 10.4.4.5:34351, step = STP_FIRST, handling = error, ws =
0x2aaaeb37b078 { id = sess, {s,f,r,e} =
{0x2aaaeb37b808,,+15,(nil),+16384}, }, worker = 0x49de8be0 { }, },
Sep 17 22:37:52 web2 varnishd[27525]: child (2021) Started
Sep 17 22:37:52 web2 varnishd[27630]: child (2022) Started
Sep 17 22:37:52 web2 varnishd[27525]: Pushing vcls failed: CLI communication
error
Sep 17 22:37:52 web2 varnishd[27525]: Child (2021) said Closed fds: 4 5 6 10 11
13 14
Sep 17 22:37:52 web2 varnishd[27525]: Child (2021) said Child starts
Sep 17 22:37:52 web2 varnishd[27630]: Pushing vcls failed: CLI communication
error
Sep 17 22:37:52 web2 varnishd[27630]: Child (2022) said Closed fds: 4 5 6 10 11
13 14
Sep 17 22:37:52 web2 varnishd[27630]: Child (2022) said Child starts
Sep 17 22:37:52 web2 varnishd[27681]: Child (27682) died signal=6
Sep 17 22:37:52 web2 varnishd[27681]: Child (27682) Panic message: Assert error
in VSL(), shmlog.c line 157: Condition(loghead-ptr loghead-size) not
true. thread = (cache-worker)sp = 0x2aaaeb303008 { fd = 10, id = 10, xid =
0, client = 10.4.4.5:44416, step = STP_FIRST, handling = error, ws =
0x2aaaeb303078 { id = sess, {s,f,r,e} =
{0x2aaaeb303808,,+15,(nil),+16384}, }, worker = 0x4a141be0 { }, },
PAVEL PRAGIN
ppra...@solutionset.commailto:ejohans...@solutionset.com
T 650.328.3900
M 408.806.8621
F 650.328.3901
SolutionSet
The Brand Technology Company
http://www.SolutionSet.comhttp://www.solutionset.com/
PA 275 Alma Street, Palo Alto, CA 94301
SF 85 Second St., San Francisco, CA 94105
___
varnish-misc mailing list
varnish-misc@projects.linpro.no
http://projects.linpro.no/mailman/listinfo/varnish-misc
Re: Panic message: Assert error in VSL(), shmlog.c line 157
Remove the shared memory file, it must have become corrupted.
Varnish will recreate it on startup.
The file is named _.vsl and is located wherever your varnish
has its workdirectory (-n argument or whatever is default on
your platform)
Poul-henning
In message f1b9797980995749a47520a7f9136e48103daae...@mvlmailbox.solutionset.l
ocal, Pavel Pragin writes:
--===1052186233==
Content-Language: en-US
Content-Type: multipart/alternative;
boundary=_000_F1B9797980995749A47520A7F9136E48103DAAE5E7MVLMAILBOXsol_
--_000_F1B9797980995749A47520A7F9136E48103DAAE5E7MVLMAILBOXsol_
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Varnish was running fine for months. It no longer starts and I see these er=
rors on the systems logs. This was compiled by me.
Thanks
Version:
[r...@web2 varnish-2.0.4]# /usr/local/sbin/varnishd -V
varnishd (varnish-2.0.4)
Copyright (c) 2006-2009 Linpro AS / Verdens Gang AS
Platform:
[r...@web2 varnish-2.0.4]# uname -a
Linux web2.trunity.net 2.6.18-128.7.1.el5 #1 SMP Mon Aug 24 08:21:56 EDT 20=
09 x86_64 x86_64 x86_64 GNU/Linux
Sep 17 22:37:52 web2 varnishd[27525]: Child (27526) Panic message: Assert e=
rror in VSL(), shmlog.c line 157: Condition(loghead-ptr loghead-size)=
not true. thread =3D (cache-worker)sp =3D 0x2aaaeb37b008 { fd =3D 13, i=
d =3D 13, xid =3D 0, client =3D 10.4.4.5:34351, step =3D STP_FIRST, h=
andling =3D error, ws =3D 0x2aaaeb37b078 { id =3D sess, {s,f,r=
,e} =3D {0x2aaaeb37b808,,+15,(nil),+16384}, }, worker =3D 0x49de8be0 =
{ }, },
Sep 17 22:37:52 web2 varnishd[27630]: Child (27631) died signal=3D6
Sep 17 22:37:52 web2 varnishd[27630]: Child (27631) Panic message: Assert e=
rror in VSL(), shmlog.c line 157: Condition(loghead-ptr loghead-size)=
not true. thread =3D (cache-worker)sp =3D 0x2aaaeb37b008 { fd =3D 13, i=
d =3D 13, xid =3D 0, client =3D 10.4.4.5:34351, step =3D STP_FIRST, h=
andling =3D error, ws =3D 0x2aaaeb37b078 { id =3D sess, {s,f,r=
,e} =3D {0x2aaaeb37b808,,+15,(nil),+16384}, }, worker =3D 0x49de8be0 =
{ }, },
Sep 17 22:37:52 web2 varnishd[27525]: child (2021) Started
Sep 17 22:37:52 web2 varnishd[27630]: child (2022) Started
Sep 17 22:37:52 web2 varnishd[27525]: Pushing vcls failed: CLI communicatio=
n error
Sep 17 22:37:52 web2 varnishd[27525]: Child (2021) said Closed fds: 4 5 6 1=
0 11 13 14
Sep 17 22:37:52 web2 varnishd[27525]: Child (2021) said Child starts
Sep 17 22:37:52 web2 varnishd[27630]: Pushing vcls failed: CLI communicatio=
n error
Sep 17 22:37:52 web2 varnishd[27630]: Child (2022) said Closed fds: 4 5 6 1=
0 11 13 14
Sep 17 22:37:52 web2 varnishd[27630]: Child (2022) said Child starts
Sep 17 22:37:52 web2 varnishd[27681]: Child (27682) died signal=3D6
Sep 17 22:37:52 web2 varnishd[27681]: Child (27682) Panic message: Assert e=
rror in VSL(), shmlog.c line 157: Condition(loghead-ptr loghead-size)=
not true. thread =3D (cache-worker)sp =3D 0x2aaaeb303008 { fd =3D 10, i=
d =3D 10, xid =3D 0, client =3D 10.4.4.5:44416, step =3D STP_FIRST, h=
andling =3D error, ws =3D 0x2aaaeb303078 { id =3D sess, {s,f,r=
,e} =3D {0x2aaaeb303808,,+15,(nil),+16384}, }, worker =3D 0x4a141be0 =
{ }, },
PAVEL PRAGIN
ppra...@solutionset.commailto:ejohans...@solutionset.com
T 650.328.3900
M 408.806.8621
F 650.328.3901
SolutionSet
The Brand Technology Company
http://www.SolutionSet.comhttp://www.solutionset.com/
PA 275 Alma Street, Palo Alto, CA 94301
SF 85 Second St., San Francisco, CA 94105
--_000_F1B9797980995749A47520A7F9136E48103DAAE5E7MVLMAILBOXsol_
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
html xmlns:v=3Durn:schemas-microsoft-com:vml xmlns:o=3Durn:schemas-micr=
osoft-com:office:office xmlns:w=3Durn:schemas-microsoft-com:office:word =
xmlns:m=3Dhttp://schemas.microsoft.com/office/2004/12/omml; xmlns=3Dhttp:=
//www.w3.org/TR/REC-html40
head
meta http-equiv=3DContent-Type content=3Dtext/html; charset=3Dus-ascii
meta name=3DGenerator content=3DMicrosoft Word 12 (filtered medium)
style
!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:Calibri,sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:Calibri,sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
