n vcl_recv?
Any way for the script to return a header that can tell vcl_fetch to
pipe? Or is that too late?
Am I right to assume that "pass" is not intended to work in a case like
this?
running varnish-2.0.3
Regards
Gaute Amundsen
___
varni
ng varnish when I get close.
I guess I will have to resort to tempfiles and vcl.load :)
Gaute
On Wednesday 03 June 2009 15:55:56 Gaute Amundsen wrote:
> Hi
>
> After removing comments, how would I have to process the normal config file
> to be able to load it as a string using vcl
.host = \"127.0.0.1\"; }\n\tacl a {\n\t\t\"1.2.3.4\"/31;
\n\t\t\"1.2.3.4\"/31;\n\t}\n\tsub vcl_recv { if (client.ip ~ a) { pass; } }\n"
I could make it work by pasting into telnet, but not with varnishadm, or
python telnetlib for that matter.
Any suggestions?
suggestions? Something involving the Client-Date header perhaps?
And any suggestions on the deeper mystery are most welcome as well of course.
Right now we are expanding logging, in the hope of catching the bug "in the
wild"
Regards
Gaute Amundsen
--
Programmerer - Pixelhos
Various usages:
remove req.http.cookie;
unset obj.http.Set-Cookie;
unset resp.http.magicmarker;
Unset is not in man vcl (v2.0.3) but remove is.
A clarification would be nice :)
Regards
Gaute Amundsen
___
varnish-misc mailing list
varnish-misc
On Wednesday 25 February 2009 19:55:54 Dag-Erling Smørgrav wrote:
> Gaute Amundsen writes:
> > Dag-Erling Smørgrav writes:
> > > There is no "purge.list" command.
> >
> > No?
>
> Sorry, I was looking at the parent commands; purge.list is a child
&
On Wednesday 25 February 2009 17:30:59 Dag-Erling Smørgrav wrote:
> Gaute Amundsen writes:
> > # varnishadm -T localhost:90 purge.list
> > An error occured in receiving answer.
>
> There is no "purge.list" command.
>
> DES
# varnishadm -T localhost:90 help
servers soon, will a newer distribution make a difference?
( to ubuntu server jeos 8.04 )
Regards
Gaute Amundsen
___
varnish-misc mailing list
varnish-misc@projects.linpro.no
http://projects.linpro.no/mailman/listinfo/varnish-misc
Hi
we are currently running varnish-1.0.4-3el4.i386.rpm
( with a small patch )
We were planning to hold out for the next release, but our need for per-host
purging is growing rapidly...
Is it possible to say anything about how far off a release might be, or is
there a particular SVN revision
On Friday 06 July 2007 12:21, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, Gaute Amundsen writes:
> >On Thursday 05 July 2007 19:39, Andr=E9 Cruz wrote:
> >> I'm caching pages from different vhosts, say x.com and y.com.
> >>
> >> If I wa
That did the trick for the processing :-D
Only the logging itself left then.
With som luck logger restarts on logrotate every hour will keep that stable
til 1.1 is out :-)
Gaute
On Thursday 05 July 2007 20:20, Gaute Amundsen wrote:
> On Thursday 05 July 2007 17:18, Dag-Erling Smørgrav wr
On Thursday 05 July 2007 20:30, André Cruz wrote:
> On 2007/07/05, at 19:13, Gaute Amundsen wrote:
> > That's not easily done, as far as I have been able to determine.
> > I've submitted a feature request for it..
>
> Where is it so that I can vote for it? :) Do you
On Thursday 05 July 2007 19:39, André Cruz wrote:
> Hello.
>
> I'm caching pages from different vhosts, say x.com and y.com.
>
> If I want to purge all the data from one of the vhosts how do I do
> it? "url.purge x.com.*" does not work. I'm a bit confused with the
> syntax since the wiki only talks
> Ah, OK, you won't be able to process log files larger than about 2 GB on
> a 32-bit machine. I should probably figure out a way to get around
> that.
Ok, now I have set up /var/log/varnish/varnish.log to rotate every hour, and a
postrotate action on that to pipe through varnishncsa and append
On Wednesday 04 July 2007 09:47, Dag-Erling Smørgrav wrote:
> Gaute Amundsen <[EMAIL PROTECTED]> writes:
> > On Tuesday 03 July 2007 16:30, Dag-Erling Smørgrav wrote:
> > > Is this a 32-bit machine, BTW?
> >
> > It is. Quad Xeon 3 GHz.
>
> Ah, OK, you won&
On Tuesday 03 July 2007 16:30, Dag-Erling Smørgrav wrote:
> varnishncsa shouldn't care, as it processes the log file linearly, but I
> generally prefer to rotate by size.
Hm.. ok. But that would have me running awstats at odd times..
Wil just have to try it out I guess
> Is this a 32-bit machine
On Tuesday 03 July 2007 16:05, Dag-Erling Smørgrav wrote:
> Gaute Amundsen <[EMAIL PROTECTED]> writes:
> > Rotation is weekly, and the previous logs have sane dates.
>
> Weekly rotation is probably far too seldom, Varnish can easily generate
> several gigabytes of log da
Hm..
I was finding quite a bit of "Pipe Shut" just running varnishlog -o.
I's out of my buffer, so I cant paste it in right now, but could it bee that I
was opening to many pipes?
I the default action in vcl_recv was pipe, and only a few hosts would get a
lookup... Trying with pass now, and it
On Tuesday 03 July 2007 15:18, Dag-Erling Smørgrav wrote:
> Gaute Amundsen <[EMAIL PROTECTED]> writes:
> > We have had logging running for about a week now with no apparent
> > problems, but yesterday I routed all our traffic into varnish, and now
> > bad things happe
Hi again.
We have had logging running for about a week now with no apparent problems,
but yesterday I routed all our traffic into varnish, and now bad things
happen.
/var/log/varnish/varnish.log just stops growing after a while and a tail -n 1
gives me pages after pages of:
Pipe Shut write(r
On Tuesday 03 July 2007 11:27, Dag-Erling Smørgrav wrote:
> Gaute Amundsen <[EMAIL PROTECTED]> writes:
> > Now the question is, how do I best detect if varnsih should have a
> > problem? Would it be reasonably reliable to just chek if the pid from
> > /var/run/varnish.p
I have come to understand that in some builds under some conditions varnish
may hang or a crash. (we run 1.0.4-3el4.i386.rpm)
I have now routed all our ~180 sites troug varnish, pipe by default, cached
for selected hostnames. Talk a bout all ones eggs in one basket :)
The way it is all set up,
On Wednesday 27 June 2007 22:10, Dag-Erling Smørgrav wrote:
> Gaute Amundsen <[EMAIL PROTECTED]> writes:
> > The problem is that AWstats really need a separate field for server
> > hostname (apache: %v) to filter separate vhosts on. [...] The only
> > option I can th
st.
(quite unusual place to have it, is it not?)
Any sed wizards out there?
sed -e 's#\("\([A-Z]\+\) http://\([^/]*\)\)#\3 \1#g'
Or any better sugestions?
Regards
Gaute Amundsen
___
varnish-misc mailing list
varnish-misc@projects.lin
> * Stig Sandbeck Mathisen
>
> > One separate init script (for Debian) is available at
> > http://varnish.projects.linpro.no/browser/trunk/varnish-cache/debian/varn
> >ish.varnishlog.init
>
> Just for the record, the RedHat subdirectory has a similar script. It is
> also included in the RHEL packa
d/varnish_combined-access_log &
Regards
Gaute Amundsen
___
varnish-misc mailing list
varnish-misc@projects.linpro.no
http://projects.linpro.no/mailman/listinfo/varnish-misc
am looking at piping varnishlog -o thru a script to filter on hostname, and
then pick out the relevant fields.
Or is this doable with the right regexp perhaps?
Regards
Gaute Amundsen
___
varnish-misc mailing list
varnish-misc@projects.linpro.no
http
Hi.
Just today, I got asked by our server guy, if he should upgrade from 1.0.1 to
1.0.3, to se if that would fix some problems we have had reported.
I am not yet convinced that those glitches are related to varnish and not the
customers IE7, but if you have some RPM's right around the corner, t
the Fielding Dissertation, so I expect to be working with Varnish
for quite a while :)
Regards
Gaute Amundsen
--
Programmerer - Pixelhospitalet AS
Tørkoppveien 10, 1570 Dilling
Tlf. 24 12 97 81 - 9074 7344
___
varnish-misc mailing list
29 matches
Mail list logo
