Hi All, We were experiencing some performance issues with our Management server and were identifying the problem to be with the php-fpm deamon. We read on the forum there is a know issue which can be corrected by making a modification to the zabbix.conf file, in the php-fpm.d directory. We noticed when in the php-fpm.d directory besides the zabbix.conf which is where the tweaks are to be made, there also resides a www.conf. Can someone share with us how the whole two web server conf files work. If we have to make a tweak to the zabbix.conf, does it also have to be made to the www.conf as well? We also noticed there is a restart command for the php-fpm (systemctl restart rh-php72-php-fpm) and a restart for apache (service apache2 restart​). Does one depend on the other to be restarted? Or can they be restarted separately, TIA
Ad Widget
Collapse
Web server on Zabbix has two conf files
Collapse
X
-
Each conf file in that php-fpm.d directory controls a separate pool of worker processes for php-fpm.
The zabbix.conf controls the settings for a pool of php-fpm workers that are dedicated to the Zabbix web front end. It has settings for things like how many workers to start, how many idle workers to keep around, and whether to have workers die off after serving so many requests.
The www.conf is for a default worker pool named 'www'. You're probably not using that pool, so you likely don't need to do much tuning in the www.conf file. However, if the www pool is starting a lot of idle workers that are never doing anything, you could certainly reduce the # of workers it starts and keeps around.
Apache and php-fpm work together when a PHP application is requested. Apache httpd proxies the request to php-fpm, which runs the PHP and sends the response back through the Apache httpd proxy connection. You need both for PHP. For non-PHP web requests, php-fpm is not involved. If you're making a configuration change to a php-fpm pool or to php-fpm in general, then only the php-fpm workers need to be restarted. In that case, you wouldn't need to restart Apache httpd.
Comment