CiviCRM Community Forums (archive)

I recently updated to 4.2.1 from 4.1.3 and I'm now getting a cron error every time a mailing is sent. The email is delivered fine, but the mailing status remains "Running"  and I get the attached cron error.

Not submitting this as a bug unless someone can reproduce.

I'm assuming the db error is related to the changing of the mailing status as I don't see any other side-effects though that should be a db update and not an insert, so the "already exists" doesn't make any sense.
Any pointers on how to troubleshoot this one? I see nothing special in syslog.

Trying to see the job log from within civicrm (joblog?jid=2&reset=1) runs out of memory, so I haven't pursued that further.

Thanks!

Strangely enough everything works now. The original 2 mailings that generated the error are still marked as scheduled, but all newer ones went out without errors and are "complete".

Thanks for the suggestion anyway!