Closed huguesalary closed 10 years ago
Could you try to run 'make check' ?
The make check
fails for me, but it actually fails for every single vmod I compile. I suspect a problem with varnishadm
on the mac os x port. If I read the test well, it seems to fail because varnishadm
is supposedly not answering. But we clearly see later that it does. Something that also makes me think there's a problem with varnishadm
is that when I start it and use it, there's no prompt. Typing a command and validating with [enter] will execute the command normally though. I added a picture, that should help.
$make check
Making check in src
/Users/hugues/Downloads/varnish-3.0.2/bin/varnishtest/varnishtest -Dvarnishd=/Users/hugues/Downloads/varnish-3.0.2/bin/varnishd/varnishd -Dvmod_topbuild=/Users/hugues/libvmod-digest tests/test01.vtc
**** top 0.0 macro def varnishd=/Users/hugues/Downloads/varnish-3.0.2/bin/varnishd/varnishd
**** top 0.0 macro def vmod_topbuild=/Users/hugues/libvmod-digest
**** top 0.0 macro def pwd=/Users/hugues/libvmod-digest/src
**** top 0.0 macro def topbuild=/Users/hugues/libvmod-digest/src/../..
**** top 0.0 macro def bad_ip=10.255.255.255
**** top 0.0 macro def tmpdir=/tmp/vtc.72111.0aa822c9
* top 0.0 TEST tests/test01.vtc starting
*** top 0.0 varnishtest
* top 0.0 TEST Test digest vmod
*** top 0.0 server
** s1 0.0 Starting server
**** s1 0.0 macro def s1_addr=127.0.0.1
**** s1 0.0 macro def s1_port=50707
**** s1 0.0 macro def s1_sock=127.0.0.1 50707
* s1 0.0 Listen on 127.0.0.1 50707
** s1 0.0 Started on 127.0.0.1 50707
*** top 0.0 varnish
** v1 0.0 Launch
*** v1 0.0 CMD: cd ${pwd} && ${varnishd} -d -d -n /tmp/vtc.72111.0aa822c9/v1 -l 10m,1m,- -p auto_restart=off -p syslog_cli_traffic=off -a '127.0.0.1:0' -S /tmp/vtc.72111.0aa822c9/v1/_S -M '127.0.0.1 50708' -P /tmp/vtc.72111.0aa822c9/v1/varnishd.pid -sfile,/tmp/vtc.72111.0aa822c9/v1,10M
*** v1 0.0 CMD: cd /Users/hugues/libvmod-digest/src && /Users/hugues/Downloads/varnish-3.0.2/bin/varnishd/varnishd -d -d -n /tmp/vtc.72111.0aa822c9/v1 -l 10m,1m,- -p auto_restart=off -p syslog_cli_traffic=off -a '127.0.0.1:0' -S /tmp/vtc.72111.0aa822c9/v1/_S -M '127.0.0.1 50708' -P /tmp/vtc.72111.0aa822c9/v1/varnishd.pid -sfile,/tmp/vtc.72111.0aa822c9/v1,10M
*** v1 0.0 PID: 72129
**** v1 0.1 CLIPOLL 0 0x0 0x0
---- v1 0.1 FAIL timeout waiting for CLI connection
* top 0.1 RESETTING after tests/test01.vtc
*** v1 0.1 debug| Platform: Darwin,10.8.0,x86_64,-sfile,-smalloc,-hcritbit\n
** s1 0.1 Waiting for server
**** s1 0.1 macro undef s1_addr
**** s1 0.1 macro undef s1_port
**** s1 0.1 macro undef s1_sock
*** v1 0.1 debug| 200 233 \n
*** v1 0.1 debug| -----------------------------\n
*** v1 0.1 debug| Varnish Cache CLI 1.0\n
*** v1 0.1 debug| -----------------------------\n
*** v1 0.1 debug| Darwin,10.8.0,x86_64,-sfile,-smalloc,-hcritbit\n
*** v1 0.1 debug| \n
*** v1 0.1 debug| Type 'help' for command list.\n
*** v1 0.1 debug| Type 'quit' to close CLI session.\n
*** v1 0.1 debug| Type 'start' to launch worker process.\n
*** v1 0.1 debug| \n
** v1 1.1 Wait
** v1 1.1 R 72129 Status: 0000
* top 1.2 TEST tests/test01.vtc FAILED
# top TEST tests/test01.vtc FAILED (1.183) exit=1
make[1]: *** [tests/test01.vtc] Error 2
make: *** [check-recursive] Error 1
Hi.
From what I see it appears that libmhash has a problem on BSD and macos. The rest works. The libvmod-digest layer between Varnish and libmhash is pretty thin.
The varnishadm problem you describe is probably readline/editline related and shouldn't influence this vmod in any way.
Are you still experiencing this? What libmhash version are you running?
Hi Lasse,
I haven't tried on the latest version of Varnish. As soon as I can I'll compile the latest version and try again.
-Hugues
Hi there,
I just compiled your vmod on my
Mac Os X 10.6.8
I tried using the
digest.hash_md5()
function in my VCL, the VCL compiles with no error, but when I make an HTTP request, nothing is returned to the browser.I then tried using
digest.hash_sha1
, and it works.VCL Config
Varnishlog
Am I missing something?
-Hugues