James Heinrich
New Pleskian
- Server operating system version
- Ubuntu 22.04.5 LTS (GNU/Linux 5.15.0-139-generic x86_64)
- Plesk version and microupdate number
- Plesk Obsidian 18.0.69 Update #2, Web Host Edition
I noticed the automated "Package Update Manager notification" emails contained an error message for the last few days ("ERROR: Apt cache fetch failed: E:Repository 'Index of /ondrej/php/ubuntu jammy InRelease' changed its 'Label' value from '***** The main PPA for supported PHP versions with many PECL extensions *****' to 'PPA for PHP'"). Looking in Plesk I noticed it had failed to check for updates since 2025-Apr-27 (presumably due to the above error). Attempting to fix this, I manually ran "apt update" and confirmed that I wanted to use the new name. I believe I then also ran "apt upgrade" and it installed some updates. And I think that was my mistake.
Now, later the same day, I'm getting emails "Cron <root@servername> cd / && run-parts --report /etc/cron.hourly" with message contents:
And then I tried to run a PHP script that connects to a MariaDB database (which worked perfectly fine yesterday) and it tells me:
"PHP Fatal error: Uncaught Error: Class "mysqli" not found in ..."
I tried enabling mysqli extension in /etc/php/8.4/cli/php.ini without success (all the extensions are commented-out there)
So I think I unwittingly clobbered the Plesk PHP-CLI installation (which may have been v7.4 but I'm not certain) and now I've got PHP 8.4.6 which it certainly wasn't before.
The question is either:
a) how do I revert the PHP-CLI configuration to what Plesk is expecting
or
b) how do I make PHP 8.4.6 play nice with Plesk and my command-line calls to scripts that require mysqli and/or other extensions.
Assume there is no viable Plesk backup available. I tried the Plesk "Diagnose & Repair" extension and it did not help.
Now, later the same day, I'm getting emails "Cron <root@servername> cd / && run-parts --report /etc/cron.hourly" with message contents:
/etc/cron.hourly/plesk-php-cleanuper:
/usr/lib/plesk-9.0/maxlifetime: line 16: [:
Deprecated: PHP Startup: session.sid_length INI setting is deprecated in Unknown on line 0
Deprecated: PHP Startup: session.sid_bits_per_character INI setting is deprecated in Unknown on line 0
1440: integer expression expected
/usr/lib/plesk-9.0/maxlifetime: line 16: [:
Deprecated: PHP Startup: session.sid_length INI setting is deprecated in Unknown on line 0
Deprecated: PHP Startup: session.sid_bits_per_character INI setting is deprecated in Unknown on line 0
1440: integer expression expected
And then I tried to run a PHP script that connects to a MariaDB database (which worked perfectly fine yesterday) and it tells me:
"PHP Fatal error: Uncaught Error: Class "mysqli" not found in ..."
I tried enabling mysqli extension in /etc/php/8.4/cli/php.ini without success (all the extensions are commented-out there)
So I think I unwittingly clobbered the Plesk PHP-CLI installation (which may have been v7.4 but I'm not certain) and now I've got PHP 8.4.6 which it certainly wasn't before.
The question is either:
a) how do I revert the PHP-CLI configuration to what Plesk is expecting
or
b) how do I make PHP 8.4.6 play nice with Plesk and my command-line calls to scripts that require mysqli and/or other extensions.
Assume there is no viable Plesk backup available. I tried the Plesk "Diagnose & Repair" extension and it did not help.