A few days(?) ago my cron stopped running properly. I narrowed dow the problem to radioactivity_process_memcached_entries() where my $start_entry_id == 0 and $stop_entry_id == 381701...

I'm not sure exactly what this number is, but I recognize that it is large. If it corresponds to a nid ... I would suspect that this error may be related to having a database setup with non-sequential serialized nids. In my case, my nid's are 10,20,30,40,50,60,70,80,90,100,110 ... (not under my control)

In any event ... this breaks my cron so I have had to comment out this line:

function radioactivity_cron() {
  if (radioactivity_get_memcached_enable()) {
    //radioactivity_process_memcached_entries();
  }
...

the error I receive is this:

Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 71 bytes) in /data0/home/httpd/h.astrology.com/htdocs/lifegoesstrong/current/public/sites/all/modules/contrib/memcache/dmemcache.inc on line 99

clearly 128mb or memory should be enough ...

Ideas?

Comments

bleen’s picture

bleen commented

this is how I figured out what module was causing the memory problem .. in case someone finds this...

http://www.bleen.net/blog/debugging-memory-problems-during-cron-run

techgirlgeek’s picture

techgirlgeek commented

I was getting this error as well. Make sure your memcache is using the most recent contrib module. No matter what settings I would set in memcache or upped memory, I would continue to get these errors. After I updated the memcached contrib module the error disappeared and my memcached hit percentages increased.

Hope this helps.

sutharsan’s picture

sutharsan commented
Issue summary: View changes
Status: Active » Closed (outdated)

Issue triage: Closing issue, the 6.x branch is no longer maintained.

If you believe this issue is closed in error, feel free to re-open.