Closed (fixed)
Project:
Memcache API and Integration
Version:
7.x-1.x-dev
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
11 Dec 2010 at 20:48 UTC
Updated:
30 Sep 2011 at 06:51 UTC
Jump to comment: Most recent file
Comments
Comment #1
jeremy commentedWhat version of the memcache module are you using? You've assigned this against 6.x-1.x-dev, but the latest version of the has only one increment on line 297. Perhaps try updating to the latest snapshot?
Comment #2
alfthecat commentedI'm having the same issue. Using version 1.7 of Memcache.
I found this post that removed the error from the hosts page but cron is failing to run. When I trigger it, the error returns:
Fatal error: Call to a member function increment() on a non-object in /home/[...]/public_html/sites/all/modules/memcache/memcache.inc on line 262
I'm using a pressflowed instance of Drupal 6.19
Comment #3
ghankstef commentedJust to provide a little more info - I am also seeing this when running pressflow 6.20, memcache 6.x-1.7 , or even memcache 6.x-1.8 and ubercart and the error occurs right at the moment of completing a transaction.
I also get it with pressflow 6.20 and memcache 6.x-1.7 while running `drush cc all` or `drush updatedb` from the command line.
Downgrading to memcache 6.x-1.6 seems to take care of the issue.
Comment #4
alfthecat commentedHi ghankstef, thanks for that info, I'll try downgrading to 1.6!
Comment #5
igorik commentedDowngrade to 1.6. fix the error, thanks for this.
Comment #6
ryan_courtnage commentedduplicated with 6.x-1.8. Clearing cache on Drupal's "performance" page also causes the problem.
using memcached-1.4.5-1.el5 on CentOS 5.5
Comment #7
brunodboSimilar problem here with version 6.x-1.8 of memcache module (when doing a 'drush cc all' or emptying the cache on /admin/settings/performance):
*But* I only get it when adding 'cache_page' => 'none' to the memcache_bins array.
So this works fine:
While this doesn't (throws the PHP error when clearing the cache, as mentioned above:
ps: Misspelling 'cache_page' => 'none' as 'cache_pages' => 'none' also works, that's how I found out :)
Comment #8
brunodboThis is still an issue in the latest dev snapshot (error happens on line 297 there though).
Comment #9
valthebaldQuick patch (against 6.x-1.8)
Comment #10
valthebaldComment #11
catchThis looks like a sensible check to me, wondering if we should consider logging when dmemcache_object() fails, but the patch in itself is fine. Committed to 6.x-1.x, this may need commit to 7.x as well.
Comment #12
valthebaldSorry for late reply:
I think that watchdogging this kind of failure is the right thing to do.
Comment #13
catchThis doesn't really apply to the 7.x branch, marking fixed.