Posted by perandre on December 17, 2010 at 7:28pm
I have setup a few sites using the Pantheon Linode stack script (what a blessing!). On one of them, I want to totally disable Varnish, but keep all other settings on the server (memcache, etc). If I kill all Varnish processes, the site goes down. How to get back to good ol' Apache only?
Comments
Can you access your site from
Can you access your site from example.com:8080? If so then you probably need to move apache back to port 80 because I believe Varnish listens on 80 and forwards to apache on 8080 from a standard Mercury install.
Without touching anything, I
Without touching anything, I have access on example.com:8080. Does that mean I can just set the vhost to :80 and I'm good?
Per André Rønsen | Front | Twitter: @perandre
To answer my own question:
To answer my own question: No, that we'll throw me a 404.
Per André Rønsen | Front | Twitter: @perandre
try editing
try editing /etc/apach2/ports.conf and changing 8080 to 80 and then /etc/init.d/apache2 restart
I tried that, but then I got
I tried that, but then I got a "Fail!" restarting Apache. Hm...
Per André Rønsen | Front | Twitter: @perandre
Did you edit your
Did you edit your etc/apache2/site-available/default port too?
Can I ask why you need to disable varnish?
Hi, actully, I didn't edit
Hi,
actully, I didn't edit /etc/apache2/sites-available/default... I guess I should try that!
Why: On this campaign site, as it turns out, we won't have any anonymous users at all. So, Varnish won't do much good for us. Add to this that I've had lots of random Varnish 503's on this particular site, for some reason.
Per André Rønsen | Front | Twitter: @perandre
Editing
Editing /etc/apache2/sites-available/default did not help. I found the reason for the Varnish 503s, however; it's the javascript_aggregator. I'll post a thread on that.
Per André Rønsen | Front | Twitter: @perandre
re: Editing
Replacing port 8080 with port 80 in your /etc/apache2/ports and /etc/apache2/sites-available/default and the restarting apache should allow you to run a pantheon server w/o varnish. I would then change your drupal cache from "external" to aggressive (assuming the install modules will allow).
Make sure that varnish is off when you restart apache or apache will fail to restart since port 80 will be used by varnish.
Depending on the version of Pantheon, you can the following variable in /etc/pantheon/server_tuneables:
from export VARNISH_STATUS="" to export VARNISH_STATUS="OFF"
Hope this helps,
Greg
--
Greg Coit
Systems Administrator
http://www.chapterthree.com
Thanks a bunch, Greg! Off to
Thanks a bunch, Greg! Off to test! Edit: Works like a charm!
Per André Rønsen | Front | Twitter: @perandre
How did you even get the
How did you even get the linode stackscript to work?
I tried both of the Pantheon one's and neither of them did anything. It never sent an email that it was finished (even after linode dashboard showed task was complete), and I was not even allowed to ssh into the server. A linode employee checked it out and said that the ssh connection was being closed/rejected by the server (and not my local machine).
Linode
Hi,
the stack script works fine! But you are right: The email never gets sent, and the user you create with the script must be created again (see the linode docs). Login as root, and you are good.
Let me know if you need more assistance, and I can post my full workflow (we've used the script several times).
Per André Rønsen | Front | Twitter: @perandre