When you are getting some errors from PHP-FPM like “signal 11 (core dumped)” in your logs, you can need to generate some core dumps to understand what’s happening.
You first need to install some packages to allow you generating dumps:
apt-get install gdb php5-dbg
System core updates
You will then need to update some sysctl parameters. Those commands will request root access to be executed.
Obviously, you can change the directory in which one you want to put the core dumps depending on your configuration (here /opt/core/ is used):
echo '/opt/core/core-%e.%p' > /proc/sys/kernel/core_pattern
echo 0 > /proc/sys/kernel/core_uses_pid
ulimit -c unlimited
You can use several patterns for naming your core dumps files:
%% a single % character
%p PID of dumped process
%u (numeric) real UID of dumped process
%g (numeric) real GID of dumped process
%s number of signal causing dump
%t time of dump, expressed as seconds since the Epoch, 1970-01-01 00:00:00 +0000 (UTC)
%h hostname (same as nodename returned by uname(2))
%e executable filename (without path prefix)
%E pathname of executable, with slashes ('/') replaced by exclamation marks ('!').
%c core file size soft resource limit of crashing process (since Linux 2.6.24)
Update PHP-FPM config
Once system configuration performed, you will need to update php-fpm configuration as well.
Edit file /etc/php5/fpm/php-fpm.conf (or specific pool configuration file under pool.d directory) and uncomment following line:
rlimit_core = unlimited
Once done, restart php5-fpm service:
Your core dumps will now be created in the folder you indicated at the beginning as soon as a new core dump will be generated.
Check your core dumps
Check your PHP-FPM logs, and if you see something like:
[01-Jan-2015 05:30:15] WARNING: [pool www] child 547934 exited on signal 11 (SIGSEGV - core dumped) after 410.674135 seconds from start
Go to the folder you chose for storing core dumps and you will see your core dump files:
# ls -l /opt/core/*
-rw------- 1 www-data www-data 124512498 Jan 1 05:30 /opt/core/core-php5-fpm.547934
Analyze a core dump
Once core dump generated, you will need to analyze this file to see why this core dump has been generated.
For that, you will need to use a standard tool called gdb.
Use this command line with the new file just generated to launch a debug shell and start analysis:
gdb /usr/sbin/php5-fpm /opt/core/core-php5-fpm.547934
Once the shell is launched you can use different commands to analyze output like:
- backtrace: it will display the simple backtrace of core dump
- backtrace full: will display the full detailed backtrace
(gdb) bt full
You will so get the backtrace of code that generated this core dump and be able to debug the application easily!
WARNING: Be careful to those core dumps which can be quite big and take lots of disk space very quickly if lots of core dumps are generated.