Resolved PHP 8.2 - Memcached Extension Not Available

[LuigiMdg]

Server operating system version

AlmaLinux 9

Plesk version and microupdate number

Plesk Obsidian v18.0.53_build1800230619.12

Greetings,
in the list of available extensions for PHP 8.2, the Memcached extension is not available, why?

JustPaste.it - Share Text & Images the Easy Way

justpaste.it

 

[Peter Debik]

Why it is not included by default I do not know, but if you want to add it, maybe this KB article can help:

https://support.plesk.com/hc/en-us/articles/12377651968023

 

[LuigiMdg]

Sorry but I expected much better from Plesk..
For anything a little more complicated, you still have to get your hands dirty with the terminal, so you might as well go back to Webmin + Virtualmin, at least they're free..

 

[LuigiMdg]

Why it is not included by default I do not know, but if you want to add it, maybe this KB article can help:

https://support.plesk.com/hc/en-us/articles/12377651968023

Anyway I followed the procedure, at the point service plesk-php82-fpm restart, the service is not restarted.

Job for plesk-php82-fpm.service failed because the control process exited with error code.
See "systemctl status plesk-php82-fpm.service" and "journalctl -xeu plesk-php82-fpm.service" for details.

Then:

Jul 16 23:40:58 vmi1354264.contaboserver.net php-fpm[3380534]: [16-Jul-2023 23:40:58] WARNING: Nothing matches the include pattern '/opt/plesk/php/8.2/etc/php-fpm.d/*.conf' from /opt/plesk/php/8.2/etc/php-fpm.conf at line 119.
Jul 16 23:40:58 vmi1354264.contaboserver.net php-fpm[3380534]: [16-Jul-2023 23:40:58] ERROR: No pool defined. at least one pool section must be specified in config file
Jul 16 23:40:58 vmi1354264.contaboserver.net php-fpm[3380534]: [16-Jul-2023 23:40:58] ERROR: failed to post process the configuration
Jul 16 23:40:58 vmi1354264.contaboserver.net php-fpm[3380534]: [16-Jul-2023 23:40:58] ERROR: FPM initialization failed

 

[Peter Debik]

In order to start the daemon, at least one website must be configured to use that PHP version. When you configure a domain to use that PHP version, it should automatically start the service along with the configuration, because then a pool configuration will exist.

 

[LuigiMdg]

In order to start the daemon, at least one website must be configured to use that PHP version. When you configure a domain to use that PHP version, it should automatically start the service along with the configuration, because then a pool configuration will exist.

It wasn't due to that as it was already running on the domain, however upon reboot it would appear to have booted up fine, thanks.