While attempting to run varnish, I am getting the following error.
Recieved status code 11 running status. Full response text: Resource temporarily unavailable
/sites/all/modules/varnish$ varnishd -V
varnishd (varnish-3.0.2 revision 55e70a4)
Copyright (c) 2006 Verdens Gang AS
Copyright (c) 2006-2011 Varnish Software AS
drush -cc
clear all cache gave the following error message
WD varnish: Socket error: Resource temporarily unavailable [error]
cache_bootstrap(variables) was not cleared. APC cli uses a different memory storage then the webserver. For [warning]
more info see: http://drupal.org/node/1278232
WD varnish: Socket error: Resource temporarily unavailable [error]
WD varnish: Recieved status code 11 running ban req.http.host ~ default && req.url ~ "/". Full response [error]
text: Resource temporarily unavailable
Comments
Comment #1
jghyde CreditAttribution: jghyde commentedI received the same error on a new installation with Drupal 7 and Varnish 3. In addition, I cannot log in at http://example.com/user/login. But I can log in at http://example.com/?q=user/login. The same goes for other forms. The Drupal path works, but not with clean urls.
On the "Net" tab on Firefox, it indicates that the result page, after attempting to login at user/register (clean URL), the site was returning a 404.
Drush cc all gives the same error. Although, the second cache clear did not.
Comment #2
jghyde CreditAttribution: jghyde commentedI figured this out, so I'll leave it here in case someone googles it.
This was a migration of a Drupal 7 site from the dev site to a production server. As such, I just dumped and then imported the database. This allowed me to override Drupal's Clean URLs check that you usually see when attempting to enable Clean URLs. So, the site was configured for clean urls, but mod_rewrite was not.
To solve, assuming you are awesome and using Ubuntu with Apache2,
Comment #3
vishy_singhal CreditAttribution: vishy_singhal commentedLet me check and revert back within a few days. I want to check across multiple servers that I have hosted at.
Comment #4
MiSc CreditAttribution: MiSc commentedClosing issues that had no activity the latest year, please re-open if the issues is still relevant.