Bug #79395 [Opn->Fbk]: SIGABRT from child when accessing website
| From: | requinix@php.net | Date: | Wed, 18 Mar 2020 14:53:27 +0000 |
| Subject: | Bug #79395 [Opn->Fbk]: SIGABRT from child when accessing website | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-226162@lists.php.net to get a copy of this message | ||
Edit report at https://bugs.php.net/bug.php?id=79395&edit=1
ID: 79395
Updated by: requinix@php.net
Reported by: antony dot landsman at verticacrm dot com
Summary: SIGABRT from child when accessing website
-Status: Open
+Status: Feedback
Type: Bug
Package: FPM related
Operating System: Centos 8.1.1911 (Core)
PHP Version: 7.3.15
Block user comment: N
Private report: N
New Comment:
Not enough information was provided for us to be able
to handle this bug. Please re-read the instructions at
http://bugs.php.net/how-to-report.php
If you can provide more information, feel free to add it
to this bug and change the status back to "Open".
Thank you for your interest in PHP.
You can still get a stack trace with a release build, but it won't be as useful.
Try with all modules and zend_modules disabled? How about 7.3.16, which was tagged yesterday and
will be announced tomorrow?
Previous Comments:
------------------------------------------------------------------------
[2020-03-18 14:42:53] antony dot landsman at verticacrm dot com
Description:
------------
I recently built a copy of 7.3.15. When I try to access my website (running on NGINX) I get a 502
error. In looking at the logs I see that the child process is terminating with a SIGABRT (Signal
6). In order to gather more information, I created a debug build. To my surprise, with the debug
build the site works perfectly. Sort of a catch 22, because as IU understand it, I cannot get a
stack trace without a debug build.
------------------------------------------------------------------------
--
Edit this bug report at https://bugs.php.net/bug.php?id=79395&edit=1