Upgrading from 8.5.1 to 8.8.0 resulting in 500 Error

Just to be sure I understand what youā€™re asking, because Iā€™m in the middle of the upgrade between the upgrade and upgrade-finalize steps.

You want me to roll back now, get back into SuiteCRM 8.5, set the new log level, just to see if thereā€™s a FATAL error on upgrade? Iā€™ll do it, butā€¦

ā€¦you forgot to answer my question regarding the php8.2-fpm. I tried a restart of it anyways and itā€™s not installed.
Failed to restart php8.2-fpm.service: Unit php8.2-fpm.service not found.

Please and Thank you

noooo, you can continue with finalize steps and check your CRM.

Maybe you do not need to restart PHP now. Leave it. Donā€™t worry about it.

1 Like

Youā€™re not going to believe what I think the issue was. I followed my script to the letter, as last time, with one exception.
At site_url and host_name in .htaccess I noticed we didnā€™t have http:// or https:// in front of the website address, so I added them this time.

The upgrade to 8.8 was a success. And the PHP Fatal errors in error.log are gone.

Just to be sure Iā€™m going to roll back and induce this fault and see if I can repeat the results. Iā€™m also going to turn on log level = FATAL and install php8.2-fpm if you still think we need it.

Thanks for the quick back and forth today. Iā€™m sure many others will find our detailed troubleshooting helpful in the future.

Cheers

Thatā€™s interesting. Please check config.php file in legacy folder.

Check host_name and site_url parameters.

you do not need php8.2-fpm. You just need correct version of php that can run your CRM.

Yes, definitely. :partying_face: :partying_face: :partying_face: :smile: :smile:

Looks like I hit an unknown ā€œDaily Reply Limitā€ yesterday. LOL

Anyways, thanks again for all the assistance and I wanted to leave you and everyone with this final (possibly scary) note.

If re-verification of our findings turns out to be correct, this means :
a) leaving off the protocol on site_url or host_name doesnā€™t affect normal operations, other than the occasional php WARN or INFO; and
b) these settings need to be perfectly correct as they are referenced during an upgrade and this does affect successful completion of the upgrade and subsequent operations resulting in FATAL errors occuring.

In short, if an incorrect setting prohibits the successful upgrade of your application it should also prohibit the program from running at all. Just a suggestion.

Cheers