scheduling on Mac OS X

[ElgertS]

I have a new install of SugarCRM 5.0.0g on Mac OS X Server 10.5.4 and I am not able to get the scheduled jobs to process. I have tried setting up cron jobs and tried the wiki suggestion, but when I even manually run these commands either via a web browser or cli I get nothing to process. The only thing that will process is if I go to the admin and click the button to manually send queued messages. I have searched and tried lots of options on setting up cron jobs and nothing is working for me.

[jnassi]

I have a new install of SugarCRM 5.0.0g on Mac OS X Server 10.5.4 and I am not able to get the scheduled jobs to process. I have tried setting up cron jobs and tried the wiki suggestion, but when I even manually run these commands either via a web browser or cli I get nothing to process. The only thing that will process is if I go to the admin and click the button to manually send queued messages. I have searched and tried lots of options on setting up cron jobs and nothing is working for me.

What is the cli syntax you're using to execute cron.php? Were there any errors returned?

[ElgertS]

I haven't gotten any errors unless I try to process the emailmandelivery.php, in which case it says the page has moved and redirects to index.php.

What I have run is various takes on this:

* * * * * php -f cron.php 2>&1

specifying the actual location of the cron.php file or using cd to get to that directory first.

I have also tried using curl to run cron.php and emailmandelivery.php and also tried wget. With these, I do sometimes get errors, primarily it doesn't run the last command which is the one that sends the action to delivery the email.

[jnassi]

Some things to try....

1) Raise your sugarcrm log level in log4php.properties from fatal to debug, on a temporary basis. That way you can tail the sugarcrm.log file to see if the schedulers are executing at all, and you'll know when you have success.

2) Ensure that you're using the RIGHT php binary by specifying the full path of the php binary. You can verify the path that Sugar is using by dropping a phpinfo file into your Sugar root.

3) Ensure that you're running the command as the same user that your web server is running as.

Hope something here helps unsticks your scheduler.. without any errors, it's difficult to know where the problem resides