Swoole 问题 asleep - deadlock 以及 HTTP -1 Unknown: Connect timeout! the server is not listening on the port or the network is missing!

发表于2023-04-03|更新于2023-04-03|踩坑教训

|评论数:

问题代码

// 批量请求接口
$responseList = SaberGM::list([

    // 深度接口地址
    'uri' => $urlList,

    // 代理列表
    'proxy' => $proxyList,
]);

php swoole 版本 4.6.4

swoole

Swoole => enabled
Author => Swoole Team <team@swoole.com>
Version => 4.6.4
Built => Mar 11 2021 14:42:19
coroutine => enabled with boost asm context
trace_log => enabled
epoll => enabled
eventfd => enabled
signalfd => enabled
cpu_affinity => enabled
spinlock => enabled
rwlock => enabled
sockets => enabled
openssl => OpenSSL 1.0.2k-fips  26 Jan 2017
http2 => enabled
json => enabled
curl-native => enabled
pcre => enabled
zlib => 1.2.7
mutex_timedlock => enabled
pthread_barrier => enabled
futex => enabled
mysqlnd => enabled
async_redis => enabled

Directive => Local Value => Master Value
swoole.enable_coroutine => On => On
swoole.enable_library => On => On
swoole.enable_preemptive_scheduler => Off => Off
swoole.display_errors => On => On
swoole.use_shortname => On => On
swoole.unixsock_buffer_size => 8388608 => 8388608

[FATAL ERROR]: all coroutines (count: 1) are asleep - deadlock!

Fatal error: Uncaught Swlib\Http\Exception\ConnectException: HTTP -1 Unknown: Connect timeout! the server is not listening on the port or the network is missing! in 
/vendor/swlib/saber/src/Request.php:641

诶查了很多文档, 最后还是选择不使用代理注释代理代码问题就解决了. 但也不是个办法希望后面会有时间解决下问题吧.

Uncaught SwlibHttpExceptionConnectException:Connect timeout! the server is not listening on the port or the network is missing! #22

Swoole 出现 deadlock 字样

SwlibSaberGM

文章作者: Leon

文章链接: https://tago.top/archives/cbe0ed8f.html

版权声明: 本博客所有文章除特别声明外，均采用 CC BY-NC-SA 4.0 许可协议。转载请注明来源 Leon！

相关推荐

Swoole WARNING Worker_reactor_try_to_exit() (ERRNO 9101): worker exit timeout, forced termination

swoole 遇到一个定时器 tick 的问题 WARNING Worker_reactor_try_to_exit() (ERRNO 9101): worker exit timeout, forced termination 今天突然发下 swoole 报错了，后来找资料才发现原来是定时器的问题，大概是说定时器设置的时间大于进程退出的时间了官方文档 : worker exit timeout, forced to terminate发现形如以下报错： WARNING swWorker_reactor_try_to_exit (ERRNO 9012): worker exit timeout, forced to terminateCopy to clipboardErrorCopied 表示在约定的时间 (max_wait_time 秒) 内此 Worker 没有退出，Swoole 底层强行终止此进程。可使用如下代码进行复现： use Swoole\Timer;$server = new Swoole\Server('127.0.0.1', ...

[踩坑] Swoole 4.2.11低版本不抛错执行不同静态方法一定次数进程异常退出 `PHP Deprecated: Non-static method `

很久之前运维同学通知我线上服务器产生大量 core.15…. 文件磁盘快占满了我没在意.今天发现线上有个服务的否个进程运行出了问题.找了一下午问题. 都没找明白 . 想起每次找swoole官方回复都是版本太低, 先升级到最新版本. 抱着试试看的心态. 升级swoole 到 4.4.12 在运行发现如下错误: PHP Deprecated: Non-static method Controller\Test::func() should not be called statically in /data/application/QuantPlatform/script/src/Controller/Test.php on line 41PHP Deprecated: Swoole\Timer::swoole_timer_tick() expects parameter 2 to be a valid callback, non-static method Controller\Test::func() should not be called statically...

Swoole 异常疑难杂症求解

问题很难搞呀下面是抛错 [2019-08-26 11:08:03 $26288.0] WARNING swManager_check_exit_status: worker#1 abnormal exit, status=0, signal=11A bug occurred in Swoole-v4.2.12, 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/issues/2000Please do not send bug reports in the mailing list or personal letters.The...

Swoole onClose handler error. Http onRequest handler error.

接口调用一个不存在的类长时间不回显. 客户端主动断链抛错 PHP Warning: SwooleServer::start(): onClose handler error接下来再次请求直接不回包抛错 PHP Warning: SwooleServer::start(): Http onRequest handler error. 请求其他正常接口仍不回显, 抛上述错误. 再次请求这个进程仍是抛错直到 worker 进程死掉才会抛 PHP Warning: SwooleServer::start(): onWorkerStop handler errorPHP Fatal error: Uncaught Error: Class 'ControllerWebTest' not found 抛错:PHP Warning: Swoole\Server::start(): onClose handler error. PHP Warning: Swoole\Server::start(): Http onRequest handler erro...

Swoole : wManager_check_exit_status: worker#5 abnormal exit

解决 Swoole : wManager_check_exit_status: worker#5 abnormal exit在使用 Swoole 进行服务开发时，有时可能会遇到类似 “wManager_check_exit_status: worker#5 abnormal exit” 的错误信息，提示某个 Worker 进程异常退出。这种错误通常是由于 Worker 进程在执行过程中遇到了问题导致的。本文将介绍可能导致这个错误的一些常见原因以及解决方法。原因分析出现 “wManager_check_exit_status: worker#5 abnormal exit” 错误的原因可能包括但不限于：代码问题：Worker 进程执行的代码存在逻辑错误、异常或者死循环，导致进程异常退出。资源限制：Worker 进程可能受到系统资源限制，例如内存限制、文件描述符限制等，导致进程异常退出。协程使用不当：如果代码中使用了协程，可能会出现协程使用不当导致的异常退出。 PHP 版本不兼容：Swoole 的不同版本对 PHP 版本的兼容性可能存在差异，使用不兼容的 PHP 版本可...

[踩坑] Swoole 抛错记录

近期遇到三个swoole 的抛错日志, 很头疼有的有解释有的并没有, 但总体也算是解决了问题. [2023-11-21 19:44:02<.978122> #9118.2] WARNING del (ERRNO 800): failed to delete events[430], it has already been removed[2023-11-21 22:17:28<.225417> *19693.61] WARNING Worker_discard_data (ERRNO 1007): [2] ignore data[1272 bytes] received from session#15689[2023-11-18 09:15:07 *22844.90] WARNING send_blocking(:206): send 40 bytes failed, Error: Resource temporarily unavailable[11] 问题如上 3种抛错, 数据都是swoole抛错日志, 需要注意的是 : 在Swoole 日...

评论

数据加载中