Cron Issues after Upgrade

We are having some Cron issues now after our upgrade. I am getting the following errors sent to the user that the cron is running as (apache user):

    Fatal error: Uncaught exception 'Exception' with message 'Assertion failed: [array] "" is not a valid asset ID' in /home/websites/puc_matrix_3-16-2/core/include/assertions.inc:507
    Stack trace:
    #0 /home/websites/puc_matrix_3-16-2/core/include/asset_manager.inc(1017): trigger_exception('[array] "" is n...', false, true)
    #1 /home/websites/puc_matrix_3-16-2/core/assets/system/cron/jobs/cron_job_clear_matrix_cache/cron_job_clear_matrix_cache.inc(91): Asset_Manager->getAsset(Array)
    #2 /home/websites/puc_matrix_3-16-2/core/assets/system/cron/cron_job/cron_job.inc(597): Cron_Job_Clear_Matrix_Cache->_exec('')
    #3 /home/websites/puc_matrix_3-16-2/core/assets/system/cron/cron_manager/cron_manager.inc(570): Cron_Job->run()
    #4 /home/websites/puc_matrix_3-16-2/core/cron/run.php(63): Cron_Manager->run()
    #5 {main}
     thrown in /home/websites/puc_matrix_3-16-2/core/include/assertions.inc on line 507


This is then followed by a cron deadlock which has to be cleared each time the cron runs. Was there something that needed to be done to the cron during upgrade in addition to commenting out the entries in the crontab?

That's a very strange problem. That job has undergone some development and additional testing in the last few versions but nothing changed with the job owner, which is where the error lies. You can submit a bug report, but a support ticket may be better as it may involve some manual DB changes or investigation.

bug #3427


I will submit a ticket to Squiz Support as well.



Thanks.