Posted by alexus on September 27, 2011 at 5:24pm
I'm trying to use Varnish HTTP Accelerator Integration module ( http://drupal.org/project/varnish ) in our environment and I'm getting following error under "admin/settings/varnish"
Status: The Varnish control terminal is not responding at 172.16.0.110 on port 6082.
for troubleshooting purposes I did
telnet 172.16.0.110 6082
Trying 172.16.0.110...
Connected to 172.16.0.110.
Escape character is '^]'.
200 154
Varnish HTTP accelerator CLI.
Type 'help' for command list.
Type 'quit' to close CLI session.
quit
500 22
Closing CLI connection
Connection closed by foreign host.
so communication between them seems to be Ok
any ideas?
Comments
At the risk of asking a daft
At the risk of asking a daft question, have you tried (and is it possible for you to try) a different port to rule out some oddities in the handling of connections (firewalls, etc)?
I assume this isn't localhost is it? (If it were, you could try 127.0.0.1 as the IP address).
/Al
it's not a firewall issue,
it's not a firewall issue, since i can telnet from that place to varnish's port
there is a communication between them, its just for one reason or another varnish's plugin doesn't sees it
alexus.org && alexus.biz
Also, is the php sockets
Also, is the php sockets extension enabled? I've had clients who had to recompile PHP in order to get this working.
do you know which extension
do you know which extension is it exactly? I've looked and I only found this:
just looked at phpinfo(); and found this
sockets
Sockets Support enabled
so if you were referring to that, this is enabled
alexus.org && alexus.biz
Two checks
Two checks may be needed:
do you know exactly which
do you know exactly which timeout? page renders pretty quickly though, doesn't seems like it's timeout issue...
not using localhost so i'm already accessing it via "normal" ip
alexus.org && alexus.biz
A little more info about our setup
Varnish is running on a separate VM from our Pressflow VM. Like Alexus wrote we are able to connect on that port from the pressflow server to the Varnish proxy. However, I did open up UDP in addition to TCP on that port in hopes that was it. We use the PHP from RedHat so it's not compiled.
The reason we are trying to do this is that we have some Front-end folk that need to have the ability to Flush the cache via Drupal when they put up an urgent article/node, etc. Currently, Flushing all caches does not clear the Varnish cache and we were looking at this module as a method to do that. So if you know of another way that we can accomplish this same task we are all ears.
Thanks again!
Spotty reception
Ok for some reason we see it is running and then it isn't. The status toggles back and forth between:
Status:
Varnish running. Observe more detailed statistics here.
Status:
The Varnish control terminal is not responding at xxx.xxx.0.110 on port 6082.
When I click on the statistics I do see information, so it is communicating sometimes but is there any way to see what might be causing the 'Spotty Reception'?
And this is what we see from the 'statistics' on our Staging pressflow VM
3643408384 bytes free
74 SMS allocator requests
9472 SMS bytes allocated
9472 SMS bytes freed
915 Backend requests made
1 N vcl total
1 N vcl available
30 N total active purges
30 N new purges added
317 N objects tested
634 N regexps tested against
28 N duplicate purges removed
1317 HCB Lookups without lock
468 HCB Lookups with lock
468 HCB Inserts
8859 Client uptime
Now using 1.0
Earlier we were using the HEAD version and that seemed to give us inconsistent communication with Varnish. Now we downgraded that module to the 1.0 release and it appears to be communicating consistently. Fingers crossed that it does what we need. Thanks for you help.
Hi, Another way to do is to
Hi,
Another way to do is to call purge in the VCL. We have a setup where we just issue /purgeall to the top level domain, and it purges the cache with respect to cache headers, so that all new pages and updated pages will get updated.
https://www.varnish-cache.org/docs/trunk/tutorial/purging.html
Also, with Varnish 2.x you can have a challanging respons. If that is properly setup than the varnish module won't work. But that said, it's no issue to use varnish without a challanging response...
--
Vegard
Try using another port
I had an issue with running Varnish on this port with a cents installation.. changing the port fixed it.... just a suggestion.
Switching ports didn't help
Switching ports didn't help me.