running pressflow6 + varnish3b, frequently but not always,

> drush @testsite up

...
Code updates will be made to the following projects: PHPMailer [phpmailer-6.x-3.1], Views [views-6.x-3.x-dev]
Note: A backup of your project will be stored to backups directory if it is not managed by a supported version control system.
Note: If you have made any modifications to any file that belongs to one of these projects, you will have to migrate those modifications after updating.
Do you really want to continue with the update process? (y/n): y
Project phpmailer was updated successfully. Installed version is now 6.x-3.1.
Project views was updated successfully. Installed version is now 6.x-3.x-dev.
No database updates required                                                                              [success]
WD varnish: Recieved status code 101 running purge req.http.host ~ www.testsite.loc && req.url ~ ^/. Full[error]
response text: Unknown request.
Type 'help' for more info.
'all' cache was cleared                                                                                   [success]
Finished performing updates.                                                                              [ok]

> drush @testsite up

No code updates available.                                                                                [ok]

unclear if that ERROR is a fatal problem or not.

Comments

fabsor’s picture

fabsor commented
Issue tags: +Varnish 3

Tagging this with varnish 3

fabsor’s picture

fabsor commented

I have created a generic issue for varnish 3 support. Have a look at #1179964: Support for Varnish 3.x

_-.’s picture

_-. commented

i'm able to reproducibly cause the reported error; unclear whether it's the ONLY way to cause it.

drush cc
	Enter a number to choose which cache to clear.
	 [0]  :  Cancel
	 [1]  :  all
	 [2]  :  theme-registry
	 [3]  :  menu
	 [4]  :  css-js
	 [5]  :  block
	 [6]  :  module-list
	 [7]  :  theme-list
	 [8]  :  nodeaccess
	 [9]  :  views
	...

drush cc theme-registry
	'theme-registry' cache was cleared                   [success]
drush cc menu
	'menu' cache was cleared                             [success]
drush cc css-js
	'css-js' cache was cleared                           [success]
drush cc block
	'block' cache was cleared                            [success]
drush cc module-list
	'module-list' cache was cleared                      [success]
drush cc theme-list
	'theme-list' cache was cleared                       [success]
drush cc nodeaccess
	'nodeaccess' cache was cleared                       [success]
	Content permissions have been rebuilt.               [status]
drush cc views
	'views' cache was cleared                            [success]

but,

drush cc all
	WD varnish: Recieved status code 101 running purge req.http.host ~ www.testsite.loc && req.url ~ ^/.    [error]
	Full response text: Unknown request.
	Type 'help' for more info.
	'all' cache was cleared                              [success]

iiuc, 'drush cc all' _should_ be the equivalent of running all of the other commands. apparently, there's a difference.

mrded’s picture

mrded commented
Version: 6.x-1.x-dev » 7.x-1.x-dev

Same error on Drupal 7

# drush cc all
WD varnish: Recieved status code 101 running ban req.http.host ~ default && req.url ~ "/". Full response    [error]
text: Unknown request.
Type 'help' for more info.


WD varnish: Recieved status code 101 running ban req.http.host ~ default && req.url ~ "/". Full response    [error]
text: Unknown request.
Type 'help' for more info.


'all' cache was cleared                                                                                     [success]
dan_lennox’s picture

dan_lennox commented

I reproduced this as per #3 with Drupal 7, however only when my Varnish version was incorrectly set at admin/config/development/varnish

Apologies if your settings are correct, but just based on this it might be worthing double checking your Varnish version setting.

bibo’s picture

bibo commented
Version: 7.x-1.x-dev » 7.x-1.0-beta1
Status: Active » Closed (fixed)

@mrded

Version: 6.x-1.x-dev » 7.x-1.x-dev
Same error on Drupal 7

I thought I found out the same, that Varnish 3 would in some cases generate this error. Like when using cache_actions: "Clear a specific cache cid" -> cache page. Turns out varnish.cache.inc in the latest recommended release ( 7.x-1.0-beta1) still has this bug, making that version not fully Varnish 3 compatible.

It was fixed with a simple oneliner like a month after that release:
http://drupalcode.org/project/varnish.git/commitdiff/51f66150291d06f5d279d4c08808fd431dc9f615?hp=bd19eb5e62dc21b33a9dd53ccbb4c5a5d68f99fa.

So, for 7.x-1.dev this is really fixed. But IMO this bug should be stated on the front page of the module until there is a new recommended release (fabsor?).

Solution for now: use the dev version.

sylvain lecoy’s picture

sylvain lecoy commented
Version: 7.x-1.0-beta1 » 7.x-1.x-dev
Status: Closed (fixed) » Needs work

Still happening in -dev version.

drush cc all throws this error.

Ravenight’s picture

Ravenight commented
Status: Needs work » Closed (fixed)

Check your varnish version at admin/config/development/varnish. I had this error until I changed the version to 3.x.

sylvain lecoy’s picture

sylvain lecoy commented
Status: Closed (fixed) » Needs work

I am currently in 3.x as well.

sylvain lecoy’s picture

sylvain lecoy commented

Ok actually, this is fixed.

sylvain lecoy’s picture

sylvain lecoy commented
Status: Needs work » Closed (fixed)
pyxio’s picture

pyxio commented

Greetings,

Can you please explain how this is fixed before closing an issue? I have the same problem and I am glad it is fixed but how do I fix it? Thanks.

sylvain lecoy’s picture

sylvain lecoy commented

For me, it was because the feature reverted the variable to 2.x, thus drupal could not contact Varnish server. Switched back to 3.x, it fixed the issue.

pyxio’s picture

pyxio commented

Yes. that worked for me too. Cheers

Pedja Grujić’s picture

Pedja Grujić commented

Is there a way to set version by default?

I am running into similar issue on a multiple server setup, every time we deploy a fresh copy and enable varnish via drush it defaults to version 2.

Wonder if there is a way to set version in settings.php and have it persist across multiple servers.

EDIT

To set version by default just add following to your settings.php

$conf['varnish_version'] = 3;

ressa’s picture

ressa
he/him
commented

After re-installing Varnish and running a drush up, I got this error
WD varnish: Recieved status code 0 running ban req.http.host ~ && req.url ~ "/". Full response text: Success.

You can find the secret Varnish code with this command:
sudo cat /etc/varnish/secret