Hi.

Yesterday i upgraded to 4 and then to 8 a customer running an other release channel Osclass. Fully loaded.

And i got this in debug log, several times. The upgrade was ok, until now i see no issues anywhere.

I tried to find out what is the cause of this, on the net, and i failed. Some said (for Wordpress) it is PHP 7.4 but i re-did the upgrade in a staging server, same issue.

Thanks

02-Oct-2022 23:41:27 Europe/London] PHP Notice:  fgets(): read of 8192 bytes failed with errno=21 Is a directory in /home/oc-includes/osclass/upgrade-funcs.php on line 512

It looks like some server related issue.

I have no idea what it is, this is why i asked. Server related, i doubt since the site is/was running there for 6 years without issues. Also after the upgrade i see no errors of anykind .

Shall i leave it as it is and see how it goes? What do you think?

Thanks

@dsf
      $handle = @fopen($file, 'rb');

It just could not open some file... irrelevant.

Ok, it could be related to this:

PHP Warning:  require_once(/home/oc-admin/upgrade.php): failed to open stream: No such file or directory in /home/oc-admin/index.php on line 196

I had to manually copy the upgrade.php in there, for some reason it was not there.

Thanks !

Today i tried to upgrade a second site. Big, a lot of Countries.

I failed. The strange error is:

[04-Oct-2022 19:43:23 Europe/London] PHP Fatal error:  Uncaught Error: Call to undefined function convertAlert() in /home/oc-includes/osclass/upgrade-funcs.php:279
Stack trace:
#0 /home/oc-admin/upgrade.php(36): require()
#1 /home/oc-admin/index.php(149): CAdminUpgrade->doModel()
#2 {main}
  thrown in /home/oc-includes/osclass/upgrade-funcs.php on line 279

I bumped the PHP memory to 1 gb just in case (from 512), same error.

Any ideas?

Thanks

It seems something related to Alerts?

That is very old function, probably already removed.

/**
     * Convert alerts < 2.4, updating s_search with json encoded to based64.
     *
     * @param string $alert base64+serialized
     */


Deleting all the alerts (via DB) before upgrade, seems to solve this issue.