Jump to content

1-click upgrade of PrestaShop from 1.7.8.0 to 1.7.8.1 result in a 500 server error


Vidar Bjerkeland

Recommended Posts

I have tried to update from 1.7.8.0 to 1.7.8.1 using 1-click upgrade. When clicking on the 1-click upgrade in admin-panel, I get immediately an HTTP 500 ERROR.

The log on the SiteGround server shows this error: 

It appears that this problem is related to the actual application and not the server. As soon as I try to open the "1-click Upgrade". the following error is being generated:

2021-11-17 12:46:59.253045 [Wed Nov 17 12:46:59.252997 2021] [:error] [pid 9066] [client 82.118.240.146:44610] PHP Fatal error: Uncaught Error: Class 'Symfony\Component\Debug\Exception\FatalThrowableError' not found in /home/customer/www/racinghorses.eu/public_html/vendor/symfony/symfony/src/Symfony/Component/Debug/ErrorHandler.php:559, referer: https://racinghorses.eu//index.php?controller=AdminDashboard&token=abb00599a85666a8b03a7cb1d49fb75f
2021-11-17 12:46:59.253095 [Wed Nov 17 12:46:59.253028 2021] [:error] [pid 9066] [client 82.118.240.146:44610] Stack trace:, referer: https://racinghorses.eu//index.php?controller=AdminDashboard&token=abb00599a85666a8b03a7cb1d49fb75f
2021-11-17 12:46:59.253101 [Wed Nov 17 12:46:59.253065 2021] [:error] [pid 9066] [client 82.118.240.146:44610] #0 [internal function]: Symfony\Component\Debug\ErrorHandler->handleException(Object(Error)), referer: https://racinghorses.eu//index.php?controller=AdminDashboard&token=abb00599a85666a8b03a7cb1d49fb75f
2021-11-17 12:46:59.253104 [Wed Nov 17 12:46:59.253071 2021] [:error] [pid 9066] [client 82.118.240.146:44610] #1 {main}, referer: https://racinghorses.eu//index.php?controller=AdminDashboard&token=abb00599a85666a8b03a7cb1d49fb75f
2021-11-17 12:46:59.253142 [Wed Nov 17 12:46:59.253125 2021] [:error] [pid 9066] [client 82.118.240.146:44610] thrown in /home/customer/www/racinghorses.eu/public_html/vendor/symfony/symfony/src/Symfony/Component/Debug/ErrorHandler.php on line 559, referer: https://racinghorses.eu//index.php?controller=AdminDashboard&token=abb00599a85666a8b03a7cb1d49fb75f

 

I would be very thankful for any advise who can let me solve this problem with the version upgrade of my 1.7.8.0 PrestaShop Multistore.

Skjermbilde 2021-11-18 091003.png

Link to comment
Share on other sites

11 hours ago, SmartDataSoft said:

Hello, Did you backup the site before one click update. It will better to download the zip file and upload in sever folder and manually zip select from update area. some time download failed if internet make problem

 

thank you

Hello, thank you for advise. I am novise when it comes to the server issues. Does your company provide support for PrestaShop on the matter? I would be interested in having a frequent 2 line support from your company in those cases when I am not able to solve the issues myself. For more than 10 years, I have been able to solv issues myself, but this time with the 1-click upgrade module that is failing, I'm stuck. I have no idea how to run the module without getting the HTTP 500 ERROR.

Link to comment
Share on other sites

please be aware that due to the latest changes the ZipArchive::extractTo functionality triggered by the module is causing a very large number of files to be opened at the same time. The limit on SiteGround GoGeek plans is 4096 which should be enough for the functionality of most applications. It appears that with the latest changes in the module it tries to open more than 16 000 files while attempting the upgrade. This is a very increased value and they are not able to adjust their servers to match the demand. So, with SiteGround, the only solution will be to upgrade to their solution> 

Jump Start

80,00€/mo

EXCL. VAT

Link to comment
Share on other sites

5 minutes ago, cassandra8 said:

I am on siteground as well and the same thing happened to me. How were you able to fix? I had updated a couple of weeks ago and just got around to opening when this happened. I tried to restore to that point but still returns a 500 error.

In this case, the reason was from the server side...

new kernel 1.7.8.x is more demanding on server resources (for example, the value of the ulimit parameter)

therefore only works well on tuned VPS or VDS

 

There should be a more accurate text of your error in the webserver logs or in the prestashop logs: /var/logs

 

How may I help you?

Link to comment
Share on other sites

12 minutes ago, cassandra8 said:

I also do not understand why version 4.12 of 1 click upgrade worked with upgrading to 1.7.7.8. I had no problem upgrading using this version  Then when I updgrade once I was already on 1.7.7.8 it threw the error.

text of your error in the webserver logs or in the prestashop logs: /var/logs

 

and install newest version 4.13

https://github.com/PrestaShop/autoupgrade/releases

#408: Fix CLI upgrade by @atomiix

 

 

and check this page in BO:

/youradmin/index.php/configure/advanced/system-information/

if it is also 500, then the reason is in your webserver

 

my config:

image.thumb.png.d60ffcc4fbb05cdad7df0f93609fbd4e.png

 

 

 

Link to comment
Share on other sites

  • 4 weeks later...

Same problem,

Trying to update to prestashop_1.7.8.2 in a Siteground hosted site, and I have tis error in the log of the updater:

[INTERNAL] /home/customer/www/DOMAIN/public_html/modules/autoupgrade/classes/ZipAction.php line 154 - ZipArchive::extractTo(/home/customer/www/DOMAIN/public_html/ADMIN/autoupgrade/latest/localization/CLDR/core/common/main/fo.xml): failed to open stream: Too many open files

 

 

Link to comment
Share on other sites

4 hours ago, Arno Peck said:

Same problem,

Trying to update to prestashop_1.7.8.2 in a Siteground hosted site, and I have tis error in the log of the updater:

[INTERNAL] /home/customer/www/DOMAIN/public_html/modules/autoupgrade/classes/ZipAction.php line 154 - ZipArchive::extractTo(/home/customer/www/DOMAIN/public_html/ADMIN/autoupgrade/latest/localization/CLDR/core/common/main/fo.xml): failed to open stream: Too many open files

 

 

You site is shared or dedicated. The error logs problem in file node limit of the server . Some server has file limit or space limit.

It occure error at the time of unzip the file due to many files.

 

Thank you

Link to comment
Share on other sites

I have had nothing but problems from Siteground with my site. Every time I try to move or update something I am getting a 500 error in the back end stating too many files opened. It has soemthing to do with cache.  The option was to reinstall a clean install and start over or start over with a new hosting and move away from Prestashop. Sorry Prestashop but I am moving. 

Link to comment
Share on other sites

The cost of renting separate virtual or real servers is also getting cheaper

https://www.hetzner.com/cloud

and they may already be cheaper than the old hosting, but the site will be on a more modern computer hardware

 

Examples of fresh site optimization on the 1.7.8 core:

https://nasosvdom.com/ru/

https://pagespeed.web.dev/report?url=https%3A%2F%2Fnasosvdom.com%2Fru%2F

https://kma.ua/ru/

https://gtmetrix.com/reports/kma.ua/VOR92HJK/

 

 

 

Edited by Sashok (see edit history)
Link to comment
Share on other sites

On 11/23/2021 at 3:51 PM, Vidar Bjerkeland said:

please be aware that due to the latest changes the ZipArchive::extractTo functionality triggered by the module is causing a very large number of files to be opened at the same time. The limit on SiteGround GoGeek plans is 4096 which should be enough for the functionality of most applications. It appears that with the latest changes in the module it tries to open more than 16 000 files while attempting the upgrade. This is a very increased value and they are not able to adjust their servers to match the demand. So, with SiteGround, the only solution will be to upgrade to their solution> 

Jump Start

80,00€/mo

EXCL. VAT

Workaround if you don't wanna spend that money just to be able to upgrade: 

 

Link to comment
Share on other sites

  • 1 year later...

A workaround in case you get error 500 with manual update from local directory:
if you have already updated the autoupgrade module, upload via ftp the old version and modify all config.xml files changing the version to 4.15.0.
Thus the module opens and the update can start.

Link to comment
Share on other sites

  • 8 months later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...