Email notification on every cron run when module updates are available

I have the same problem.

I have the same problem.

Same problem too.

I removed my email for notifications but obviously I have to check for updates manually.
When I put it back my email I get the notifications again every five minutes or so.

I am not sure if the issue was there under the 6.5 version. Right now I have the 6.6 version.

I just checked my logs.
The cron is supossed to run by its defaults values every 60 minutes and retry in case of error every 10 minutes.

However in my logs the cron runs exactly every five minutes: admin/reports/dblog (filter: "cron").

Checking the machine producing the cron to run it gives me an IP 75.101.228.155 which corresponds to Amazon.com

Do you have the amazon module on your systems?

Perhaps this issue it has something to do with that.

I created a support request in amazon module queue:
http://drupal.org/node/329862

Garnerin,

See if you can check your logs, as I did.
If you have an IP machine running every five minutes, with an ip lookup webpage like http://ip-lookup.net/ perhaps we can shed some light on this issue.

I haven't amazon module too

I had the cache enable here:
http://YOURWEBPAGE/admin/settings/performance

It runs every 5 minutes.
I changed to 15 minutes but still I got the same notifications every five minutes (not entirely tested).

I disabled the cache and the messages are not coming anymore.

Could it be the case for you too?

I've got the same issue. No Amazon module. Poormanscron set to run every hour. Cron runs every five minutes by the same IP address (75.101.228.155).

same as #13.

The courious thing with that IP is that it corresponds to Amazon.
See for yourself introducing the IP here:
http://www.arin.net/whois/

Garnerin,
sorry I cannot be more helpful. I re-read your first post and I was under the same symptoms.

We will need somebody more technical taking a look at this.

Also experiencing the same problem

The cron.php request probably comes from Acquia'a AWS server. Did you download the Acquia package ?

In my case I did not have acquia either (only mollom).

Alains message gave me an idea: I decided to download acquia and let him administer cron...and it worked!
I do not get the notification mails anymore every five minutes. I just get only one.

I do not know if this issue is produced by poormanscron or is something else.
Perhaps others can try acquia and see if it works for them.

Acquia.com will only be pinging your site if you (or someone) signed up for a subscription or a trial subscription and entered your site URL (or IP address).

Also, if you have an Acquia subscription, you can turn off the cron service by logging in to acquia.com, clicking on your subscription name in the Site Selector menu, then "Settings", then "Cron"...

However, I think it's clear from the original bug report that this is something which occurs independently of whether it's Acquia running cron for you or not. (Acquia's default cron interval is 5 minutes, though - so obviously the bug will be a lot more annoying if you are running cron that often :)

I just turned e-mail notification on and I noticed I'm having the same problem.
I run cron every 30 minutes and notifications are coming each time.
I do not have Acquia, it's surely coming from Drupal itself.

Also, I must mention, that not only notification comes with each run of cron, but also the event log (on admin/reports/dblog) shows for EACH run of cron that the information about updates has been collected! Also when I run cron manually, there is check for updates!

Regardless I set it (on admin/reports/updates/settings) to weekly or daily, whether there should be an e-mail notification or not, Drupal is always checking for updates with each cron run.

If we can find the problem and fix it, the change will have to happen first for Drupal 7.x

That being said, here's what I've collected about how drupal is handling sending the emails.

 // cron.php
if (isset($_GET['cron_key']) && variable_get('cron_key', 'drupal') == $_GET['cron_key']) {
  drupal_cron_run();
}

Notice how that if statement above is checking for a cron_key. This cron_key is designed to keep remote sites from running your cron for you (that should alleviate some concerns). That is from D7, so not sure if D6 has this particular convention.

 // drupal_cron_run() is found in includes/common.inc
module_invoke_all('cron');

That function above makes sure we aren't running more than one cron.php instance at a time. And then it calls "module_invoke_all()" which will invoke the update module's cron funtion...

 // update_cron.php from update.module

/**
 * Implementation of hook_cron().
 */
function update_cron() {
  $frequency = variable_get('update_check_frequency', 1);
  $interval = 60 * 60 * 24 * $frequency;
  // Cron should check for updates if there is no update data cached or if the configured
  // update interval has elapsed.
  if (!cache_get('update_info', 'cache_update') || ((REQUEST_TIME - variable_get('update_last_check', 0)) > $interval)) {
    update_refresh();
    _update_cron_notify();
  }
}

If you read those lines above correctly, this function is enforcing the variable "update_check_frequency." The default setting is 1 day, but it also enforces an update if the cache_get() functions return "false." (meaning cache has not been created). So that's where our bug lives, if it exists at all.

Hope that helps.

Josh

Moving to the proper queue. The update system relates to update.php, while update.module is the "available updates" page, etc.

I think this is yet another symptom of #220592: Core cache API breaks update.module: fetches data way too often, kills site performance, etc.