Php fpm логи ошибок

to get php-fpm errors in nginx error log you need:

as for nginx: it s enough just basic config

# cat default  | grep -v "#"


server {
    listen 80 default_server;
    listen [::]:80 default_server;

    root /var/www/html;

    index index.html index.htm index.nginx-debian.html;

    server_name _;
 
        index index.html;

    location / {
        try_files $uri $uri/ =404;
    }

    location ~ \.php$ {
        include snippets/fastcgi-php.conf;
    
        fastcgi_pass unix:/run/php/php7.0-fpm.sock;
    }

}

as for php-fpm the main setting is

log_errors = On

basically it s enough. but to be on the safe side i would suggest
to put the following block in php-fpm config(/etc/php/7.0/fpm/php.ini) :

[PHP]
...
error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT
display_errors = Off
display_startup_errors = On
log_errors = On
log_errors_max_len = 1024
ignore_repeated_errors = Off
ignore_repeated_source = Off
report_memleaks = On
track_errors = Off
html_errors = On

...

after that all php stack traces will be in

# tail /var/log/nginx/error.log 
2023/06/20 23:37:06 [error] 20307#20307: *1 FastCGI sent in stderr: "PHP message: PHP Parse error:  syntax error, unexpected '"asd"' (T_CONSTANT_ENCAPSED_STRING) in /var/www/html/php1.php on line 2" while reading response header from upstream, client: 127.0.0.1, server: _, request: "GET /php1.php HTTP/1.1", upstream: "fastcgi://unix:/run/php/php7.0-fpm.sock:", host: "localhost"
2023/06/20 23:48:40 [error] 20307#20307: *5 FastCGI sent in stderr: "PHP message: PHP Parse error:  syntax error, unexpected '"asd"' (T_CONSTANT_ENCAPSED_STRING) in /var/www/html/php1.php on line 2" while reading response header from upstream, client: 127.0.0.1, server: _, request: "GET /php1.php HTTP/1.1", upstream: "fastcgi://unix:/run/php/php7.0-fpm.sock:", host: "localhost"
2023/06/21 00:18:17 [error] 20307#20307: *7 FastCGI sent in stderr: "PHP message: PHP Parse error:  syntax error, unexpected '"asd"' (T_CONSTANT_ENCAPSED_STRING) in /var/www/html/php1.php on line 2" while reading response header from upstream, client: 127.0.0.1, server: _, request: "GET /php1.php HTTP/1.1", upstream: "fastcgi://unix:/run/php/php7.0-fpm.sock:", host: "localhost:4545"

if you want to see php stack traces not in nginx erorr file but
instead in a separate file you need to add error_log setting
that is

error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT
display_errors = Off
display_startup_errors = On
log_errors = On
error_log = /var/log/php-errors.log
log_errors_max_len = 1024
ignore_repeated_errors = Off
ignore_repeated_source = Off
report_memleaks = On
track_errors = Off
html_errors = On

also very important to create /var/log/php-errors.log manually and set proper
permisssions because php-fpm wont do that and will continue to transfer error
to nginx. so

# touch /var/log/php-errors.log
# chown www-data.www-data /var/log/php-errors.log
# systemctl restart php7.0-fpm

after that nginx error log /var/log/nginx/error.log will be empty
but all php-errors will be in /var/log/php-errors.log

PHP FPM

First of all we need to enable option catch_workers_output for fpm.

catch_workers_output boolean
Redirect worker stdout and stderr into main error log. If not set, stdout and stderr will be redirected to /dev/null according to FastCGI specs. Default value: no.

/usr/local/etc/php-fpm.d/www.conf (in my configuration)

• catch_workers_output = yes

sed -i '/^;catch_workers_output/ccatch_workers_output = yes' "/usr/local/etc/php-fpm.d/www.conf"

Or simply edit and save the file manually to uncomment line starting with ;catch_workers_output.

Then we need to configure log file names and locations.

Access log

If you want or need to activate access log at php level:

access.log string
The access log file. Default value: not set

• access.log = /var/log/php/fpm-access.log

sed -i '/^;access.log/caccess.log = /var/log/php/fpm-access.log' "/usr/local/etc/php-fpm.d/www.conf"

Or simply edit and save the file manually to uncomment line starting with ;access.log.

You will have this kind of output:

$ tailf var/logs/php/fpm-access.log
172.18.0.5 -  20/Feb/2017:13:07:39 +0100 "GET /app_dev.php" 200
172.18.0.5 -  20/Feb/2017:13:07:47 +0100 "POST /app_dev.php" 302
172.18.0.5 -  20/Feb/2017:13:07:47 +0100 "POST /app_dev.php" 302
172.18.0.5 -  20/Feb/2017:13:07:47 +0100 "GET /app_dev.php" 200
172.18.0.5 -  20/Feb/2017:13:07:48 +0100 "GET /app_dev.php" 302
172.18.0.5 -  20/Feb/2017:13:07:48 +0100 "GET /app_dev.php" 200

Error log

Of course in production we do not want to display errors to users:

• php_flag[display_errors] = off

sed -i '/^;php_flag\[display_errors\]/cphp_flag[display_errors] = off' "/usr/local/etc/php-fpm.d/www.conf"

Or simply edit and save the file manually to uncomment line starting with ;php_flag[display_errors].

Then we must enable error log and define the error log file location :

• php_admin_value[error_log] = /var/log/php/fpm-error.log
• php_admin_flag[log_errors] = on

sed -i '/^;php_admin_value\[error_log\]/cphp_admin_value[error_log] = /var/log/php/fpm-error.log' "/usr/local/etc/php-fpm.d/www.conf"
sed -i '/^;php_admin_flag\[log_errors\]/cphp_admin_flag[log_errors] = on' "/usr/local/etc/php-fpm.d/www.conf"

Or simply edit and save the file manually to uncomment lines starting with ;php_admin_value[error_log] and ;php_admin_flag[log_errors].

You will have this kind of output:

$ tailf var/logs/php/fpm-error.log
[20-Feb-2017 13:33:46 Europe/Paris] PHP Parse error:  syntax error, unexpected '8' (T_LNUMBER), expecting variable (T_VARIABLE) or '{' or '$' in /var/www/html/web/app_dev.php on line 26

You also could change log level:

log_level string
Error log level. Possible values: alert, error, warning, notice, debug. Default value: notice.

sed -i '/^;log_level/clog_level = error' "/usr/local/etc/php-fpm.d/www.conf"

Important

Log files must have correct access rights (owner) and must exist:

mkdir -p /var/log/php
touch /var/log/php/fpm-access.log
touch /var/log/php/fpm-error.log
chown -R www-data:www-data /var/log/php

PHP CLI

To enable php CLI errors, we need to add these lines into the (cli) php.ini file.

This configuration is for production not for debug or development.

error_reporting = E_ALL
display_startup_errors = Off
ignore_repeated_errors = Off
ignore_repeated_source = Off
html_errors = Off
track_errors = Off
display_errors = Off
log_errors = On
error_log = /var/log/php/cli-error.log

Conclusion

Using the given configuration you should have those logs:

$ ll var/logs/php              
total 256K
-rw-r--r-- 1 82 82    0 févr. 17 09:35 cli-error.log
-rw-r--r-- 1 82 82  64K févr. 20 13:34 fpm-access.log
-rw-r--r-- 1 82 82  186 févr. 20 13:33 fpm-error.log

Do NOT forget to enable log rotation, you will have:

$ ll var/logs/php              
total 256K
-rw-r--r-- 1 82 82    0 févr. 17 09:35 cli-error.log
-rw-r--r-- 1 82 82  390 févr. 17 09:35 cli-error.log-20170217
-rw-r--r-- 1 82 82  64K févr. 20 13:34 fpm-access.log
-rw-r--r-- 1 82 82  100 févr. 17 09:35 fpm-access.log-20170217.gz
-rw-r--r-- 1 82 82 172K févr. 18 02:00 fpm-access.log-20170218
-rw-r--r-- 1 82 82  186 févr. 20 13:33 fpm-error.log
-rw-r--r-- 1 82 82  374 févr. 17 09:35 fpm-error.log-20170217

PHP FPM handler can boost the website performance even on high traffic.

Sometimes, websites using PHP FPM show unexpected errors. And, the users may not have a clue on the underlying reason.

Fortunately, PHP fpm error reporting gives real-time details on the causes of the error. But, to make use of this we need to turn on error reporting for the website.

At Bobcares, we often get requests to fix PHP FPM errors as part of our Server Management Services.

Today, we’ll see how our Support Engineers set up PHP FPM error reporting and fix the related errors.

Importance of PHP FPM error reporting

PHP FPM error logging provides a simple but efficient solution for logging all errors into a log file. Also, the information they contain will give exact details of errors and the amount of time spent on tracking the root causes of errors.

For instance,

The entries in the PHP FPM error logs look like.

[22-Mar-2019 16:52:18] WARNING: [pool www] seems busy (you may need to increase pm.start_servers, or pm.min/max_spare_servers), spawning 32 children, there are 9 idle, and 89 total children

Luckily, it is very easy to troubleshoot after analyzing the PHP-FPM error log and our Support Engineers found that this error occurs due to the values of pm.min/max_spare_servers and pm.start_servers. Then we increased these two values in /etc/php-fpm.d/www.conf.

Similarly, another example of entries in the PHP FPM error logs.

[25-Apr-2019 16:28:20] WARNING: [pool www] server reached max_children setting (80), consider raising it

From the error log, we could identify that this error happens when pm.max_children setting reached its threshold value and our Support Engineers increased this value of pm.max_children in the PHP-FPM configuration file.

However, only a proper configuration of PHP FPM error reporting will provide useful entries to help fix the root cause of errors.

How we set up PHP FPM error reporting.

Now, let’s see how our Support Engineers set up PHP FPM error logging on servers.

To configure error logging for PHP-FPM,

1. Firstly, we need to configure log file names and location.

By default, we’re using www.conf pool config file or find php-fpm.conf or www.conf depending on what version of PHP-FPM you have installed. Here, we took /etc/php/7.0/fpm/pool.d/www.conf as an example.

2. So, we edit /etc/php/7.0/fpm/pool.d/www.conf file and uncomment “catch_workers_output=yes"

3. At last, we restart  php-fpm service.

How we nailed the errors related to PHP FPM error reporting

From our experience in managing server, we’ve seen that many customers had issues related to  PHP FPM error logging. Let’s take a look at the top problems and how we fix them.

Improper configuration settings

Recently, one of our customers had an issue PHP FPM error logging. He couldn’t find anything in the error log after enabled FPM error reporting.

Then, our Support Engineers found that he set up PHP-FPM error log in the wrong configuration file.

Therefore, we found the exact file location by using the following command.

ps aux | grep fpm

root 1508 0.0 1.5 367260 31380 ? Ss Nov05 0:11 php-fpm: master process (/etc/php/7.0/fpm/php-fpm.conf)
www-data 10231 0.0 2.7 453420 55540 ? S 15:10 0:03 php-fpm: pool www
www-data 13266 0.0 2.4 449892 50900 ? S 22:13 0:00 php-fpm: pool www
www-data 13572 0.0 1.8 372468 37740 ? S 23:14 0:00 php-fpm: pool www
user+ 13721 0.0 0.0 14512 980 pts/0 R+ 23:30 0:00 grep --color=auto fpm

Next, we edited /etc/php/7.0/fpm/php-fpm.conf and properly configured it.

That fixed the problem.

Incorrect permission/missing log file

Sometimes, PHP FPM error logging may not work as we expect even if we set up the right configuration. This can happen due to missing log files or lack of write permissions for a webserver on the log file.

For example, if the permission of error log fpm-php.www.log is incorrect, the error logging will not work properly. The same thing happens in the case of missing log files.

When a customer reported problems with error logging we executed the following command to verify the files. But, files were missing as per the logs below.

ls /usr/local/etc/php-fpm.d/fpm.log

ls: cannot access '/usr/local/etc/php-fpm.d/fpm.log': No such file or directory
ls: cannot access '/usr/local/etc/php-fpm.d': No such file or directory

Then our Support Engineers created the directory and log file fpm.log. And, then set up the right ownership.

This is how we fixed the error.

[Having trouble while setting up PHP FPM error reporting? We’ll fix it for you.]

Conclusion

In short, PHP FPM error logging provides a simple but efficient solution for logging all errors into a log file. Today, we saw how our Support Engineers set up PHP FPM error reporting and solved related issues.

var google_conversion_label = «owonCMyG5nEQ0aD71QM»;

In this blog i will explain how to configure the access, error and slow logs of php-fpm and to modify the format in which the logs are received.

Prerequisites:

Lets have an application that uses the php5-fpm module, in this case, we will use the WordPress Application running on a LEMP stack.

To enable the logs , two files are relevant, namely

i) /etc/php5/fpm/php-fpm.conf
ii) /etc/php5/fpm/pool.d/www.conf

Firstly, open the first file for editing

[js]vi /etc/php5/fpm/php-fpm.conf[/js]

Set the desired location for getting error logs. The line should look like:
error_log = /var/log/php5/error.log
Then save and exit

Next open the second file for editing

[js] vi /etc/php5/fpm/pool.d/www.conf [/js]

Look for the line containing the location of access.log and set it to the desired path.
ex: access.log = /var/log/php5/access.log

Understanding the access log format:

access.format = %R – %u %t \”%m %r%Q%q\” %s %f %{mili}d %{kilo}M %C%%”

%R : remote IP address
%u : remote user (you dont see these two in output of tail -f)

%t : server time of receiving request
%m : method
%r : request uri {Addidtional : %q:if query string exists, %Q: the ? character is query
string exists }
%s: status response
%f : script filename
%d : time taken to serve request (in mili seconds)
%M : peak memory allocated by php (in kilobytes)
%C : CPU used by request

Example:

[js]
%t %m %r %s %f %d %M %C
17/May/2015:09:41:04 +0000 «GET /wp-admin/install.php» 200 /var/www/wp-admin/install.php 218.177 2816 87.09%
[/js]

The format of the access log can be altered as per desire.

The path for slow log is defined is defined just beneath the block of access logs. Uncomment the line and set the desired path for getting slow logs.
slowlog = /var/log/php5/slow.log
Make sure to set the request_slowlog_timeout to the desired value. The line should look like :

Ex: request_slowlog_timeout = 10

At the bottom of the file set
php_admin_value[error_log] = /var/log/php5/error.log ##path of error.log
php_admin_flag[log_errors] = on

Create the directory(if it does not exist) where the logs are to be created.

[js]mkdir -p /var/log/php5[/js]

Restart the php5-fpm service

[js]service php5-fpm restart[/js]

Henceforth you will start getting the logs at the set path.