Custom httpd changes not taking effect in PHP 8.1

cyberda

Verified User
Joined
Oct 20, 2020
Messages
21
Location
Spain
Hello,

I have been able to verify that the changes made in custom httpd do not take effect and finally I have to restart the php-fpm service manually. It only happens in PHP 8.1. I do not know if also in 8.0.

In the other versions, Directadmin takes care of doing it automatically by displaying the following message in /var/log/directadmin/system.log:

2022:10:25-20:53:14: php-fpm74 restarted

Does anybody know what is it due to?
Thank you.
Kind regards.
 
Hello,

The custom httpd changes are applied to a web-server Apache, Nginx, OLS, LS. Why should it restart PHP-FPM? Changes for PHP-FPM should be done in "PHP-FPM config customization" section. If you do changes in "PHP-FPM config customization" and a corresponding PHP-FPM process does not reload/restart then you might check Directadmin logs under /var/log/directadmin/ for possible clues. If already checked and nothing found, then you might open a ticket with Directadmin support and let them check your setup.
 
Hi,

Inside custom2 of PHP-FPM 8.1 you put some variable. I have also tested it on several servers:

What you do see is that it launches the following:
PHP 8.1
tail -f /usr/local/directadmin/data/task.queue
action=php%2Dfpm%38%31&value=restart

/var/log/directadmin/system.log
empty

Same test with PHP 5.6, 7.X and 8.0 works correctly. Example:

PHP 5.6
tail -f /usr/local/directadmin/data/task.queue
action=php%2Dfpm%35%36&value=restart

/var/log/directadmin/system.log
2022:10:26-03:56:17: httpd reloaded
2022:10:26-03:56:17: php-fpm56 reloaded
2022:10:26-03:56:17: php-fpm74 reloaded
2022:10:26-03:56:17: php-fpm81 reloaded
2022:10:26-03:58:16: php-fpm56 restarted <<<<<<<<<<<<<

As you can see by not performing a PHP 8.1 subtract the changes in PHP-FPM custom2 are not applied as in the other versions and a manual restart of the service is necessary for the changes to be applied.

Thank you.

Kind regards.
 
If this is the case, you might open a ticket with DirectAdmin support. They will investigate the case and fix DirectAdmin if it's required. Forums users have nothing to offer here, but check it on their server and/or suggest a way to bypass it.
 
Back
Top