-
Notifications
You must be signed in to change notification settings - Fork 69
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
Function Callback loop SEGFAULT #651
Comments
PHP MODULES
|
I think this is related too: #634 We are also seeing same issue |
This issue is not present in 1.3.1, we reverted and it fixed it @pjaak |
Possibly related to -- or duplicate of -- #636 . |
We encounter the same using CentOS 7 + PHP 7.4 + ElasticAPM 1.5.2 |
@pjaak @doyelese @atc-cegodk @mcouillard Could you please check if you still experiencing the issue with the latest release (v.16) and if so could you please share a simple docker image definition that reproduces this issue? |
I'm seeing an improvement, but still some new ERROR logs that are not present when using 1.3.1 (we're still on PHP 7.4 and using an ElasticAPM log level of ERROR)
|
Here's more detail behind the CRITICALs we see (even on APM 1.6.1), apparently triggered during every PHP PID recycle (happens fairly often due to PHP-FPM job lifetimes).
|
I think this is also related to #831 the segfault can be reproduced with something like: <?php
switch ( 1 ) {
case 1:
continue;
}
echo 'Done' . PHP_EOL; Which segfaults PHP when using the APM module and produces the following warning when
The core dump for the segfault also loops over the same
|
Hey @xyu, @mcouillard, @pjaak @doyelese I wasn't able to reproduce issue mentioned by @xyu with latest release https://github.com/elastic/apm-agent-php/releases/tag/v1.8.4 and PHP 8.2. Could you please verify it on yours environment? If it still causes issues, please reopen issue Best regards, |
Describe the bug
A clear and concise description of what the bug is.
When enabled on a Centos 7 apache + php-fpm server elastic-apm module causes an Apache 503 and kills the children processes super quick. This is only happening with some of our PHP pages.
To Reproduce
Steps to reproduce the behavior:
Access PHP page that gives behaviour
Expected behavior
A clear and concise description of what you expected to happen.
Not cause an HTTP 503
Core Dump
This goes on in a loop
The text was updated successfully, but these errors were encountered: