Unable to upgrade from 7.4.2 to 7.4.3

📦 Install & Upgrade Help
1

on step one of the system check of the upgrade process I end up getting the following…

"500 – Internal Server Error

The page you requested is currently unavailable. Please try again later.

If you are the website owner, please see Error: 500 Internal Server Error documentation for more information and possible steps to resolve the problem.".

I have double checked my permission and still get this 500 error. when I start the upgrade process in the upgrade wizard.

Does anyone have any ideas of what i should be looking for?

I’m running a LAMP setup

Thanks

Glen

2

Does anyone know what folders and files are checked during the “system check” of the upgrade process?

Thanks
Glen

3

Looking further into this error on our server this is what I found…

[Fri Dec 11 16:16:27 2015] [error] [client xxx.189.xxx.169] Premature end of script headers: php55.cgi, referer: http://xxxx?module=UpgradeWizard&action=index
[Fri Dec 11 16:16:28 2015] [error] [client xxx.189.xxx.169] Premature end of script headers: php55.cgi, referer: http://xxxx?module=UpgradeWizard&action=index
[Fri Dec 11 16:17:48 2015] [error] [client xxx.189.xxx.169] Premature end of script headers: php55.cgi, referer: http://xxxx?module=UpgradeWizard&action=index

Hopefully this helps, I have the directory permission to 777 as 775 was not working although 775 was working in the past.

4

Does ANYONE have any ideas where i can look for a solution on this error i get when trying to upgrade?

  • I have double checked permissions on all folders and files and they are set properly.
5

Can Anyone direct me to whom I can contact and pay to help me fix this upgrade issue?

Thanks

Glen

6

Looking further into this issues I found the upgrade wizard log and in it I see that the system check has passed with no issues. The log even shows that there are NO permission issues. Does anyone know what folder/file/script is triggered after the system check is completed?

This seems to be where the conflict is.

Again any assistance would be very much appreciated.

7

After working with my hosting company, they were able to determine the server was timing out and not allowing the upgrade wizard to complete all the scripts to move forward in the installation process.

Hope this helps someone else out.

8

Here is what my hosting company did…

I raised proxy_read_timeout to 10 minutes in our front-end Nginx configuration, and Timeout to 10 minutes in our back-end Apache configuration. I also removed RequestReadTimeout from the Apache configuration. The actual values probably aren’t too important, as long as they’re high enough to allow for whatever operations to complete