-
Notifications
You must be signed in to change notification settings - Fork 63
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
Agent 10.22.0.12 & 11.2.0.15 on php 7.4 PHP 7.4.33 in agent/php_user_instrument.c #968
Comments
Thank you for your issue report. A member of the New Relic PHP Agent Team will review your report and endeavor to respond in a timely manner. |
This issue has been identified as requiring additional information to debug. Due to the potentially sensitive nature of the information we may have to collect, such as PHPInfo and Debug Logs, please follow these steps to create a support case, where a member of our New Relic Support Team will work with you to gather the necessary information securely and help debug your issue. |
This issue requires more information and/or work. |
Further evaluation was done directly together with Neil & Co from the NewRelic support team:
These issues most likely should not lead to a segfault in the agent - but at least there are workarounds one can implement once you know what you've to look for. Shout out to Neil and the whole NewRelic support team for going through the ton of logs with us and providing helpful insights which allowed us to workaround the issues. It was a pleasure to do some bug-squashing with you. Cheers, |
Description
We've been seeing random stack failures on one of our last php 7.4 systems.
Once core dumps were enabled we could see that in all of the core dumps the nr agent was involved.
As we saw that the NR agent was involved we upgraded to the latest version of it 10.22.0.12 -> 11.2.0.15 but within hours we had another segfault.
Below you'll find a excerpt of backtraces from the collected core dumps.
For the moment we decided to see if disabling the agent via
newrelic.enabled
stops the failures.If that doesn't work we'll completely disable the extension to see if that helps.
Since the failures are random and it can take more than a week between occurrences this is a ongoing process.
Steps to Reproduce
We haven't found any specific steps which would trigger the issue. Sometimes it was working for a week without issues, then we had multiple failures within a couple of hours.
Relevant Logs / Console output
11.2.0.15
Agent - 11.2.0.15 -core.php-fpm.5978.e79a3bcdf9fd.1727959653.log
10.22.0.12
Agent - 10.22.0.12 -core.php-fpm.397963.7a8065e6c40b.1727937097.log
Agent - 10.22.0.12 -core.php-fpm.399674.7a8065e6c40b.1727937092.log
Agent - 10.22.0.12 - core.php-fpm.796057.14037af4a05c.1727859777.log
Your Environment
System-Info:
Docker image based on official build: https://hub.docker.com/layers/library/php/7.4-fpm/images/sha256-7c6a2cba718f37c4b3ca3486476c7d3dc68dc3ea9b12bde9c57bd4b8d9479fc0?context=explore
PHP-Version
PHP enabled Extensions
Additional context
The text was updated successfully, but these errors were encountered: