Closed (fixed)
Project:
Simplenews
Version:
5.x-1.2
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
8 Mar 2007 at 10:47 UTC
Updated:
15 May 2008 at 14:52 UTC
When I look in my admin log, I see a lot of messages saying that the cron run did not finish. But there is no indication of the reason for this. Could it be something to do with Simplenews? The news certainly seems to take a long time to get sent. I notice that when I run cron "by hand" it works fine, I don't get the "did not complete" message. Any ideas would be welcome...
Comments
Comment #1
IGadmin commentedI also am seeing the odd cron job not finishing when sending a simplenews newsletter. Some stats: my list is 3500+ people, and am throttling 100 mails per cron run. Am on Drupal 4.7.6.
Also, I'll occasionally see watchdog reporting multiple cron jobs executed per scheduled cron run, often 4-5 instances of cron time-stamped the exact same, reporting "cron run completed", when only ONE should have run. I'm unclear whether simplenews actually IS sending 100 emails for each one of these instances, even though it apparently THINKS it is, as it finishes sending to my 3500+ list earlier than expected.
Could use help with this, as my hosting provider throttles me to 1,000 emails sent an hour. When simplenews spits them all out faster than it should, as above, half my emails are quietly being throttled by my hosting provider, so the recipients never get them.
Comment #2
beginner commentedI confirm all the symptoms described above.
1300+ emails, and I tried sending 200 newsletter per cron run, which obviously is too much.
symptoms:
- "cron not completed" errors in the logs
- cron runs multiple times in the same minute, at the time it is supposed to run, even though is says it completed.
- users complain that they receive multiple copies of the newsletter.
This is actually a core problem that has been fixed in Drupal 5: cron could be run multiple times, causing troubles like this one. In Drupal 5, cron sets a flag that prevents multiple runs of cron.
I am going to upgrade to D5, now and I guess everybody using simplenews.module should do the same.
It's not something that can be solved with this module.
leave this issue open until Drupal 4.7 is no longer supported, so that people can find it.
Comment #3
beginner commentedActually, I have found that cron is actually running twice every hour instead of once. There is another problem going around.
Also, what may be relevant is the cron script you use. I am using
scripts/cron-lynx.sh. And you?Comment #4
IGadmin commentedEvery 10 minutes, I'm invoking a cron job using the following:
/usr/bin/wget -O - -q http://[ip address, removed for security]/cron.php
Should I be running the script directly from the script folder? If so, what's the right syntax?
Comment #5
beginner commentedmy comment #3 is not relevant. I since found out that my host had somehow duplicated the cron job, making it run twice. The duplicate has been removed and now everything is ok.
IGadmin: you use Drupal 4.7, right? This is a core problem: upgrade to D5.
Or do ALL of the following:
1) run cron less often (once per hour is enough),
2) send much fewer emails per run (50?)
and
3) make sure cron is never run twice at the same time.
Comment #6
Tigerhuli commentedTry to check your system time!
I solved the similar problem by correcting the server system time, which was way off.
Comment #7
Taekyon commentedI have the same problem with a newsletter on a drupal 5.7 site. Some people receive up to four copies of the newsletter. Others just one.
Cron is handled by poormanscron. Could that be (part of) the problem?
Comment #8
sutharsan commentedThe problem is usually a cron overrun. The previous cron job is not finished before a new one is started. Decrease the number of newsletters per cron job or a bigger interval between the jobs.
Comment #9
sutharsan commentedI will to add some instructions on this subject in the documentation.
Comment #10
sutharsan commentedREADME.txt now contains this instruction:
Comment #11
sutharsan commentedComment #12
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.