During the upgrade from v4.7.18 to v4.7.19, the upgrade process was interrupted by the following error message:

CANNOT_WRITE
/var/www/html/107786/system/File/Amazon.php::328

After 'Retry' attempts failed (coming back the same error message, I was able to 'Continue' with the upgrade. It did finish to completion; however, is this upgrade error during the process one of concern?

Thanks,
Mike

 

If you could complete it after clicking continue, it was most likely a temporary write issue with your Amazon S3 bucket.

 

I wouldn't worry about it unless you also get the same error when uploading attachments, etc.

 

Are you seeing anything showing up in the system logs, post upgrade?

The system log shows 17 errors during/after the upgrade.

8 of them display "upgrade_error" - "IPS\File\Exception (3) ServiceUnavailable no tomes available CANNOT WRITE"

the above errors are after the following errors:
3 logs:  "javascript" - "IPS\File\Exception (3) ServiceUnavailable: CPU too busy CANNOT WRITE

"template_store_missing" - "Template sotre key:template_0_07d4cac51a1499786921b8471f7e65f8_dashboad missing ...."

"uncaught_exception" - "ErrrorException: template_store_missing (0) #0 /var/www/html/107786/applications/gallery/extensions/core/Dashboard/Overview.php (61)
 

I can provide more detail from the logs if necessary
 

45 minutes ago, Mke Stoltz said:

The system log shows 17 errors during/after the upgrade.

8 of them display "upgrade_error" - "IPS\File\Exception (3) ServiceUnavailable no tomes available CANNOT WRITE"

the above errors are after the following errors:
3 logs:  "javascript" - "IPS\File\Exception (3) ServiceUnavailable: CPU too busy CANNOT WRITE

"template_store_missing" - "Template sotre key:template_0_07d4cac51a1499786921b8471f7e65f8_dashboad missing ...."

"uncaught_exception" - "ErrrorException: template_store_missing (0) #0 /var/www/html/107786/applications/gallery/extensions/core/Dashboard/Overview.php (61)
 

I can provide more detail from the logs if necessary
 

Those are from during the upgrade itself. Please let us know if you see any issues, but as the upgrade is through, you can safely ignore this 

I saw this behavior on my primary cloud account and on my dev cloud instance.  I was able to continue the upgrade and so far I have not seen any issues uploading files.  So I ignored it and moved on.  🙂