swoole-src: A bug occurred in Swoole-v5.1.2, please report it
Please answer these questions before submitting your issue.
- What did you do? If possible, provide a simple script for reproducing the error.
update swoole in docker php ext
- What did you expect to see?
all working
- What did you see instead?
doesnt response laravel octane with swoole
- What version of Swoole are you using (show your
php --ri swoole)?
it says 5.1.2
- What is your machine environment used (show your
uname -a&php -v&gcc -v) ? Linux 1baab60a7013 5.15.146.1-microsoft-standard-WSL2 #1 SMP Thu Jan 11 04:09:03 UTC 2024 x86_64 Linux PHP 8.3.7 (cli) (built: May 10 2024 21:59:17) (NTS) Copyright © The PHP Group Zend Engine v4.3.7, Copyright © Zend Technologies /app $ gcc -v /bin/sh: gcc: not found
[2024-05-12 09:13:10 #19.0] WARNING Server::check_worker_exit_status(): worker(pid=30, id=2) abnormal exit, status=0, signal=11 A bug occurred in Swoole-v5.1.2, please report it. The Swoole developers probably don’t know about it, and unless you report it, chances are it won’t be fixed. You can read How to report a bug doc before submitting any bug reports:
https://github.com/swoole/swoole-src/blob/master/.github/ISSUE.md Please do not send bug reports in the mailing list or personal letters. The issue page is also suitable to submit feature requests.
OS: Linux 5.15.146.1-microsoft-standard-WSL2 #1 SMP Thu Jan 11 04:09:03 UTC 2024 x86_64 GCC_VERSION: 13.2.1 20231014 OPENSSL_VERSION: OpenSSL 3.1.4 24 Oct 2023 PHP_VERSION : 8.3.7
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 26 (10 by maintainers)
@HallexCosta @lv2u @error1001es @robinnydahl @modrink We have released Swoole v5.1.3, optimized a dynamic array. You can try Swoole v5.1.3 to see if this issue still exists.
Same here, using Laravel, Octane, Swoole
Image built using the following Dockerfile:
Trying to access the project with Octane & Swoole:
Additional info:
Can confirm it’s working on v5.1.1 (previous build)
@robinnydahl @modrink Perhaps some commits led to this issue.I’ll take some time to test it.
Hi all,
I’m afraid we have not yet had the time to fully make a reproducible case without sharing sensitive details, but I can confirm the issue is present in Swoole 5.1.2 and that reverting back to 5.1.1 solves the issue.
We have tested setting up a clean Laravel project with Octane using Swoole 5.1.2 inside a docker image running from
php:8.2-cli-alpineand usingmlocati/php-extension-installerto install Swoole. When reaching Swoole on port 8000 the service keeps running, the same goes for when we access it through NGINX inside the image as well.The NGINX config inside the image looks like this:
The problem actually occurs when we are running the requests through the Kubernetes Ingress Controller which is also using NGINX behind the scenes. After the first request is made through the Kubernetes Ingress Controller the Swoole service shuts down, after this we are also unable to reach the Swoole endpoint directly within the environment as well.
I can concur with @modrink that the issue is that the client closes the connection (HTTP 499), so there seems to be something wrong with the implementation in the HTTP server that was introduced in 5.1.2 and that it’s triggered mostly when using HTTP Proxies like NGNIX (with certain settings), Traefik and Cloudflare.
As mentioned we have not yet been able to reproduce this in a way to share yet.
Do you have the xdebug extension? If so, try not using it and see.
@NathanFreeman I’ve tried setting max_nesting_level to 50000 - but still seeing the same issue.
Actually - seeing the same issue with Swoole-v5.1.0 and Swoole-v5.1.1 Also tried xdebug 3.3.1 - but with the same result as xdebug 3.3.2.