Open jpvdw86 opened 2 weeks ago
Small update. We just disabled worker mode and now its working without any segmentation faults
Would you manage to gather a stack trace? This is the only way we can get an idea of what's going on :/
Could you also try with worker mode with op_cache
disabled?
In certain situations, we experienced significant issues with gmagick. As a result, we reverted to PHP 8.2 with imagick, which resolved some of the problems.
However, segmentation faults still occur frequently. To address this, we disabled the opcache preload function. It seemed to reduce the errors somewhat, but this observation is based purely on intuition. We have not fully disabled opcache to test further. @Alliballibaba2
@dunglas Unfortunately, I was unable to generate a stack trace or kernel dumps. We rolled back the environment to a version without FrankenPHP. On the test environment, I couldn't reproduce the issue, likely due to insufficient load to simulate the real-world scenario.
We also performed a load test with K6, but everything ran smoothly during testing. The issue arises only under real-time conditions, where large amounts of data and forms are processed. This is challenging to replicate in a controlled test environment. The application in question is an internal tool used to streamline business processes and is protected behind SSO authentication.
What happened?
We are running FrankenPHP (non-static variant) in Docker on our Kubernetes platform. This is in worker mode with a Symfony application. The application seems to work well; however, as traffic increases, we regularly encounter segmentation fault errors.
We have already rolled back from the PHP 8.3 variant with Gmagick because we were getting errors during some crons with the message, "Disconnected 'Magick: abort due to signal 11 (SIGSEGV) Segmentation Fault' ... Aborted (core dumped)."
We have therefore reverted to PHP 8.2 with Imagick. The "Magick abort" error is gone, but we still sporadically experience segmentation faults.
In the documentation, I read about the OpenSSL bug, but this only applies to the static build, correct? Additionally, we are following the recommendation to use the provided Docker image.
Base dockerfile
Build Type
Docker (Debian Bookworm)
Worker Mode
Yes
Operating System
GNU/Linux
CPU Architecture
x86_64
PHP configuration
Relevant log output
Caddyfile
EDIT: Another error appears, maybe related ?