POST UPGRADE FAILED from 9.0.2 to 9.0.3

Check your file permissions on the file it failed to open.

I often use the following three commands from Sugar Root to set all directories to 775 and all files to 664 and give ownership to apache.

sudo chown -R  apache:apache *

sudo find . -type d -exec chmod 775 {} \;

sudo find . -type f -exec chmod 664 {} \;

Hi Francesca, 

thank you for your reply. The problem is not in file permissions because the file Sugar look for doesn't exists. The module involved, pmse_Inbox, is related to Process Management module that is not present in PRO version. 

The issue is related to the type of sugar user: single users have problems to log into the platform, admin users have not.

It seems like there are a currupted class_map file that require this module even if there isn't any file il place. 
I think that the problem is related to the error I had upgrading the system that doesn't clean well the configuration file after upgrading, but I don't know how to manually clean and how to manually complete the post install phase.

Regards,

Sorry for misunderstanding the issue Federico.

It looks like the classmap you see in your cache comes from: 

vendor/composer/autoload_classmap.php

I would compare the vendor/composer/autoload_classmap.php in your development and production environment and see if there are any differences.
If all else fails try to comment out the entry for the PMSEEngineUtils.php and see if that works.

Then report your findings to Sugar Support.

Sorry I'm not much help on this, good luck!

Francesca

HI Francesca, 

At the end I choose to reestablish the previous version in production and so I repaired the installation. Next week I will try to create a mirror image in the same environment and upgrade the release with silent upgrade. 

Class map is different but today I found that some modules has changed from standard view to a view similar at schedulers and reports...  

It seems like there something wrong in some PHP settings that doesn't work well enough when upgrading from web interface..
Boh, now I solved, but in the future for stability purposes I'm thinking to reinstall from scratch directly in the last version and then import customization to the last version: it'a very big challenge but it seems to be the only way to have some sustainability in time for the platform.

Regards,

HI Francesca, 

At the end I choose to reestablish the previous version in production and so I repaired the installation. Next week I will try to create a mirror image in the same environment and upgrade the release with silent upgrade. 

Class map is different but today I found that some modules has changed from standard view to a view similar at schedulers and reports...  

It seems like there something wrong in some PHP settings that doesn't work well enough when upgrading from web interface..
Boh, now I solved, but in the future for stability purposes I'm thinking to reinstall from scratch directly in the last version and then import customization to the last version: it'a very big challenge but it seems to be the only way to have some sustainability in time for the platform.

Regards,

Best of luck!
I have always used Silent Upgrade, I had a few issues in the past but nothing insurmountable. 
We will see how our 9.0.2-> 9.0.3 upgrade goes... I've not done it yet

In bocca al lupo!

Francesca

Crepi il lupo!

Federico