-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SIGSEGV in php-fpm #275
Comments
ps: It would be nice to have to be able to build php/module binaries with debug symbols with the Dockerfiles with only slight modifications. Currently you have to figure it out yourselves. |
I have decided to use the standard packages from alpine - less problematic is getting the debug symbols. At this point I am not sure this is related to alpine (musl) or php itself (imagick). Here is the backtrace.
|
I am really just googling Valgrind here. This is all I got.
|
Created a bugreport on Alpine: https://bugs.alpinelinux.org/issues/6021 |
+1 I am having this same exact issue. I have even tried using graphicsmagick, but after successfully installing gmagick via PECL, I get a SIGSEGV when starting PHP. Testing with the Debian version now, everything is working great. |
+1 I am seeing this issue
|
Possible workaround: dmstr/docker-php-yii2@58a9b1b Or you need to wait for PHP (Alpine) 7.2.x, since this is using Alpine-3.6 |
So this is solved by PHP 7.2 and/or Alpine 3.6+? (and thus #504) |
I think this is solved by Alpine 3.6, probably related to it's C-compiler. CC: @handcode |
I am also getting ImageMagick segfaults on all Alpine 3.4-based images. The fix is to use a newer version of ImageMagick, but that would require someone to backport the updated 6.9.x branch of ImageMagick to Alpine 3.4 (and apply the security patches that are still relevant). Alternately, this problem goes away completely if the PHP <= 7.1 docker images are moved to a newer version of Alpine - preferably Alpine 3.6+ since they include ImageMagick 7. I don't know why they aren't built for Alpine 3.6+ today, but I'm happy to help if it's a resource problem. |
Our php-fpm got SEGV today, is there a simple way to enable debug symbol? Normally -g -O2 flag should not impact performance, should we enable it by default? |
Hello,
I'd like to get some help troubleshooting and fixing this issue I have.
As a base image I am using the '5-fpm-alpine' variant of the images, latest version as of today.
I have added several core and pecl modules with the way as it is described in it's docker hub page.
php-fpm servs - among others - an ownCloud installation which is constantly causing php-fpm to fail with SIGSEGV.
I managed to get core files - however even though I recompiled php with --enable-debug and skipped stripping the symbols from the binaries - but gdb shows nothing useful for me. (I am not a developer)
bash-4.3# gdb -c coredump-php-fpm.11 /usr/local/sbin/php-fpm
GNU gdb (GDB) 7.11
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-alpine-linux-musl".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/.
Find the GDB manual and other documentation resources online at:
http://www.gnu.org/software/gdb/documentation/.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/local/sbin/php-fpm...done.
[New LWP 11]
warning: Can't read pathname for load map: No error information.
Core was generated by `php-fpm:'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007ffa3365e80f in free () from /lib/ld-musl-x86_64.so.1
(gdb) bt
#0 0x00007ffa3365e80f in free () from /lib/ld-musl-x86_64.so.1
#1 0x0000000000000020 in ?? ()
#2 0x00007ffa3365f0e8 in memalign () from /lib/ld-musl-x86_64.so.1
#3 0x00005647f095a0a0 in ?? ()
#4 0x00005647f0899680 in ?? ()
#5 0x00005647f0959fc0 in ?? ()
#6 0x0000000000000001 in ?? ()
#7 0x0000000000000000 in ?? ()
(gdb)
dmesg:
[403674.575650] traps: php-fpm[7246] general protection ip:7ffa3365e80f sp:7ffeca2ed950 error:0 in ld-musl-x86_64.so.1[7ffa3363b000+88000]
[403675.578962] traps: php-fpm[7247] general protection ip:7ffa3365e80f sp:7ffeca2ed950 error:0 in ld-musl-x86_64.so.1[7ffa3363b000+88000]
syslog:
Jul 29 11:50:36 localhost docker/balagedocker_php5-fpm_1[15585]: [29-Jul-2016 09:50:36] WARNING: [pool www] child 11 exited on signal 11 (SIGSEGV - core dumped) after 81.363321 seconds from start
Jul 29 11:50:36 localhost docker/balagedocker_php5-fpm_1[15585]: [29-Jul-2016 09:50:36] NOTICE: [pool www] child 27 started
Jul 29 11:50:37 localhost docker/balagedocker_php5-fpm_1[15585]: [29-Jul-2016 09:50:37] WARNING: [pool www] child 12 exited on signal 11 (SIGSEGV - core dumped) after 82.337205 seconds from start
Jul 29 11:50:37 localhost docker/balagedocker_php5-fpm_1[15585]: [29-Jul-2016 09:50:37] NOTICE: [pool www] child 28 started
That's all I got.
I am attaching the Dockerfile I used to build the image. Also some core files if
cores.zip
supervisord.txt
Dockerfile.txt
Host is openSUSE Leap 42.1 x86_64 (kernel 4.1.27-27-default)
Any help is appreciated.
The text was updated successfully, but these errors were encountered: