CiviCRM Community Forums (archive)

I recently upgraded from CiviCRM 4.2.7 to 4.3 and am now having a problem with the mailer.

Previously we had it so that every hour, when drupal's cron is run, it also runs the CiviMail cron to send messages.
The cron still exists, and according to the Scheduled Tasks page, the cron is properly being run every hour. However, no mails are being sent, and no errors appear in the log.

Oddly, when I manually run the task from that page, the mails go out. As it stands, right now I have to manually process the job every hour for it to work.
How can I get it to resume sending mails when the task is run automatically?

Thanks

Hi Lobo,

I checked all three of those permissions and they are all correct. They haven't changed since before I upgraded, when it was working fine. I just tested it again, and the cron job "runs" automatically, but no mails get sent.



---

Just to add something else that I just noticed -- when I run the scheduled jobs from a URL (by visiting http://[SITEROOT]/sites/all/modules/civicrm/bin/cron.php?name=username&pass=password&key=site-key), it works correctly and the mails send. It's only when I use the CiviCRM Cron Module for Drupal that the scheduled job runs without actually sending any mails.

Also, strangely, using a cron job to hit the URL (such as */5 * * * * wget -O /dev/null -q -t 1 "http://<domain>/sites/all/modules/civicrm/bin/cron.php?name=<name>&pass=<pass>&key=<key>") runs the cron, but does not mail anything, exactly like the Drupal module. Any idea why it only works when I hit the URL or manually execute them?

if the exact cron command runs via the brower but not via the cron tab, it basically means that civi is getting something different when sent via the cron tab

you might want to check the apache logs to see what the crontab is sending to the browser

finally might want to just wrap the cron line in a small sh/bash file and execute that file. Gives you a bit more control

if it still does not work, might be worth hiring someone to take a look. i suspect its a quick easy syntax-like fix

lobo

Hi Lobo,

Thanks very much. I think you're right, that sounds exactly like the problem.
I'll use your solution with the bash file for now until 4.3.4 gets released.

Thanks for your attention and rapid work on this problem!

I upgraded to 4.3.5 and our cron mailings failed with a memory error. 
After a moment of inspiration I copied my site php.ini into civicrm/bin and it looks like the mailings are going out OK now.
The cron cmd I use is
wget -O - -t 1 "<sitename>/sites/all/modules/civicrm/bin/cron.php?name=<user>&pass=<pass>&key=<civicrmkey>"

Hmm.  Almost every time I've done a civicrm upgrade I've had trouble getting the cron jobs to run afterwards.  I did use cli at some time in the past, I think cli worked for me with civi 3.4 and an earlier version of php, but not since civi 4 and the php upgrade.

This is what I tried with my current setup:

the same command that I used with drupal 6 and civi 4.2.8
wget -O - -t 1 "<mysite>/sites/all/modules/civicrm/bin/cron.php?name=<uname>&pass=<pass>&key=<key>"
Allowed memory size of 33554432 bytes exhausted (tried to allocate 77824 bytes) in sites/all/modules/civicrm/CRM/Contact/BAO/Query.php on line 1739

something else that had worked at some point in the past
cd public_html/sites/all/modules/civicrm; php -c bin/php.ini bin/cron.php name=<name> pass=<pass> key=<key>
Sorry, could not locate bootstrap.inc

the same cli command that I had used successfully prior to civi 4.2.8, with an older php
cd public_html; php sites/all/modules/civicrm/bin/cli.php -u <uname> -p <pass> -e Job -a execute
Fatal error:  cli.php can only be run from command line. in sites/all/modules/civicrm/bin/cli.class.php on line 82

I do not have ssh access unfortunately, my hosting provider is very security conscious.

The first command (wget) was successful after copying php.ini into civicrm/bin.  My php.ini has a memory limit of 1000M so I am guessing cron.php must use another php.ini somewhere which I have not found yet.

Anyway, my cron mail jobs were all processed successfully so I guess I'm good until the next upgrade.