Upgrade to Release 6.1.4

[murugappan]

Hi,

I performed an upgrade to version 6.1.4. The upgrade was successful. I get the following error in the log. I am not sure what it is as the message is very cryptic. Please help.


[2021-03-09 22:12:02] ERROR: CronManager (ScheduledJob 5f118f6164ed9a317): Scheduling string error - Invalid CRON field value 0/1 at position 0. [] [] [2021-03-09 22:13:02] ERROR: CronManager (ScheduledJob 5f118f6164ed9a317): Scheduling string error - Invalid CRON field value 0/1 at position 0. [] [] [2021-03-09 22:14:02] ERROR: CronManager (ScheduledJob 5f118f6164ed9a317): Scheduling string error - Invalid CRON field value 0/1 at position 0. [] [] [2021-03-09 22:15:02] ERROR: CronManager (ScheduledJob 5f118f6164ed9a317): Scheduling string error - Invalid CRON field value 0/1 at position 0. [] [] [2021-03-09 22:16:02] ERROR: CronManager (ScheduledJob 5f118f6164ed9a317): Scheduling string error - Invalid CRON field value 0/1 at position 0. [] [] [2021-03-09 22:17:02] ERROR: CronManager (ScheduledJob 5f118f6164ed9a317): Scheduling string error - Invalid CRON field value 0/1 at position 0. [] []

[murugappan]

Hi All,

I manage to fix it. It all well and good now. The problem was caused by the upgrade. It corrupted on the of Group Email Accounts. I removed the account and created another and it works fine now.

[murugappan]

A word of reservation. After more testing, i found that this may only work if the instance has not been upgraded to version 6.0.10. Once you sink into versions > 6.0.10, the problem continues to exists. I have raised this with Maximus again. I do have 3 instances (test, staging, and production) relating to one app with this problem.

In one instance, after smooth upgrading to 6.1.4, there was a problem/error with the Scheduled Jobs on the Group Email Accounts. I found that a Group Email Account and the scheduler has some problem. All i did was to remove the "faulty" Group Email Account and created a new one in its place. Everything went on fine and cron is fetching the email correctly now. Phew!