CiviCRM Community Forums (archive)

Gary .. this is what is working for me at my host:

wget -O - -q -t 1 --post-data='name=nxxxxx&pass=xxxxxxx&key=xxxxxxxx http://usafnukes.com/administrator/components/com_civicrm/civicrm/bin/EmailProcessor.php

I have it running each night at 2 AM.

I couldn't get the CRON.PHP to run either .. so I'm running each process separately .

FYI I have a similar problem under 4.2.3 and Drupal 6.  The civicrm cron job runs fine until I enable the process_mailing job.  It still works fine if I run that job manually but it starts and never completes if run via CLI as a cron job.

Similar to you I found it works fine if I call it via wget or curl.

The error message when the CLI process dies is quite mysterious.  It gives an 'out of memory error' message with 47,000,000 bites of memory allocated. This is quite strange because I experimented with upping the memory limit in php.ini and via ini_set immediately before this error happened.  It would happily print "memory_limit=512M" or whatever, immediately before croaking with only 47M allocated.

This might be some restriction of our shared host (CiviHosting)--but it seems surprising if it is, because they allow us to edit the php.ini.  (php.cli takes a separate php.ini but I set it up with a custom php.ini, it seemed to take it, and still the same out of memory error.)

Also, somewhat related, many of the cron and api type jobs are memory hogs because of the pear  db_dataobject library.  It saves all sql queries and results in memory in case they are needed later . . . for some of the api type things, like running through every contact record in the DB to update something, saving all those query results in memory adds up fast.  See http://forum.civicrm.org/index.php?topic=2472.0