Jump to content

500 Server Error while Rollback from Prestashop 8.2.1 to 8.1.6 , BackOffice is not reachable


Recommended Posts

Hi there, 
I could finally upgrade our Shop from 8.1.6 to 8.2.1 with 1-click-Upgrade v 6.3  , but I could NOT be able to open the Shop  due to a HTTP ERROR 500  (with and without Maintenance Mode).   Yesterday I could not found other way to make it work and today I wanted to ty to use the Rollback function of the 1-click-Upgrade to go back to the previous functioning version 8.1.6 . Unfortuanatly, the Rollback was failed. Now the BackOffice https://ourDomain/shop/admin***/   and also the Shop itself are not reachable due to a 500 Server Error 

 

500-Server-Error.jpg

 

I tried to look at /usr/local/www/our_shop/var/logs 

*ERROR*     v8.1.6    2025/04/01 - 09:02:40: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'asprestashop.ps_configuration' doesn't exist at line 151 in file classes/db/DbPDO.php
 

It seems something is / are missing.  With the previous HTTP Error 500 i could at least login to the Backoffice, but now it is totally horrible. The Server ist responding for ping check and apache24 is running. 

Is there any way to overcome or solve this error? Thanks! 
 

Edited by Abdurahman-Amat (see edit history)
Link to comment
Share on other sites

Posted (edited)
  On 4/1/2025 at 10:11 AM, Knowband Plugins said:

Any backup of the database (except the 1-click-Upgrade backup).

You can try restoring the database backup if you have one. 

Always take a backup of the files and DB separately. Don't rely on the 1-click-Upgrade backup.

 

Expand  

Thanks for your blitz respond!  

I found one complete copy of the /usr/local/www/shop directory, /usr/local/www/phpMyAdmin directory and /usr/local/www/apache24 directory from the server, which I secured last November 2024. The 1-Click-Upgrade was doing its job well during the years and this time I forgot to secure this time.  Is there any way to restore the shop?  it is ok if it does require some manuall fixing.  

 

Edited by Abdurahman-Amat (see edit history)
Link to comment
Share on other sites

Go to Admin -> backups directory (Check the admin according to your PrestaShop installation). There should be some bz file. 

Check the latest sql.bz2 file. Download the same, Unzip on local and restore in the new Database and try changing the database in the app/config/parameters.php (Its suggested to restore in the new Database instead of the existing database).

 

 

Link to comment
Share on other sites

  On 4/1/2025 at 10:36 AM, Knowband Plugins said:

Go to Admin -> backups directory (Check the admin according to your PrestaShop installation). There should be some bz file. 

Check the latest sql.bz2 file. Download the same, Unzip on local and restore in the new Database and try changing the database in the app/config/parameters.php (Its suggested to restore in the new Database instead of the existing database).

 

 

Expand  

Yes, there is a xxxx.sql.bz2 file under the backed up copy shop_directory/adminxxx/backups   

You are saying that to download the aktuell database file yyyy.sql.bz2 from the server and extract it. Then restore the contents of the backed up xxxx.sql.bz2 after extraction into this extracted new datebase file.  At the end adjust the app/config/parameters.php for the newly restored database. I hope I am understanding it right. 

Link to comment
Share on other sites

  On 4/1/2025 at 10:53 AM, Abdurahman-Amat said:

You are saying that to download the aktuell database file yyyy.sql.bz2 from the server and extract it. Then restore the contents of the backed up xxxx.sql.bz2 after extraction into this extracted new datebase file.  At the end adjust the app/config/parameters.php for the newly restored database. I hope I am understanding it right. 

Expand  

Yes correct. 

Link to comment
Share on other sites

Posted (edited)
  On 4/1/2025 at 10:56 AM, Knowband Plugins said:

Yes correct. 

Expand  

I extracted the backed up xxxx.sql.bz2  file and inside exits only a sql file xxxx.sql   .  It is weird, i could not find the current database file. Where should I look for it? Is it under phpMyAdmin oder somewhere under adminxxx folder ? Do you have any idea about it ?

I found a auto_backupfile_v8.1.6_xxxx.zip file  created yesterday by 1-click-upgrade modul, during the successfull (at least BackOffice was reachable) upgrade. I am ganna extract this auto_backup file as well. 

thanks! 

Edited by Abdurahman-Amat (see edit history)
Link to comment
Share on other sites

Posted (edited)
  On 4/1/2025 at 1:09 PM, Knowband Plugins said:

.sql file is a database file which you need to import via the PHPMyAdmin.

 

Expand  

When I open the login page of phpMyAdmin pannel of our shop, several Deprication Notices are being displayed.

Deprecation Notice in ./libraries/classes/Url.php#246
 http_build_query(): Passing null to parameter #2 ($numeric_prefix) of type string is deprecated

Backtrace 

....

Deprecation Notice in ./vendor/twig/twig/src/Loader/FilesystemLoader.php#40
 realpath(): Passing null to parameter #1 ($path) of type string is deprecated

Backtrace

...

Deprecation Notice in ./libraries/classes/Url.php#246
 http_build_query(): Passing null to parameter #2 ($numeric_prefix) of type string is deprecated

Backtrace

...

Deprecation Notice in ./vendor/twig/twig/src/Node/Node.php#210
 Return type of Twig\Node\Node::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Backtrace

...

Deprecation Notice in ./vendor/twig/twig/src/Node/Node.php#215
 Return type of Twig\Node\Node::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Backtrace

...

I can login to it and there I am encountering Deprication Notices.   At the left side panel I can at lease see the Database name and other entries, like ps_order, ps_order_details etc.  and when I click any of them that Deprication Notice willbe poped up and annoying me.  

When I open "Import" Tab on phpMyAdmin Menu, I get again a lot of these Deprication Notices and at bottum the following is showen. 

image.png.12dba38fdcadc077d3b139df52265afa.png

 

For Gods sake, i can ignore them with "Ignore All" option.  I am about to import that backed up Database sql file.  Can I check if that backed up Database (mentioned above) is currect? I mean, is it possible to check that sql file before the Import that, for example, an order short before the Backup date Nov. 2024  ?  I can look at our E-Mails etc., then I can then say that whether theis backed up database is currect or not.  I have never done Database Import yet. 

Screenshot2025-04-01170257.thumb.jpg.29207c8d03125335c8b83a1c725d5935.jpg

I am worrying now, if I am ganna losing our Online shop  and all the Database or not. That is a terrible feeling ...  Please give me advice and tips about this. I am ganna perform this Import tomorrow. 

I give my best to get our shop back! 

 

Edited by Abdurahman-Amat (see edit history)
Link to comment
Share on other sites

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