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.
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.
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.