I have been seeing this more often than not and am wondering if anyone has had similar errors. I have a bunch of sites running with memcache and recently I have noticed this particular error:

Location:
http://www.example.com/httprl_async_function_callback?count=3

Message:
Notice: Undefined index: httprl_<token> in lock_release() (line 136 of /www.example.com/sites/all/modules/memcache/memcache-lock-code.inc).

Now, I know there have been issues in the past between the way the Memcache modules do their locking and this may be just a new version of that. I thought it worth mentioning as I dig into what may be going on and see if anyone else has seen this.

I am posting this here because I am not entirely sure which module is kicking the error out. https://www.drupal.org/node/2413657

Comments

Jeremy’s picture

Jeremy CreditAttribution: Jeremy commented
Issue tags: +7.x-1.6-blocker

It looks like there's a valid bug here in the memcache module. It seems to be triggered by the HTTP Parallel Request & Threading Library trying to free a lock that's already been freed, or was never set. However, the memcache locking code shouldn't throw a notice in this case. It should be an easy fix, tagging to fix before the next release.

ron_s’s picture

ron_s CreditAttribution: ron_s commented
Related issues: +#2413657: Notice: Undefined index: httprl lock_release memcache

Thanks Jeremy. I can confirm we're seeing this too.

Here's some additional information we posted on Shane's original HTTPRL thread: https://www.drupal.org/node/2413657#comment-9593447

erez111’s picture

erez111 CreditAttribution: erez111 commented

Thanks, I have the exact same issue like Jeremy described here.

Jeremy’s picture

Jeremy CreditAttribution: Jeremy commented
Status: Active » Fixed

Fix committed:
http://cgit.drupalcode.org/memcache/commit/?id=06e9348

  • Jeremy committed 06e9348 on 7.x-1.x 
    Issue #2413663 by Jeremy: Notice: Undefined index in lock_release()
erez111’s picture

erez111 CreditAttribution: erez111 commented

Hi Jeremy, thanks for the patch.

While enabling both memcache module & module "HTTP Parallel Request Library" (httpl),

Except error issue -
Does synergy of httpl + memcache decrease memcache performance?

Jeremy’s picture

Jeremy CreditAttribution: Jeremy commented

@erez11 I'm not sure I'm understanding your question. Are you asking if httpl will negatively affect memcache's performance? A quick glance through the code suggestions to me it will not. These two modules should be compatible.

erez111’s picture

erez111 CreditAttribution: erez111 commented

Thanks!

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

ron_s’s picture

ron_s CreditAttribution: ron_s commented
Status: Closed (fixed) » Needs work

I added this patch to our Memcache 7.x-1.5 code and it made no difference. Still receiving "HTTPRL - Core" error messages in our status report:

HTTPRL - Core	drupal_http_request()
Your system or network configuration does not allow Drupal to access web pages. This could be due to your webserver configuration or PHP settings.

[status] => Non-Blocking request sent out. Not waiting for the response.

The only way to fix this problem is disable Memcache locking by commenting out the following lines in our settings.php file:

$conf['lock_inc'] = 'sites/all/modules/memcache/memcache-lock.inc';
$conf['memcache_stampede_protection'] = TRUE;
glynster’s picture

glynster CreditAttribution: glynster commented

#4 worked a treated, can we have this committed in the next release please?

ron_s’s picture

ron_s CreditAttribution: ron_s commented

@glynster, the patch does not work. Maybe works in your scenario, but does not work with HTTPRL. Might want to review this thread: https://www.drupal.org/node/2413657

glynster’s picture

glynster CreditAttribution: glynster commented

@ron_s quite right I spoke too soon!

andsigno82’s picture

andsigno82 CreditAttribution: andsigno82 as a volunteer commented

following.

i have same, identical problem as #10

pribeh’s picture

pribeh CreditAttribution: pribeh commented

Same.

Jeremy’s picture

Jeremy CreditAttribution: Jeremy commented
Status: Needs work » Closed (cannot reproduce)

doesn't seem to be a problem any more, closing

ron_s’s picture

ron_s CreditAttribution: ron_s commented

I wouldn't say it's not a problem any more, just have moved on to other modules.