CiviCRM Community Forums (archive)

When I run this command from the command line:

wget 'http://my.org/sites/all/modules/civicrm/bin/civimail.cronjob.php?name=XXXX&pass=XXXX&key=XXXX'
... it changes the status of my scheduled mailing to 'Running', but no messages are sent. The mailing gets stuck and never completes.

To send the mailing, I have to run it manually using "http://<my.org>/civicrm/mailing/queue&reset=1", which sends the messages and changes the status to 'Complete'.

What am I doing wrong? Unfortunately, my server doesn't support cli, so I must use the webserver. I'm using Bluehost. I know it's a budget host, but CiviMail was working perfectly until I upgraded to 3.2.4, which broke the auto-mailer (or exposed a flaw in my configuration).

Thanks,
James

I'm seeing the same thing with CiviCRM 3.3.0.

Hmmm, I don't think this will help jimmyjam, but in 3.3.0 the issue sees to be with the child jobs:

mysql> select * from civicrm_mailing_job where mailing_id = 43;
+----+------------+---------------------+---------------------+----------+-----------+---------+----------+-----------+------------+-----------+
| id | mailing_id | scheduled_date      | start_date          | end_date | status    | is_test | job_type | parent_id | job_offset | job_limit |
+----+------------+---------------------+---------------------+----------+-----------+---------+----------+-----------+------------+-----------+
| 87 |         43 | 2010-12-10 10:20:01 | 2010-12-10 10:21:13 | NULL     | Running   |       0 | NULL     |      NULL |          0 |         0 |
| 88 |         43 | 2010-12-10 10:20:01 | NULL                | NULL     | Scheduled |       0 | child    |        87 |          0 |         0 |
+----+------------+---------------------+---------------------+----------+-----------+---------+----------+-----------+------------+-----------+
2 rows in set (0.00 sec)


The parent job is running but the child job is merely scheduled.  You can run the cron job many times but this doesn't change...  :-(

Doing the queue reset that jimmyjam suggests causes delivery to happen and for both parent/child to be marked as "Complete".  However, trying to delete the mailing fails with a foreign key issue, since the delete process seems to try to delete the parent before the child.  If I manually delete the child from the DB then I can delete the mailing through CiviCRM.  Oh, and I'm only trying to delete the mailing because it is a test...  ;-)

hey martin:

the civicrm/mailing/queue calls the same function as the cron job. so a bit curious as to why the cronjob does not put the child job in running status and run the jobs. We (and emotive) have tried this on our local servers and all seems fine

can you debug the cronjob script and see what is happening and why. ping us on irc if u need help getting started

lobo

The delete issue has two reason:

1. There is a bug in the upgrade script. We'll fix this in the 3.3.2 release

2. There is also a bug in mysql which is triggered in some releases (not in your  case)

http://bugs.mysql.com/bug.php?id=57255

Not a lot we can do if folks hit this bug

lobo

try the patch mentioned here:

http://forum.civicrm.org/index.php/topic,16569.msg72549.html#msg72549

lobo

OK, it looks to be about permissions.

CRM_Mailing_BAO_Job::runJobs() is the only function in Job.php that uses  {$mailingACL} in the query.  Some of the other functions set $mailingACL but do not use it.

If I remove that part of the query then the job runs to completion but no mail is sent.

I'm using an unprivileged user to run the cron jobs.  This has worked previously, although I may have hacked the cron script to say CRM_Utils_System::authenticateScript( false ) .  That doesn't seem to make a difference in this case... I just tried it.

Has security been improved so that only users with a particular CiviCRM permission can run the mail cron job?  If so, what are the minimum permissions I need to assign to the user that runs the cron job?

Note that I can still run the UpdateMembershipRecord.php cron job as an unprivileged user (and I like it that way  )...

Is there a workaround for folks stuck with a big mailing to go out? I've tried running mailing/queue?reset=1 but nothing happens...

Any help you could provide would be greatly appreciated!

Thanks so much, Lobo. Now forgive my ignorance, but how do I apply it?