cron.php, scheduler: strange behavior, 4.2.1a

[simple]

Hi All

I have some strange problems with scheduled jobs / cron.php. Two installations of Sugar Pro - one is a fresh 4.2.1a installation the other upgraded to 4.2.1a (both on linux, but two seperate systems):

On the fresh installation the scheduled jobs don't get executed when run thru crontab. When I load the cron.php in a browser it worked a few times?!? I don't know why it worked a few times....but I got some entries in the job liafter calling the cron.php within a browser.

---------------------------------------------------------------------------
Job function::runMassEmailCampaign Status Active
Date & Time Start 2006-07-24 00:00 Active From Always
Date & Time End perpetual Active To Always
Last Successful Run 2006-07-26 14:35 Interval Every 5 minutes
Execute If Missed Always
Date Created: 2006-07-17 21:43 by admin Last Modified: 2006-07-26 14:49 by admin
---------------------------------------------------------------------------
Execute Time Status
2006-07-26 14:35 Completed
2006-07-26 14:10 Completed
2006-07-26 13:40 Completed
2006-07-26 13:25 Completed
---------------------------------------------------------------------------

The crontab entry is correct and working (log). I activated full logging. There are only entries for the manual calling of cron.php within a browser.

When I execute "php -f cron.php" in a shell the scripts stops in "include/database/DBManger.php" in the function getInstance()

echo "hello1";
$dbinstances[$instanceName]->connect($config, true);
echo "hello2";


I get only the "hello1" output. The $config var seems okay - at least the user/login stuff is correct.

In version 4.2.0 the schedules were running, campaings and sending mails worked.

I hope someone can help me?

Regards, Pascal

OS: Linux Debian 3.1
Sugar: Pro 4.2.1a
Webserver: Apache 1.3.33
PHP: 4.3.10
MySQL: 4.0.24

[simple]

Hello

Sorry, my english is not very well. Is my problem description not clear enough or doesn't anybody know what the problem might be? SugarTeam?

Best Regards, Pascal

[simple]

I found the problem.

On our Debian 3.1 system I had to change the cron entry from

*/5 * * * * cd /var/www/<domain>/; php -f cron.php >/dev/null 2>&1

to

*/5 * * * * cd /var/www/<domain>/; php -c /etc/php4/apache/php.ini -f cron.php >/dev/null 2>&1

Otherwise the mysql extension is not loaded - that's why the script exited with a fatal error.

Regards, Pascal