email campaign

[ysh]

Hi

After toilling for two days over this issue, I hope someone can tell me where I'm going wrong.

I set up the email using my host's email services (SMTP) and configured each user with email their corresponding parameters, and rely on Sugar's email service rather than on the system's default
services.

Manually speaking everything works. It's the scheduling part that doesn't.
Cron is programmed to execute the cron.php every fifteen minutes.
I believe that I got it to work once, or else it was one hell of a coincidence
because I received a email at quarter past !

If I click on 'Send Queued Campaign Emails' the emails are properly transmitted.
The obvious culprit seems to be the scheduling - but my lack of experience might
be clouding my assessment of the situation.

Any ideas would be warmly received.

Thanks

yann

[kuske]

The SugarCRM scheduler must run every minute, so cron must be set up to run every minute.
Sugar itself decides now which of the scheduler jobs will run.

[ysh]

thanks for your response.

My WEB host indicated that due to their TOS I could run scheduled jobs every 15 mins.
Will this prevent us from running Sugar's scheduled tasks ?

I ran a "*/15 * * * * date > /tmp/cron.test.txt" to check whether cron was operationnal,
and this file was correctly updated - each time - still holds true if I run "* * * * * date > /tmp/cron.test.txt"

I did try to execute http://mySugarURL/cron.php but nothing visible happened and the email is still in the queue.

cron.php has 644 perms.

Tried: * * * * * cd /home/xxxxx/public_html/SCRM && php -f cron.php > /dev/null 2>&1
but doesn't seem to have made any difference.

Where in Sugar do we see whether the job was run, successful or not ?

Just as a side note, clicking on the "send test" button has never had any visible effect.

Thanks

yann

[kuske]

OK; if you have that restriction that cron only runs every 15 minutes, then you must take care that this cron job is running on *:00, *:15, *:30 and *:45.
Additionally you must set up your Sugar scheduler jobs with exactly these intervals.
Sugar compares the minute values of the starttime with the minute values of the scheduler jobs.

I would take a 664 for cron.php because I never know which idea was actually hip in the community of the deployed linux version. If 644 runs then it is ok too.

In DB table schedulers_times you can see the timestamps of the schedulers. In status field there should be a completed, if not the associated scheduler will not run anymore. An "in progress" value prevents any further execution of some scheduler jobs.
You can alway delete lines in schedulers_times.

You see it is a wide area ( "ein weites Feld" in German ).

[ysh]

Viel Danke Kuske

Ok, thanks to your pointers I now understand how to monitor the scheduler's activities.
Not only within the database table itself, but also directly from each scheduled job view screen
in admin/scheduler.

All jobs were working properly (completed).

I modified the minutes at which [Check Inbound Mailboxes] and [Update tracker_sessions table] jobs execute
from '*' to '*/15'. Although things were previously working properly using the default '*' for [Check Inbound Mailboxes].

03/11/09
I just came across a post by SugarCane in the following : http://www.sugarcrm.com/forums/showthread.php?t=53532
sheds some light of course on why the repeated use, solely for testing purposes in the present case,
of an existing campaign won't succeed ! Hmm the warm light shines again upon my face, and it's back under the bonnet I go.


yann