Cron Job Error after 4.3.1 install

[Studio136]

I'm running Civi under Joomla 2.5.10 and just upgraded Civi from 4.2.9 to 4.3.1.  After the upgrade, which went through without a problem, I started receiving emails everytime my Cron job ran with the following message.

Warning: mysqli_ping(): Couldn't fetch mysqli in /home/integrat/public_html/libraries/joomla/database/database/mysqli.php on line 190

My cron job is set up the following way and worked fine prior to the 4.3.1 upgrade (even after the 2.5.10 upgrade).

/usr/local/bin/php /home/integrat/public_html/administrator/components/com_civicrm/civicrm/bin/cli.php -j -u <<username>> -p <<password>> -e Job -a execute

Thanks.

[Hershel]

I have the same problem on a Joomla site. Changing the connect strings from mysql to mysqli (long shot anyway) didn't help.

[helenbn]

Same problem with multiple sites.
J 2.5.11
Civi 4.3.1

[helenbn]

Changing the mysqli to mysql fixed the problem but created warnings within Joomla because other things need the mqsqi.

I really need this cron to work. 

[Hershel]

Changing the mysqli to mysql fixed the problem

Yes, for me also changing to mysql in Joomla's configuration.php file fixed the cron issue.

[helenbn]

I need a different fix because I have other things within Joomla that needs the sqli.

Any ideas??

[helenbn]

Upgraded to 4.3.2. No more error but cron does not actually run according to joomla civicrm scheduled jobs.

Close, but no cigar!

[Studio136]

I upgraded to 4.3.3 and it is back again.  I'm in the same position as helenbn, I can't turn off MySQLi because other components need it.  It sounds to me like this is a bug to be reported, am I mistaken?

[Donald Lobo]

Yes, seems like a bug and should be investigated.

Dan/Helen: can one of you investigate and figure out whats happening and why, we can help u get started on irc

lobo

[pratik.joshi]

Hello,

I tried the following:
1) Configured 3 schedule jobs namely : cleanup, send_reminder and process_mailing and set them active.
2) Ran the cli script for executing the above jobs :
        php /home/path_to_joomla_site/administrator/components/com_civicrm/civicrm/bin/cli.php -u admin -p admin -e Job -a execute
3) I got the PHP Warning :
        PHP Warning:  mysqli_ping(): Couldn't fetch mysqli in /home/path_to_joomla_site/libraries/joomla/database/database/mysqli.php on line 190

4) But the jobs mentioned in #1 ran successfully.

I did a bit of investigation for this warning and found :
1) This warning occurs when the php method mysqli_ping tries to access closed connection object as parameter -
        this method calling is done by joomla to check weather the connection is active or not;

2) However, this closed connection object is being accessed while joomla calls session destruct method after the civi job execution has been completed.
3) So, as per me, the schedule jobs execution will not be affected.

I used Joomla 2.5.11 with civicrm 4.3.3 and also on civicrm 4.3 git repo.

Also found joomla bug raised http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemEdit&tracker_item_id=26197 of similar kind (mysqli_ping warning).

Thanks,
Pratik.

[helenbn]

I cannot figure out what is happening and why.

Is there any progress on this yet?

[christianweb]

I also have the same issue. No matter what i do the cron job never runs on my Joomla install. I am using the latest civicrm 4.3.4 and latest 2.5 joomla 2.5.11.

Some direct help would be appreciated, i.e. the exact cron command that should be run, because the ones outlined in your documentation do not work

Thanks

[helenbn]

Hi,

Is there a patch for this yet?

Thanks,
Helen

[christianweb]

Hi,

I have submitted this to the issue tracker and you can follow along here - http://issues.civicrm.org/jira/browse/CRM-13002

I have applied the changes outlined here - https://github.com/ravishnair/civicrm-core/commit/2cb7adde873f88ae03bcfc58206d19f43ef84864 and have run the cron job:

php -q /home/user/public_html/administrator/components/com_civicrm/civicrm/bin/cli.php -u user -p pass -e Job -a execute

This did not result in any cron errors like it did before, however it also did not run the cron jobs.

I also tried using the address bar and running cron.php manually using the existing site key and credentials and it also did nothing still. I tried changing the site key and that made no difference.

Seems like the issue is still there.

If anyone else has applied the changes specified in github and it then worked for them please let me know what you did exactly.

Igor

[helenbn]

I made the change and it did not work for me either.