首页
下载
文档
社区
视频
捐赠
源代码
赞助商
AOT 编译器
AI 助理
商业产品
PHP AOT 原生编译器
Swoole-Compiler 代码加密器
CRMEB 新零售社交电商系统
登录
注册
全部
提问
分享
讨论
建议
公告
开发框架
CodeGalaxy
发表新帖
WARNING swManager_check_exit_status: worker#0 abnormal exit, status=0, signal=11
[2017-05-17 20:43:52 $13696.0] WARNING swManager_check_exit_status: worker#0 abnormal exit, status=0, signal=11 [2017-05-17 20:46:13 $13696.0] WARNING swManager_check_exit_status: worker#1 abnormal exit, status=0, signal=11 [2017-05-17 20:48:57 $13696.0] WARNING swManager_check_exit_status: worker#2 abnormal exit, status=0, signal=11 [2017-05-17 20:50:24 $13696.0] WARNING swManager_check_exit_status: worker#0 abnormal exit, status=0, signal=11 [2017-05-17 20:50:36 $13696.0] WARNING swManager_check_exit_status: worker#1 abnormal exit, status=0, signal=11 [2017-05-17 20:52:58 $13727.0] WARNING swManager_check_exit_status: worker#0 abnormal exit, status=0, signal=11 [2017-05-17 20:53:43 $13727.0] WARNING swManager_check_exit_status: worker#1 abnormal exit, status=0, signal=11 [2017-05-17 20:24:59 $13644.0] WARNING swManager_check_exit_status: worker#0 abnormal exit, status=0, signal=11 [2017-05-17 20:25:55 $13644.0] WARNING swManager_check_exit_status: worker#1 abnormal exit, status=0, signal=11 [2017-05-17 20:28:56 $13644.0] WARNING swManager_check_exit_status: worker#2 abnormal exit, status=0, signal=11 [2017-05-17 20:31:18 $13644.0] WARNING swManager_check_exit_status: worker#0 abnormal exit, status=0, signal=11 [2017-05-17 20:34:14 $13644.0] WARNING swManager_check_exit_status: worker#1 abnormal exit, status=0, signal=11 事情是这样: 做了一个上传文件的接口,把文件上传之后接口就崩溃了,然后我使用kill pid杀掉了进程,之后再重启swoole服务,就再也无法接收请求了,一直报上面那个错误。 我想问的是,**遇到这种情况,我如何迅速的保证业务正常能访问**,第二就是怎么去解决这个问题,找到错误原因。
发布于8年前 · 5 次浏览 · 来自
提问
L
Lev
[2017-05-17 20:43:52 $13696.0] WARNING swManager_check_exit_status: worker#0 abnormal exit, status=0, signal=11 [2017-05-17 20:46:13 $13696.0] WARNING swManager_check_exit_status: worker#1 abnormal exit, status=0, signal=11 [2017-05-17 20:48:57 $13696.0] WARNING swManager_check_exit_status: worker#2 abnormal exit, status=0, signal=11 [2017-05-17 20:50:24 $13696.0] WARNING swManager_check_exit_status: worker#0 abnormal exit, status=0, signal=11 [2017-05-17 20:50:36 $13696.0] WARNING swManager_check_exit_status: worker#1 abnormal exit, status=0, signal=11 [2017-05-17 20:52:58 $13727.0] WARNING swManager_check_exit_status: worker#0 abnormal exit, status=0, signal=11 [2017-05-17 20:53:43 $13727.0] WARNING swManager_check_exit_status: worker#1 abnormal exit, status=0, signal=11 [2017-05-17 20:24:59 $13644.0] WARNING swManager_check_exit_status: worker#0 abnormal exit, status=0, signal=11 [2017-05-17 20:25:55 $13644.0] WARNING swManager_check_exit_status: worker#1 abnormal exit, status=0, signal=11 [2017-05-17 20:28:56 $13644.0] WARNING swManager_check_exit_status: worker#2 abnormal exit, status=0, signal=11 [2017-05-17 20:31:18 $13644.0] WARNING swManager_check_exit_status: worker#0 abnormal exit, status=0, signal=11 [2017-05-17 20:34:14 $13644.0] WARNING swManager_check_exit_status: worker#1 abnormal exit, status=0, signal=11 事情是这样: 做了一个上传文件的接口,把文件上传之后接口就崩溃了,然后我使用kill pid杀掉了进程,之后再重启swoole服务,就再也无法接收请求了,一直报上面那个错误。 我想问的是,**遇到这种情况,我如何迅速的保证业务正常能访问**,第二就是怎么去解决这个问题,找到错误原因。
赞
0
收藏
提问
分享
讨论
建议
公告
开发框架
CodeGalaxy
登录
后参与评论
评论
2018-09-15
め
め强迫症患者。
补充一下gdb打印出来的信息
赞
0
回复
2018-09-15
大
大海
有人解答下吗?至今服务无法启动。。。
赞
0
回复
2018-09-15
麦
麦子
重启了机器也不行
赞
0
回复