CiviCRM Community Forums (archive)

Drupal 7.2 with CiviCRM 4.0 (will be upgrading to 4.0.2 this weekend). Using the default mail option and have gone through the relevant set up in Civi interface. Can send individual emails to users, have created two Cron jobs, have set up return path. Sending a test mailing to a group works fine also. When I schedule a mailing and choose 'send immediately' it sits on scheduled for a while and when cron kicks in goes from scheduled to running but never completes. I am unsure where to look for any possible error logs on this if there are any.

Another strange thing and possibly related, when I went to create a site Key there was already one in the settings file (is this supposed to auto generate in 4.0 ?). The cron jobs appear to run (at least changing from scheduled to running) so I guess this is ok right?

Ive spent a very long time reading documentation on all this to get the set up just right but maybe there is something i have missed, any light you could shed would be much appreciated.

Thanks for the reply xavier, the report is as follows

Intended Recipients   2
Successful Deliveries   0 (0.00%)
Tracked Opens   0
Click-throughs   0
Forwards   0
Replies   0
Bounces   0 (0.00%)
Unsubscribe Requests   0 (0.00%)
Scheduled Date   8th June , 2011 11:15 PM
Status   Running
Start Date   8th June , 2011 11:20 PM
End Date   

I tried running it manually from the browser but sent me to a blank page with no errors. I stumbled across another thread which sounded similar to my issue, turns out was permissions based all along. http://forum.civicrm.org/index.php?topic=15472.0
I added the civimail drupal account i made to adminstrator group and the tests went immediatley. Now I just need to change the permissions for that civimail role. Thanks for your assistance xavier

Hi,

It's expected ( it needs to put on hold potentially any contact)

Wondering if we shouldn't bypass the access rights altogether when running the cron.

X+

Not so happy for me. I'm on Drupal 7 and Civicrm 4.0.5.

I've created a user with admin privileges, and worked with the isp to add the cron job. When the cron starts it just sits there doing nothing and never completes, so we get multiple cron jobs backing up on each other.

I am sending out 2500 email via an external smtp, one at a time. Is this expected behaviour, or should the cron job just send a start to the database and then return, not sure how this should work?

As an aside I've also got a mailing showing 100% but still running. Che strano!
Thanks
Paul

Thanks Xavier,
I did as you suggested, and it returns to the command prompt directlly but I can't see any evidence of the job having started.

If, for example, a previous manually started send job has stalled, the running of the cron job doesn't restart it. Also the drupal watchdog table doesn't log any details of the job having starting.
Thanks
Paul