Hide Forgot
Description of problem: The customer is using nginx, rh-php56, rh-php56-fpm(listening on unix socket), and running the application Tyop3 on RHEL-7.2. They have provided the arbt report with coredump ccpp-2016-10-18-12-02-55-13977.tgz will be attached #reason: php-fpm killed by SIGSEGV #exploitable: Likely crash reason: Jump to an invalid address Exploitable rating (0-9 scale): 6 #coredump <--- need help #var.log.messages Oct 18 12:02:55 hbg-internet-p2.dpa.com kernel: php-fpm[13977]: segfault at 50 ip 00007f96e85e8694 sp 00007fff6f5ec390 error 4 in php-fpm[7f96e838c000+3a0000] Cheers.
We faced same problem after major updates CentOS 7.2 => 7.3. We use Nginx 1.10.2 from repo epel, PHP-fpm 5.6.29 from repo remi-php56, MySQL Oracle 5.7.17 from repo mysql57-community. abrt report join (abrt_report_2017-01-14_06_05_26.txt). Main infos : reason: php-fpm killed by SIGSEGV cmdline: 'php-fpm: master process (/etc/php-fpm.conf)' executable: /usr/sbin/php-fpm package: php-fpm-5.6.29-1.el7.remi kernel: 3.10.0-514.2.2.el7.x86_64 os_release: CentOS Linux release 7.3.1611 (Core) pkg_name: php-fpm pkg_release: 1.el7.remi pkg_vendor: Remi Collet pkg_version: 5.6.29 exploitable: :Likely crash reason: Jump to an invalid address :Jan 14 05:56:17 my.server.com kernel: php-fpm[54429]: segfault at 5fc01 ip 00007f3ec466a965 sp 00007ffc9acff9f8 error 4 in libc-2.17.so[7f3ec452f000+1b6000] :Jan 14 05:56:17 my.server.com abrt-hook-ccpp[54573]: Process 54429 (php-fpm) of user 992 killed by SIGSEGV - ignoring (repeated crash) :Jan 14 06:05:26 my.server.com systemd[1]: php-fpm.service: main process exited, code=dumped, status=11/SEGV :Jan 14 06:05:26 my.server.com systemd[1]: Unit php-fpm.service entered failed state. :Jan 14 06:05:26 my.server.com systemd[1]: php-fpm.service failed.
Created attachment 1241781 [details] abrt report
@Malo Pichot, sorry bu we can only support RH official package here. @Patrick This look like stack exhaustion. Would it be possible: - to try running with a higher stack size ? - to have a small reproducer ?
Red Hat does not currently plan to provide any further changes to this collection in a Red Hat Software Collections update release. This software collection is nearing the retirement date (April 2018) after which customers are encouraged to upgrade to a later release. Please contact Red Hat Support if you have further questions, or refer to the support lifecycle page for more information. https://access.redhat.com/support/policy/updates/rhscl/
In accordance with the Red Hat Software Collections Product Life Cycle, the support period for this collection has ended. New bug fix, enhancement, and security errata updates, as well as technical support services will no longer be made available for this collection. Customers are encouraged to upgrade to a later release. Please contact Red Hat Support if you have further questions, or refer to the support lifecycle page for more information. https://access.redhat.com/support/policy/updates/rhscl/