i'd originally posted this @

"Varnish module, latest dev, gives "Socket Error" with Varnish versions < 2.1 (needs documentation)"
http://drupal.org/node/859116#comment-3582138

but a comment there suggested,

#33 Posted by DamienMcKenna on October 18, 2010 at 9:36am
@dev001: I think that's a different problem, please open a new issue.

so ...

i'm running,

varnishd -V
varnishd (varnish-2.1.3 SVN 5049:5055)
Copyright (c) 2006-2009 Linpro AS / Verdens Gang AS

built from src (varnish-2.1.3.tar.gz) tarball, on openSUSE 11.3 x86_64.

with latest varnish module -dev,

drush pm-list | grep -i varnish
Caching Varnish (varnish) Module Enabled 6.x-1.x-dev
grep Id ./sites/all/modules/varnish/varnish.info
; $Id: varnish.info,v 1.2 2010/05/04 16:08:53 joshk Exp $

and, i've applied the patch from "#23",

http://drupal.org/comment/reply/859116/3502726#comment-3502726

still, at 'first' use of 'drush up', i see,

drush up
...
No code updates available. [ok]
No database updates required [success]
WD varnish: Socket error: Resource temporarily unavailable [error]
WD varnish: Socket error: Resource temporarily unavailable [error]
WD varnish: Recieved status code running purge req.http.host ~ www.devsite.loc && req.url ~ ^/. Full [error]
response text:
'all' cache was cleared [success]
Finished performing updates. [ok]

then, at an _immediately_ subsequent,

drush up
...
No code updates available. [ok]
No database updates required [success]
'all' cache was cleared [success]
Finished performing updates. [ok]

Comments

Anonymous’s picture

Anonymous (not verified) CreditAttribution: Anonymous commented

subscribe

fabsor’s picture

fabsor CreditAttribution: fabsor commented

Hi!

How are your servers configured? Is your varnish server located on a different machine, and does it take a long time to connect to it? If so, there could be a problem with the varnish connect timeout time.

Are you connected if you connect to your varnish server if you go to varnish configuration page?

Drush is ran in php cli which usually has a different configuration. Can you use varnish to for instance download modules?

_-.’s picture

_-. CreditAttribution: _-. commented

> Is your varnish server located on a different machine

nope. same machine as my drupal/webserver

> and does it take a long time to connect to it? If so, there could be a problem with the varnish connect timeout time.

nope. i've no noticeable problems whatsoever with my varnish setup, except for this reported issue.

> Are you connected if you connect to your varnish server if you go to varnish configuration page?

> Drush is ran in php cli which usually has a different configuration.

the cli & web configs are virtually identical ...

> Can you use varnish to for instance download modules?

yes, download is fine.

msprunck’s picture

msprunck CreditAttribution: msprunck commented

I resolved the problem by replacing this line from varnish.module:

socket_set_option($client, SOL_SOCKET, SO_RCVTIMEO, array('sec'=>0, 'usec'=>50));

by

// Set a sensible socket timeout.
$timeout = variable_get('varnish_socket_timeout', 250); // Timeout in micro-seconds.
socket_set_option($client, SOL_SOCKET, SO_SNDTIMEO, array('sec' => (int)($timeout / 1000000), 'usec' => $timeout % 1000000));
socket_set_option($client, SOL_SOCKET, SO_RCVTIMEO, array('sec' => (int)($timeout / 1000000), 'usec' => $timeout % 1000000));

_-.’s picture

_-. CreditAttribution: _-. commented

hi.

i made the changes as you'd reported/suggested.

but, after clear/restart/boot, @

drush up

i'm still seeing,
...
No code updates available. [ok]
No database updates required [success]
WD varnish: Socket error: Resource temporarily unavailable [error]
'all' cache was cleared [success]
Finished performing updates. [ok]

Alex Andrascu’s picture

Alex Andrascu CreditAttribution: Alex Andrascu commented

subscribe. i got that too

MiSc’s picture

MiSc CreditAttribution: MiSc commented
Status: Active » Closed (won't fix)

As a part of a clean up of the issue queue for the varnish module I am closing tickets that had no activity for the last year, please feel free to re-open if needed.