• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Recent content by Jayfin3

  1. J

    Resolved Plesk not reloading service of custom PHP handler

    I understood, but so does the dedicated handler installed by plesk. Output of plesk bin php_handler --list, only the relevant lines: plesk-php81-fpm 8.1.14 8.1.14 8.1 fpm /opt/plesk/php/8.1/sbin/php-fpm /opt/plesk/php/8.1/bin/php /opt/plesk/php/8.1/etc/php.ini...
  2. J

    Resolved Plesk not reloading service of custom PHP handler

    Isn't that the exact same thing the FPM-dedicated created by Plesk handler does? Don't see any differences in the setup, except for the missing reload?
  3. J

    Resolved Plesk not reloading service of custom PHP handler

    I answered in the thread you linked.
  4. J

    Resolved Custom PHP versions: no systemctl reload is issued on a change of PHP handlers when changing from any custom handler to any other handler

    The difference in my case was that I tried to add another handler for the existing binaries: plesk bin php_handler --add -id plesk-php81-custom-fpm -displayname "8.1 custom" -path /opt/plesk/php/8.1/sbin/php-fpm -clipath /opt/plesk/php/8.1/bin/php -phpini /opt/plesk/php/8.1/etc/php.ini -type...
  5. J

    Resolved Plesk not reloading service of custom PHP handler

    Thank you very much. A small correction: "In such a case the pool config is not removed" is not correct. The file is removed, but the custom handler's service doesn't notice that because of the missing reload. That's why all that is needed for everything to work is a manual reload after you...
  6. J

    Resolved Plesk not reloading service of custom PHP handler

    Absolutely correct. The custom handler was installed using plesk bin php_handler --add, including the -service parameter. You can tell that Plesk knows about the correct service as it's restarted / reloaded correctly for example on changed setting or when switching a domain's handler to the...
  7. J

    Resolved Plesk not reloading service of custom PHP handler

    Thank you for your reply. To me it seems to be unrelated to the PHP version, as there's no systemctl reload being issued by Plesk, which is being issued when using default handlers - even PHP 8.1. If I issue the reload command myself, while Plesk is still trying to restart the new handler's...
  8. J

    Resolved Plesk not reloading service of custom PHP handler

    I have a strange issue with a custom PHP-FPM handler I added. Mostly, it's working perfectly, except for the issue below: When I switch a domain's PHP handler from my custom handler to another one, my custom handler's systemd service is not being reloaded. As a result, the service does not...
  9. J

    Resolved Xdebug stopped working after update to 3.2.0

    Nice! How are you using that separate systemd service? Did you register it as a PHP handler in Plesk? Are you using it in addition to the default service or instead of it?
  10. J

    Resolved Xdebug stopped working after update to 3.2.0

    Ok, I think I found the issue: I previously set xdebug.mode in /opt/plesk/php/8.1/etc/php-fpm.d/<domain>.conf using the UI. The result looks like this: php_value[xdebug.mode] = develop,debug,profile This worked with PHP 8.1.13 + Xdebug 3.1.5, but stoped working now. Setting xdebug.mode in...
  11. J

    Resolved Xdebug stopped working after update to 3.2.0

    Hello everyone, after a recent update from Xdebug 3.1.5 to 3.2.0 and PHP 8.1.13 to 8.1.14 Xdebug has stopped working. We didn't change the configuration at all, which also still looks perfectly fine in the output of phpinfo() For troubleshooting purposes, I set the following...
Back
Top