Hi,
I'm completely new to varnish, other than having been reading about it
for a while and wishing I had the time to implement it for a
particular client for the last 6 months or so. Their web performance
issues have now become so bad that I suddenly have the time.
I've just downloaded the varnish 2.0.4 tarball from sourceforge and
attempted to build an RPM from it (extracted the spec file to SPECS
and copied the .tar.gz file to my SOURCES directory then used rpmbuild
-ba varnish.spec).
In the copious test output I had a failure of one of the tests,
detailed below. You asked for a report, so here it is.
# top TEST ././tests/b00007.vtc starting
# TEST Check chunked encoding from backend works
## s1 Starting server
### s1 listen on 127.0.0.1:9090 (fd 3)
## v1 Launch
### v1 CMD: cd ../varnishd && ./varnishd -d -d -n /tmp/__v1 -a
'127.0.0.1:9091' -T 127.0.0.1:9011 -P /tmp/__v1/varnishd.pid
### v1 opening CLI connection
## s1 Started on 127.0.0.1:9090
### v1 CLI connection fd = 4
Assert error in varnish_ask_cli(), vtc_varnish.c line 100:
Condition(i == 0) not true.
errno = 110 (Connection timed out)
/bin/sh: line 1: 8624 Aborted ./varnishtest ${dir}$tst
FAIL: ./tests/b00007.vtc
[...]
===============================================
1 of 130 tests failed
Please report to varnish-dev@projects.linpro.no
===============================================
make[3]: *** [check-TESTS] Error 1
make[3]: Leaving directory `/usr/src/redhat/BUILD/varnish-2.0.4/bin/
varnishtest'
make[2]: *** [check-am] Error 2
make[2]: Leaving directory `/usr/src/redhat/BUILD/varnish-2.0.4/bin/
varnishtest'
make[1]: *** [check-recursive] Error 1
make[1]: Leaving directory `/usr/src/redhat/BUILD/varnish-2.0.4/bin'
make: *** [check-recursive] Error 1
error: Bad exit status from /var/tmp/rpm-tmp.17064 (%check)
RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.17064 (%check)
This is on a CentOS 4.4 x86_64 virtual server (vmware) which we use
for builds for all of the code this client runs. Other than the failed
test, I can't see any errors or warnings in the build output.
To rule out a cosmic ray strike, I re-ran the rpmbuild and the second
time through got a clean bill of health - I'll leave it to you guys to
decide if it was indeed a cosmic ray strike or if there's perhaps an
intermittent issue with chunked encoding. I'm pretty sure I didn't
change anything on the system between the two build attempts and the
second run was from my shell history so they were as alike as I could
make them.
BTW - the spec file doesn't clean up BUILD/varnish-2.0.4 after itself.
Now to see if I can replicate their current load balancer config in
vcl...
Thanks,
Bernard.
--
Bernard Gardner
Spry Business Technology Solutions Pty. Ltd.
http://www.sprybts.com/
PO Box 860, Strawberry Hills, NSW 2012, AUSTRALIA
_______________________________________________
varnish-dev mailing list
varnish-dev@projects.linpro.no
http://projects.linpro.no/mailman/listinfo/varnish-dev
