Posted by cookiesunshinex on January 13, 2011 at 1:17pm
I'm doing some development on a Mercury 1.1beta instance and Varnish caching is starting to get in the way.
Is there a way to disable caching (both Varnish and Memcached) temporarily while we fix some issues?
Thanks.
Comments
I believe is you set caching
I believe is you set caching in the performance settings (/admin/settings/performance) to "none" that should do it.
That would be the case on a
That would be the case on a normal Drupal install, but Pressflow you are suppossed to set it to "none" so that Memcached can pick up the caching externally.
What I'm talking about it Varnish mostly. We are doing development work on our front page for non-authenticated users.
clearing varnish cache with the following every 2 minutes is getting tedious
ssh to machine
ssh -i ourkey.pem ubuntu@ec2-ouripaddress.eu-west-1.compute.amazonaws.com
telnet to varnish console
$ telnet localhost 6082
you will be at a blank prompt - type the following two commands
purge req.url ~ .*
quit
$ exit
Symetrik Design
Drupal Consulting
http://www.symetrkdesign.com
That would be the case on a
Hmmm. This opens up additional questions because AFAIK you are supposed to set Cache to external on Mercury. Would like to know myself.
Check this
Check this out
http://groups.drupal.org/node/70258
You can disable it /etc/mercury/server_tuneables
How, specifically, do you
How, specifically, do you disable it in /etc/mercury/server_tuneables?
All of those settings look like memory allocation variables to me
unless there is something that can be set in this section:
/etc/varnish/default.vcl
VARNISH_VCL_ERROR
VARNISH_VCL_FETCH
VARNISH_VCL_HASH
VARNISH_VCL_RECV
Symetrik Design
Drupal Consulting
http://www.symetrkdesign.com
You will see this towards the
You will see this towards the bottom of the file
# SERVICE STATE OVERRIDES# Set services to "ON" or "OFF". If left blank, the services will use the mercury defaults.
You can turn Varnish off by
export VARNISH_STATUS="OFF"Your going to need to adjust your ports as well or just add :8080 to the end of your browser, example www.example.com:8080/something
Hope that helps
Thank you sir. You are a
Thank you sir.
You are a scholar and a gentleman.
Symetrik Design
Drupal Consulting
http://www.symetrkdesign.com
If you change the tunable to
If you change the tunable to turn varnish off, you will need to re-run bcfg2: "sudo bcfg2 -vqed" so it will pick up the change.
However, for development purposes it is usually easiest to just hit apache directly by pointing your browser to port 8080. Also, restarting Varnish will clear its cache and is generally easier than connecting to it and purging: "sudo /etc/init.d/varnish restart"
I found that my apache was
I found that my apache was running on port 81, not 8080.
I originally opened port 8080 in the AWS security group. Then hit that with the browser, and got nothing.
I then looked in the /etc/apache2/ports.conf and found that it was listening on port 81
I opened port 81 in the AWS security group, and hit that with a browser and was returned a response.
Symetrik Design
Drupal Consulting
http://www.symetrkdesign.com
Are you running off of HEAD
Are you running off of HEAD or on 1.1?
I believe that it was 1.1beta
I believe that it was 1.1beta when I set it up initally.
Symetrik Design
Drupal Consulting
http://www.symetrkdesign.com