new update crashed

[jimdanforth]

Since Ive been watching very close for the update, I saw it had posted today.  I also noticed it was actually 2 updates back-to-back.  When I ran the second upate, it aborted with the force option available.  I ran the force as I did last time, and it caused the server to generate a 500 error for both front and back end.  

I ran a restore and was able to get the site back up.  1st portion of update is fine, but second is still gereating:

update_from_55725_to_56860_version.zip installation aborted.

Im reluctant to force again.

[jimdanforth]

@Ivan Holbi

[pandrei]

14 hours ago, jimdanforth said:

Since Ive been watching very close for the update, I saw it had posted today.  I also noticed it was actually 2 updates back-to-back.  When I ran the second upate, it aborted with the force option available.  I ran the force as I did last time, and it caused the server to generate a 500 error for both front and back end.  

I ran a restore and was able to get the site back up.  1st portion of update is fine, but second is still gereating:

update_from_55725_to_56860_version.zip installation aborted.

Im reluctant to force again.

What is your PHP version? Really, this update may be installed only if you are running PHP version 7.4 or newer.

Anyway, please click the Download all logs button in Admin > Settings > Tools > Error log viewer and send me the zip file in pm.

2 hours ago, CHD-UK said:

I'm on PHP 8.0.25 so this was not installed on my server  ( ADMIN -> Tools -> Server Info )

You can update on the System update tab.

[Ken_Shea]

Cleared server cache corrected it, after the zillion times I've done that cant believe I didn't remember to do that grrrrrrr

 

On PHP 7.4.33,

Thse errors on loading Admin or Web Site even after a restore which makes no sense.

The file autoload_real.php is there.

Warning: require(/home/customer/www/v4.ontargetsportsonline.com/public_html/lib/vendor/composer/../phpunit/phpunit/src/Framework/Assert/Functions.php): failed to open stream: No such file or directory in /home/customer/www/v4.ontargetsportsonline.com/public_html/lib/vendor/composer/autoload_real.php on line 41

Fatal error: require(): Failed opening required '/home/customer/www/v4.ontargetsportsonline.com/public_html/lib/vendor/composer/../phpunit/phpunit/src/Framework/Assert/Functions.php' (include_path='.:/usr/local/php74/pear') in /home/customer/www/v4.ontargetsportsonline.com/public_html/lib/vendor/composer/autoload_real.php on line 41

Edited May 5, 2023 by Ken_Shea

[Ken_Shea]

Retried no checked files and forced restore, same fatal error.

Fatal error: require(): Failed opening required '/home/customer/www/v4.ontargetsportsonline.com/public_html/lib/vendor/composer/../phpunit/phpunit/src/Framework/Assert/Functions.php' (include_path='.:/usr/local/php74/pear') in /home/customer/www/v4.ontargetsportsonline.com/public_html/lib/vendor/composer/autoload_real.php on line 41

[bonbec]

56 minutes ago, Ken_Shea said:

.The file autoload_real.php is there.

Warning: require(/home/customer/www/v4.ontargetsportsonline.com/public_html/lib/vendor/composer/../phpunit/phpunit/src/Framework/Assert/Functions.php): failed to open stream: No such file or directory in /home/customer/www/v4.ontargetsportsonline.com/public_html/lib/vendor/composer/autoload_real.php on line 41 ...

The error says that the line 41 of the autoload_real.php have a require but the server don't find the required file ( Functions.php ).

The link is curious with /../ between composer and phpunit

[jimdanforth]

 

3 hours ago, pandrei said:

What is your PHP version? Really, this update may be installed only if you are running PHP version 7.4 or newer.

Anyway, please click the Download all logs button in Admin > Settings > Tools > Error log viewer and send me the zip file in pm.

You can update on the System update tab.

PHP Version 8.1.16

If I run the update I cannot open the backend to get the logs
I am attrempting the update from the system uptade tab as I have before.

 

[pandrei]

1 hour ago, Ken_Shea said:

The file autoload_real.php is there.

Warning: require(/home/customer/www/v4.ontargetsportsonline.com/public_html/lib/vendor/composer/../phpunit/phpunit/src/Framework/Assert/Functions.php): failed to open stream: No such file or directory in /home/customer/www/v4.ontargetsportsonline.com/public_html/lib/vendor/composer/autoload_real.php on line 41

Fatal error: require(): Failed opening required '/home/customer/www/v4.ontargetsportsonline.com/public_html/lib/vendor/composer/../phpunit/phpunit/src/Framework/Assert/Functions.php' (include_path='.:/usr/local/php74/pear') in /home/customer/www/v4.ontargetsportsonline.com/public_html/lib/vendor/composer/autoload_real.php on line 41

It looks like an error occurred during the update process and the patch was not fully applied. Could you send me the log files from here: lib/backend/runtime/logs/*.log

1 minute ago, jimdanforth said:

PHP Version 8.1.16

If I run the update I cannot open the backend to get the logs
I am attrempting the update from the system uptade tab as I have before.

Please send me the log files from here: lib/backend/runtime/logs/*.log

[jimdanforth]

Ill reapply the update and get you those logs.

 

[jimdanforth]

11 minutes ago, pandrei said:

It looks like an error occurred during the update process and the patch was not fully applied. Could you send me the log files from here: lib/backend/runtime/logs/*.log

Please send me the log files from here: lib/backend/runtime/logs/*.log

Same results after update.  Logs are not updated since April 28 even after applying update

 

[pandrei]

6 minutes ago, jimdanforth said:

Same results after update.  Logs are not updated since April 28 even after applying update

Ok. Then try to login admin panel. If you still get the error, the log files must be updated.

[jimdanforth]

12 minutes ago, pandrei said:

Ok. Then try to login admin panel. If you still get the error, the log files must be updated.

Treid that.  Date stamp still from April

[Ken_Shea]

48 minutes ago, pandrei said:

It looks like an error occurred during the update process and the patch was not fully applied. Could you send me the log files from here: lib/backend/runtime/logs/*.log

Please send me the log files from here: lib/backend/runtime/logs/*.log

list.logsql_error.logsupplier.log404_error.log

The app.log fails to upload, file too large, probably the one you need

[jimdanforth]

1 minute ago, Ken_Shea said:

list.log 102.81 kB · 0 downloads sql_error.log 143.23 kB · 0 downloads supplier.log 148 B · 0 downloads 404_error.log 34.67 kB · 0 downloads

The app.log fails to upload, file too large, probably the one you need

hmm  I only have an app.log and list.log

 

[Ken_Shea]

9 minutes ago, jimdanforth said:

hmm  I only have an app.log and list.log

 

 That's because I'm a bigger screw up then you 😄 

[jimdanforth]

5 minutes ago, Ken_Shea said:

 That's because I'm a bigger screw up then you 😄 

cant be.  I broke it first.

[pandrei]

34 minutes ago, Ken_Shea said:

The app.log fails to upload, file too large, probably the one you need

Thanks. It's enough. But there are no errors from update.

I see you restored the site. I still have an access to admin panel. May I apply the update to see the result?

[pandrei]

1 hour ago, jimdanforth said:

Treid that.  Date stamp still from April

I will try to help if you send me the access to ftp or to control panel (for shared hosting).

[Ken_Shea]

36 minutes ago, pandrei said:

Thanks. It's enough. But there are no errors from update.

I see you restored the site. I still have an access to admin panel. May I apply the update to see the result?

absolutly, I'll stay off.

[pandrei]

Just now, Ken_Shea said:

absolutly, I'll stay off.

Ok, I will apply the update.  Could you give me the access to ftp or to control panel if something goes wrong?

[pandrei]

54 minutes ago, Ken_Shea said:

absolutly, I'll stay off.

I've applied the update. You have the same issue as @jimdanforth

The php script was terminated and the update was not fully updated. Probably your server settings has some limits or something like this.

What should you do.

1. copy the file update_from_55725_to_56860_version.zip from uploads folder to the site root

2. unzip it and overwrite all files if it asks. Or just use this bash commands:
 

cd your_site_root

unzip -o update_from_55725_to_56860_version.zip

3. If it restores the admin panel, login, go to Settings -> Cache Control, select Migrations apply and click Flush button

If you still could not login, you should run this commands:

cd you_site_root
php yii.php migrate

and type yes when it asks you to confirm

Please let me know if this was of help

[jimdanforth]

I ran the process above, and it no longer gets the 500 error, but is still erroring out

 

[pandrei]

@Ken_Shea, @jimdanforth, @CHD-UK

after unzipping, upload the attached file to the site root and open this link in the browser: https://your_site/apply_migrations.php

apply_migrations.php

P.S. if you don't see the Finish in the end of the page, send me a screenshot or saved html page and log files from here lib/console/runtime/logs/*.log.

Edited May 6, 2023 by pandrei

[Ken_Shea]

Cleared browser and server cache

restored web site/v4 files

uploaded both   update_from_55725_to_56860_version.zip  and apply_migrations.php 

extracted update_from_55725_to_56860_version.zip

ran https://your_site/apply_migrations.php from browser

admin > settings > cache control flushed all cache

Both site and admin load fine 

success....... I think... hope 🙂

Thanks andrei

 

[pandrei]

1 hour ago, CHD-UK said:

Whilst installing

[05-May-2023 10:27:04 Europe/London] PHP Fatal error:  Allowed memory size of 268435456 bytes exhausted (tried to allocate 8192 bytes) in /home/dd/public_html/lib/backend/controllers/InstallController.php on line 1017
[05-May-2023 10:27:04 Europe/London] PHP Fatal error:  Allowed memory size of 268435456 bytes exhausted (tried to allocate 8192 bytes) in /home/dd/public_html/lib/backend/controllers/IndexController.php on line 393

Thanks Andy! I realized that the script was forcibly terminated, but I didn't know the reason because I don't have access to the apache logs.I understood that the script was terminated, but I have not a reason because have not access to the apache error log.

1 hour ago, CHD-UK said:

Not sure if there is anything that can be done in the update script to tune the amount of memory consumed or if it is just a case that I have to go and get a bigger server !

I think that this is a consequence of the large size of the last update (we updated third-party libraries) and the non-optimal work of the system class ZipArchive with memory.

Anyway, we will try to optimize it.