Campaign Email Cron Job broke-upgrade 5.2.0 to 5.5.0

[rousseau]

I just upgraded from 5.2.0 CE to 5.5.0 CE a week ago. I sent a campaign about 3 weeks ago just fine with the cron job taking care of the sending aspect of the work (10 emails every 3 minutes). Now after the upgrade the scheduler is broken and will not run the jobs anymore.

This is frustrating because I had everything in place - had to contact my web host to get the cron job stuff working after manually pushing through too many campaigns.

Is anyone else experiencing this? Does anyone know why this upgrade would kill this feature? More importantly, does anyone know how to fix it?

Much thanks,

SugarCRM Community Edition
Linux CentOS 4.2
PHP 5.2.5
MySQL 4.1.2
Apache 2.0.52

The attached screen shot shows the time that the cron job stopped running, which incidentally was when I did the upgrade at 11:40 am 1/02/2010...hum?

[wdroush]

Isn't 5.5 still beta?

Don't run betas in production environments.


You said "manually", so if you manually ran the cron job it would work fine? Sounds like a server issue.

[rousseau]

Isn't 5.5 still beta?

Don't run betas in production environments.


You said "manually", so if you manually ran the cron job it would work fine? Sounds like a server issue.

wdroush, thanks for your comments, my reply:

5.5 GA came out on 12/2/2009. It is over a month old, not a beta.

I didn't manually run the cron job, I manually went into the "admin" area and "email queue management" and checked each of the 6000+ emails and pushed "Send Queued Campaign Emails" until all of them went through.

Hopefully it is a simple issue, but as the image shows above, the cron job was working up till 1/02/2010 11:39am which is when I did my upgrade. It stopped from then on.

Maybe I need to somehow restart or reset the cron job, I've just never had to do this before. Any ideas?

Thanks again in advance for any ideas here...

[rousseau]

I contacted my VPS web host tech support and explained the problem. He said some permissions and owners were strange and that (after fixing permissions/owners) the job appears to be running on the server again without any error. So there may have been some server issues from the upgrade but this now seems to be fixed.

However it still does not work. In the "Admin" "Schedulers" "Run Nightly Mass Email Campaigns" it is not showing the job running again. I also restarted the Apache web server in hopes of it restarting the job for SugarCRM. But anyway it's still not working.

Anybody else experience a similar situation? Anyone have any ideas how the cron.php works with the job scheduler and the server to pull off this magic (when it's working)?

It's a great software and a great feature and I hope someone has knowledge on how to fix this.

Thanks again,
John

[rousseau]

Okay after a little more looking I've found this:

I'm on MySQL version 4.1.2 and according to the requirements I should be on MySQL 5.0 or higher. See here:
http://developers.sugarcrm.com/docs/...5.html#1109147

"If you are using MySQL, install version 5.0 or higher to use with Sugar 5.5.0."

I'll have to talk with my web host to see about getting this upgraded. (after checking that upgrading this won't cause problems to my other software on the server )

Could this be causing Cron.php Scheduler problems?

thanks, John

[rousseau]

Well, after manually forcing another 5,000-6,000 emails through I discovered the error in the sugar.log file.

I had never had to go looking into the logs before, but now I see the value

The message was:
"Fri Feb 12 15:59:01 2010 [11339][1][FATAL] Scheduler cannot read the PID file. Please check permissions on cache/modules/Schedulers
Fri Feb 12 15:59:01 2010 [11339][1][FATAL] Scheduler cannot write PID file. Please check permissions on cache/modules/Schedulers"

So I went and changed the permissions for the "PID" file to "777" or read/write by all. And viola! it worked!!

So this is a crisis resolved, and hopefully my troubles can benefit someone else.