4.2.1 upgrade breaks scheduler

[bari]

I've updated my sugar install to 4.2.1 and the scheduled jobs no longer run. Whatever is failing it is doing so silently. Problem started immediatly after I installed the update. From the log, it looks as if stuff is running, but i get now inbound email, a custom job doesnt do anything, nothing new in the job log, and last successful run value doesnt change. Any thoughts?

I attached the log

[clint]

We're releasing 4.2.1 patch A tomorrow which fixes this issue.

Clint

[clint]

This is fixed 4.2.1 patch A which we just posted.

See this thread for links to the release notes and the bits.

[unicum]

Hi Clint,

For me, the patch 421a doesn't solve the problems with any outbound email account. I tried all hints and tricks, even by a fresh install, even using other than company email accounts...

[IMG]Bild 24.png[/IMG]

[clint]

Hi Clint,

For me, the patch 421a doesn't solve the problems with any outbound email account. I tried all hints and tricks, even by a fresh install, even using other than company email accounts...

Hi Unicum -

Your outbound email problems are definitely different than the inbound email problems listed here. Inbound email is automatically polled every few minutes by a Sugar scheduler job that is driven by cron on *nix or the Windows scheduler.

Does any email get out of your system? In other words do your notification emails get sent out? The "new record assigned to you" email notifications are sent out by the system using the email settings in the "Admin" page. Is that working for you?

However, when a user sends out an email, the outbound emails settings are configured per user in the "My Account" page. So my first question there is whether those settings are 100% correct?

If those are correct, next try sending an email out with pure ASCII characters. No umlauts, no accent marks. Just plain vanilla ASCII characters. I know there are some issues with sending/receiving email with non-ASCII charsets. This is one of the things Chris is addressing in the upcoming 4.5 release (available next month). However, I don't know the details of the issues.

Let me know how your testing goes with what I just described. If you can get emails to successfully send using ASCII-only characters, I'll get Chris to weigh in on whether there are any workarounds you can do to get non-ASCII characters working.

Again, I'm not aware of all the exact technical issues so these last comments may be off-base. I'll check with Chris.

Clint

[kpit]

A little note about SMTP vs. sendmail UNIX/Linux systems with SugarCRM E-mail Campaigns.

A few points about SMTP that can cause problems with Email Campaigns.

1. SMTP when connections to your server are not on the localhost or on your local network can introduce delays and errors that may cause PHP to timeout. This may be caused by the number of messages to be sent per batch and the size of the messages to be sent.
2. SMTP would be better handled by fulltime mail servers installed locally such as postfix, sendmail and qmail. Any of these servers could be configured to relay mail to the actual email server. The email server must be configured to only relay from these specific servers with authentication.

Ther are many more reasons to use a local sendmail to send the emails over using SMTP. Emails are queued on local machine for delivery by the local email server program to the remote email server. This offloads the delevery process to email server programs such as sendmail, postfix and qmail which are better at relaying email to the email server.

I use the sendmail method in SugarCRM. I have a postfix email server configured to relay email to the real email server. The real email server is configured to accept only relays from SugarCRM Server with authentication. The email server on the SugarCRM server does not accept email at all it only relays emails from the localhost. This prevents spammers from useing my email server as an open relay.

I have found that using sendmail method for emails in SugarCRM is much better than using SMTP. First I can send many more messages per batch than using the SMTP without having PHP timeout on me. And the biggest one of all the sendmail method retries sending emails on failure of sending the emial message. It Retries for several Hours in case the server went off line for maintenance.

[Beefeater]

I've updated my sugar install to 4.2.1 and the scheduled jobs no longer run. Whatever is failing it is doing so silently. Problem started immediatly after I installed the update. From the log, it looks as if stuff is running, but i get now inbound email, a custom job doesnt do anything, nothing new in the job log, and last successful run value doesnt change. Any thoughts?

I attached the log

I'm having the exact same problem. Did you find a solution?