Cron was not returning and getting stuck with the cron_semaphore variable left behind. I added a cron logging snippet to module_invoke_all and discovered that it was breaking on ad_cache_memcache.

I disabled this component of the ad module, deleted cron_semaphore and cron.php ran sucessfully, both manually and

The history of this bug is documented in the forums: http://drupal.org/node/382682

The server with this issue is http://www.weavezinedev.com and I would be happy to help you research this issue. This is a new site, and I've kept a changelog of all the modules I've installed, what order, what versions, and summary details about content added and other configuration steps.

I really like the Advertisement module. I picked it after trying Openx and GoogleAds and found it just perfectly met my needs in terms of exactly all the functionality I wanted and nothing I didn't. Thank you for all your work on it, and if I can help you track down what's going on with this issue, just let me know.

Thanks!

Comments

WeaveGeek’s picture

WeaveGeek commented

PS: That one sentence should read: I disabled this component of the ad module, deleted cron_semaphore and cron.php ran sucessfully, both manually and via an automated crontab.

Also, I was able to toggle the repro on this bug by enabling and disabling ad_cache_memcache. I went through the process a couple of times and each time ad_cache_memcache was enabled cron got stuck, each time it was disabled (and the corn_semaphore deleted) cron ran just fine (many times.)

jeremy’s picture

jeremy commented
Category: bug » support

Are you using memcache to serve advertisements? The ad_cache_memcache module is difficult to configure and is not recommended unless you know what you're doing. Do not simply enable all ad modules, only enable the ones that you are using. I recommend you use the ad_cache_filecache instead if possible, as it is much easier to get working.

jeremy’s picture

jeremy commented
Status: Active » Postponed (maintainer needs more info)
WeaveGeek’s picture

WeaveGeek commented

I have disabled ad_cache_memcache and that solved my cron problem. I am a new Drupal user, but do make every effort to enable only those portions of a module that I know I need. Sometimes it's hard to tell which those are. Is there any documentation about how to properly use ad_cache_memcache and/or ad_cache_filecache? What I found in the Documentation link off the Ad project page was pretty minimal.

Also, if having both enabled at the same time causes trouble, would it be possible to put in a toggle so you could only enable one at a time? Or set a precedence so that if both were enabled, the simpler/safer option would win?

Just a thought.

As I said, my issue was solved by disabling ad_cache_memcache, I just reported this to be a good Drupal citizen. I spent two days trying to figure out what was going on before someone tipped me off to cron logging and I was trying to save someone else from going down the same path.

Cheers!

P.S. I tried signing up for the Ad email newsletter, but haven't received anything from it yet.

jeremy’s picture

jeremy commented
Status: Postponed (maintainer needs more info) » Fixed

Yes, the ad_cache memcache module is removed in 6.x-2.x. It will be re-written as an external project, as too many people blindly enable it without trying to understand what it's for.

Status: Fixed » Closed (fixed)

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