CiviCRM Community Forums (archive)

I have recently discovered a weird (for me) issue with my setup of:

+ Joomla 2.5.14
+ CiviCRM 4.3.4
+ CiviMail
+ cron job

I had setup an every 15 mins cli executed cron job that appeared to work just fine and it would trigger the CiviMail job to flush mailer items.

Suddenly (yeah I know - wish I could pinpoint what changed), the following situation seems to occur:

I create a new CiviMail mailing that I submit for immediate sending.
I verify that after I submit such a mailing:

+ the Mailing appears to be submitted and scheduled in the Scheduled and Sent Mailings panel of civicrm
+ the scheduled date/time stamp appears correct
+ the status is scheduled
+ the Start/Completed dates are empty
+ a new row is create in the civicrm_mailing_job table with: scheduled_date information correct (same as civicrm shows), status = scheduled, NULL values for start_date/end_date columns

When the cli cron job is executed I see the following:

+ the civicrm scheduled and sent panel shows status of this job as running
+ the civicrm panel also shows start date/time as the time that the cron job was executed
+ the database table has an extra child row linked to the previously created row

I have replicated the two relevant database rows below:


id: 194
mailing_id: 89
scheduled_date: 2013-11-01 10:26:26
start_date: 2013-11-01 10:30:02
end_date: NULL
status: Running
is_test: 0
job_type: NULL
parent_id: NULL
job_offset: 0
job_limit: 0

id: 195
mailing_id: 89
scheduled_date: 2013-11-01 10:26:26
start_date: NULL
end_date: NULL
status: Scheduled
is_test: 0
job_type: child
parent_id: 194
job_offset: 0
job_limit: 8

and the items are never emailed, the job just stays at running status forever.

Any thoughts on what the cause may be or how I can further debug this?\

Hi Donald!

I added a

var_dump($query);

to line 110 of CRM/Mailing/BAO/Job.php

and the results are:

string(562) "
      SELECT   j.*
        FROM   civicrm_mailing_job     j,
           civicrm_mailing m
       WHERE   m.id = j.mailing_id AND m.domain_id = 1
                     AND m.sms_provider_id IS NULL
         AND   j.is_test = 0
         AND   ( ( j.start_date IS null
         AND       j.scheduled_date <= 20131103190506
         AND       j.status = 'Scheduled' )
                OR     ( j.status = 'Running'
         AND       j.end_date IS null ) )
         AND (j.job_type = 'child')
         AND    ( 0 )
      ORDER BY j.mailing_id,
           j.id
      "
string(566) "
      SELECT   j.*
        FROM   civicrm_mailing_job     j,
           civicrm_mailing m
       WHERE   m.id = j.mailing_id AND m.domain_id = 1
                     AND m.sms_provider_id IS NOT NULL
         AND   j.is_test = 0
         AND   ( ( j.start_date IS null
         AND       j.scheduled_date <= 20131103190506
         AND       j.status = 'Scheduled' )
                OR     ( j.status = 'Running'
         AND       j.end_date IS null ) )
         AND (j.job_type = 'child')
         AND    ( 0 )
      ORDER BY j.mailing_id,
           j.id
      "

nick:

i suspect this is due to the acl changes we made in 4.4.0 (and which i think u patched)

i'll take a look and analyse this later today / befor 4.4.1 is released

thanx

lobo

2 questions:

a. what user are you running with cli?

b. does the mailing send when you run it via the url:

http://HOSTNAME/administrator/?option=com_civicrm&task=civicrm/mailing/queue&reset=1

lobo

since we want 4.4.1 out, i'm thinking of rolling back my changes so WP/Joomla wont have civi acls working for now (which was the status quo prior to 4.4 anyway). this seems like a bigger can of worms than i expected

lobo

we'll need someone who's familiar with joomla internals to help fill out some of the stub functions in CRM/Utils/System/Joomla.php

specifically, the loadUser aspect of things. It will need to work for both 2.5.x and 3.x.

lobo