Closed JYInMyHeart closed 3 years ago
已修复,请参考 66dd75e 修改docker-compose.yml
及milkice.qq/config.yaml
😀
好嘞 very appreciated.
已修复,请参考 66dd75e 修改
docker-compose.yml
及milkice.qq/config.yaml
😀
修改docker-compose.yml
和milkice.qq/config.yaml
后,efb
重新启动出现了如下错误
2021-05-30 05:30:43,943 [Level 99]: ehforwarderbot.__main__ (__main__.init; __main__.py:129)
Initializing slave milkice.qq...
Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/efb_qq_slave/ClientMgr.py", line 32, in __init__
self.client = cls(name, config, channel)
File "/usr/local/lib/python3.8/site-packages/efb_qq_plugin_mirai/mirai.py", line 65, in __init__
self.loop.run_until_complete(self.bot.handshake())
File "/usr/local/lib/python3.8/asyncio/base_events.py", line 616, in run_until_complete
return future.result()
File "/usr/local/lib/python3.8/site-packages/mirai_core/bot.py", line 58, in handshake
await self.auth()
File "/usr/local/lib/python3.8/site-packages/mirai_core/bot.py", line 65, in auth
result = await self.session.post('/auth', data={'authKey': self.auth_key})
File "/usr/local/lib/python3.8/site-packages/mirai_core/network.py", line 101, in post
return await HttpClient._check_response(response, url, 'post')
File "/usr/local/lib/python3.8/site-packages/mirai_core/network.py", line 44, in _check_response
raise ServerException(f'{url} {method} failed, status code: {result.status}')
mirai_core.exceptions.ServerException: /auth post failed, status code: 404
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/bin/ehforwarderbot", line 8, in <module>
sys.exit(main())
File "/usr/local/lib/python3.8/site-packages/ehforwarderbot/__main__.py", line 339, in main
init(conf)
File "/usr/local/lib/python3.8/site-packages/ehforwarderbot/__main__.py", line 135, in init
coordinator.add_channel(cls(instance_id=instance_id))
File "/usr/local/lib/python3.8/site-packages/efb_qq_slave/__init__.py", line 44, in __init__
self.init_client_manager()
File "/usr/local/lib/python3.8/site-packages/efb_qq_slave/__init__.py", line 73, in init_client_manager
self.QQClientMgr = ClientMgr(self.config['Client'], self.config, self)
File "/usr/local/lib/python3.8/site-packages/efb_qq_slave/ClientMgr.py", line 35, in __init__
raise Exception("Specified client not found!")
Exception: Specified client not found!
网络问题已经修复😊
出现Exception: Specified client not found!
的原因就是efb无法连接到mirai
docker logs mirai
检查一下mirai状态是否登录成功?
好嘞 谢谢大佬
已修复,请参考 66dd75e 修改
docker-compose.yml
及milkice.qq/config.yaml
😀修改
docker-compose.yml
和milkice.qq/config.yaml
后,efb
重新启动出现了如下错误2021-05-30 05:30:43,943 [Level 99]: ehforwarderbot.__main__ (__main__.init; __main__.py:129) Initializing slave milkice.qq... Traceback (most recent call last): File "/usr/local/lib/python3.8/site-packages/efb_qq_slave/ClientMgr.py", line 32, in __init__ self.client = cls(name, config, channel) File "/usr/local/lib/python3.8/site-packages/efb_qq_plugin_mirai/mirai.py", line 65, in __init__ self.loop.run_until_complete(self.bot.handshake()) File "/usr/local/lib/python3.8/asyncio/base_events.py", line 616, in run_until_complete return future.result() File "/usr/local/lib/python3.8/site-packages/mirai_core/bot.py", line 58, in handshake await self.auth() File "/usr/local/lib/python3.8/site-packages/mirai_core/bot.py", line 65, in auth result = await self.session.post('/auth', data={'authKey': self.auth_key}) File "/usr/local/lib/python3.8/site-packages/mirai_core/network.py", line 101, in post return await HttpClient._check_response(response, url, 'post') File "/usr/local/lib/python3.8/site-packages/mirai_core/network.py", line 44, in _check_response raise ServerException(f'{url} {method} failed, status code: {result.status}') mirai_core.exceptions.ServerException: /auth post failed, status code: 404 During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/bin/ehforwarderbot", line 8, in <module> sys.exit(main()) File "/usr/local/lib/python3.8/site-packages/ehforwarderbot/__main__.py", line 339, in main init(conf) File "/usr/local/lib/python3.8/site-packages/ehforwarderbot/__main__.py", line 135, in init coordinator.add_channel(cls(instance_id=instance_id)) File "/usr/local/lib/python3.8/site-packages/efb_qq_slave/__init__.py", line 44, in __init__ self.init_client_manager() File "/usr/local/lib/python3.8/site-packages/efb_qq_slave/__init__.py", line 73, in init_client_manager self.QQClientMgr = ClientMgr(self.config['Client'], self.config, self) File "/usr/local/lib/python3.8/site-packages/efb_qq_slave/ClientMgr.py", line 35, in __init__ raise Exception("Specified client not found!") Exception: Specified client not found!
网络问题已经修复😊
同样问题,请问解决与否?
出现
Exception: Specified client not found!
的原因就是efb无法连接到miraidocker logs mirai
检查一下mirai状态是否登录成功?
请问如何解决,我这里mirai已经登录成功,console可以显示消息。问题复现,和楼上报错日志一样
出现
Exception: Specified client not found!
的原因就是efb无法连接到miraidocker logs mirai
检查一下mirai状态是否登录成功?请问如何解决,我这里mirai已经登录成功,console可以显示消息。问题复现,和楼上报错日志一样
试一下network_mode-host
分支?
修改docker-compose.yml
及/efb/profiles/default/milkice.qq/config.yaml
两个文件,参考 2c8bcba
出现
Exception: Specified client not found!
的原因就是efb无法连接到miraidocker logs mirai
检查一下mirai状态是否登录成功?请问如何解决,我这里mirai已经登录成功,console可以显示消息。问题复现,和楼上报错日志一样
试一下
network_mode-host
分支?修改
docker-compose.yml
及/efb/profiles/default/milkice.qq/config.yaml
两个文件,参考 2c8bcba
问题依旧 :(
出现
Exception: Specified client not found!
的原因就是efb无法连接到miraidocker logs mirai
检查一下mirai状态是否登录成功?请问如何解决,我这里mirai已经登录成功,console可以显示消息。问题复现,和楼上报错日志一样
试一下
network_mode-host
分支? 修改docker-compose.yml
及/efb/profiles/default/milkice.qq/config.yaml
两个文件,参考 2c8bcba问题依旧 :(
方便发一下docker-compose logs
的完整log吗,我这边启动过程中也会出现几次Exception: Specified client not found!
,efb重启大概5-6次之后等mirai也启动完成才正常
出现
Exception: Specified client not found!
的原因就是efb无法连接到miraidocker logs mirai
检查一下mirai状态是否登录成功?请问如何解决,我这里mirai已经登录成功,console可以显示消息。问题复现,和楼上报错日志一样
试一下
network_mode-host
分支? 修改docker-compose.yml
及/efb/profiles/default/milkice.qq/config.yaml
两个文件,参考 2c8bcba问题依旧 :(
方便发一下
docker-compose logs
的完整log吗,我这边启动过程中也会出现几次Exception: Specified client not found!
,efb重启大概5-6次之后等mirai也启动完成才正常
请稍等,正在使用compose重启
出现
Exception: Specified client not found!
的原因就是efb无法连接到miraidocker logs mirai
检查一下mirai状态是否登录成功?请问如何解决,我这里mirai已经登录成功,console可以显示消息。问题复现,和楼上报错日志一样
试一下
network_mode-host
分支? 修改docker-compose.yml
及/efb/profiles/default/milkice.qq/config.yaml
两个文件,参考 2c8bcba问题依旧 :(
方便发一下
docker-compose logs
的完整log吗,我这边启动过程中也会出现几次Exception: Specified client not found!
,efb重启大概5-6次之后等mirai也启动完成才正常
mirai | 16:24:23 [INFO] iTXTech Mirai Console Loader version 1.1.0-beta.1-982f9f4
mirai | 16:24:23 [INFO] https://github.com/iTXTech/mirai-console-loader
mirai | 16:24:23 [INFO] This program is licensed under GNU AGPL v3
mirai | 16:24:23 [DEBUG] Loading script: announcement.js
mirai | 16:24:24 [DEBUG] Loading script: boot.js
mirai | 16:24:24 [DEBUG] Loading script: config.js
mirai | 16:24:24 [DEBUG] Loading script: oraclejdk.js
mirai | 16:24:24 [DEBUG] Loading script: repo.js
mirai | 16:24:24 [DEBUG] Loading script: updater.js
mirai | 16:24:25 [INFO] Fetching Mirai Console Loader Announcement...
mirai | 16:24:28 [INFO] Mirai Console Loader Announcement:
mirai | Mirai Console Loader 公告栏
mirai |
mirai | [mirai-console] 最近, 项目组发现了权限系统可能会被错误的提前加载导致的3rd权限系统无法正确加载
mirai |
mirai | 于是决定, 于 2.6 起, 超前访问权限系统将得到一个错误并中断插件加载, 请各开发者及时检查
mirai |
mirai | 影响范围: https://github.com/mamoe/mirai-console/pull/307
mirai |
mirai |
mirai | 16:24:28 [INFO] Verifying "net.mamoe:mirai-console" version 2.6.4
mirai | 16:24:29 [INFO] Verifying "net.mamoe:mirai-console-terminal" version 2.6.4
mirai | 16:24:29 [INFO] Verifying "net.mamoe:mirai-core-all" version 2.6.4
mirai | 2021-06-09 16:24:34 I/main: Starting mirai-console...
mirai | 2021-06-09 16:24:35 I/main: Backend: version 2.6.4, built on 2021-05-05 23:44:19.
mirai | 2021-06-09 16:24:35 I/main: Frontend Terminal: version 2.6.4, provided by Mamoe Technologies
mirai | 2021-06-09 16:24:35 I/main: Welcome to visit https://mirai.mamoe.net/
mirai | 2021-06-09 16:24:35 I/plugin: Successfully loaded plugin net.mamoe.mirai-api-http
mirai | 2021-06-09 16:24:37 I/main: Prepared built-in commands: autoLogin, help, login, permission, status, stop
mirai | 2021-06-09 16:24:37 W/net.mamoe.mirai-api-http: USING INITIAL KEY, please edit the key
mirai | 2021-06-09 16:24:37 I/Mirai HTTP API: ****
efb | File "/usr/local/lib/python3.8/site-packages/aiohttp/connector.py", line 535, in connect
efb | proto = await self._create_connection(req, traces, timeout)
efb | File "/usr/local/lib/python3.8/site-packages/aiohttp/connector.py", line 892, in _createconnection
efb | , proto = await self._create_direct_connection(req, traces, timeout)
efb | File "/usr/local/lib/python3.8/site-packages/aiohttp/connector.py", line 1051, in _create_direct_connection
efb | raise last_exc
efb | File "/usr/local/lib/python3.8/site-packages/aiohttp/connector.py", line 1020, in _create_direct_connection
efb | transp, proto = await self._wrap_create_connection(
efb | File "/usr/local/lib/python3.8/site-packages/aiohttp/connector.py", line 975, in _wrap_create_connection
efb | raise client_error(req.connection_key, exc) from exc
efb | aiohttp.client_exceptions.ClientConnectorError: Cannot connect to host 127.0.0.1:8080 ssl:default [Connect call failed ('127.0.0.1', 8080)]
efb |
efb | During handling of the above exception, another exception occurred:
efb |
efb | Traceback (most recent call last):
efb | File "/usr/local/lib/python3.8/site-packages/efb_qq_slave/ClientMgr.py", line 32, in init
efb | self.client = cls(name, config, channel)
efb | File "/usr/local/lib/python3.8/site-packages/efb_qq_plugin_mirai/mirai.py", line 65, in init
efb | self.loop.run_until_complete(self.bot.handshake())
efb | File "/usr/local/lib/python3.8/asyncio/base_events.py", line 616, in run_until_complete
efb | return future.result()
efb | File "/usr/local/lib/python3.8/site-packages/mirai_core/bot.py", line 58, in handshake
efb | await self.auth()
efb | File "/usr/local/lib/python3.8/site-packages/mirai_core/bot.py", line 65, in auth
efb | result = await self.session.post('/auth', data={'authKey': self.auth_key})
efb | File "/usr/local/lib/python3.8/site-packages/mirai_core/network.py", line 100, in post
efb | raise NetworkException('Unable to reach Mirai console')
efb | mirai_core.exceptions.NetworkException: Unable to reach Mirai console
efb |
efb | During handling of the above exception, another exception occurred:
efb |
efb | Traceback (most recent call last):
efb | File "/usr/local/bin/ehforwarderbot", line 8, in
@TodayNoLunch @JYInMyHeart 问题找到了😥
b6ca6a 引进了mirai-api-http-v2.0,此版本变更了很多接口,但efb-qq-plugin-mirai 尚未迁移至新接口
解决方案是暂时回退至旧版本的mirai-api-http,重新拉取新镜像即可
docker image rm xzsk2/mirai-docker
docker-compose up -d
如果配置无误应该就能正常启动了🤔
@TodayNoLunch @JYInMyHeart 问题找到了😥
b6ca6a 引进了mirai-api-http-v2.0,此版本变更了很多接口,但efb-qq-plugin-mirai 尚未迁移至新接口
解决方案是暂时回退至旧版本的mirai-api-http,重新拉取新镜像即可
- 删除有问题的mirai镜像
docker image rm xzsk2/mirai-docker
- 拉取新镜像并重新启动
docker-compose up -d
如果配置无误应该就能正常启动了🤔
nice! 辛苦啦!😄
@TodayNoLunch @JYInMyHeart 问题找到了😥
b6ca6a 引进了mirai-api-http-v2.0,此版本变更了很多接口,但efb-qq-plugin-mirai 尚未迁移至新接口
解决方案是暂时回退至旧版本的mirai-api-http,重新拉取新镜像即可
1. 删除有问题的mirai镜像 `docker image rm xzsk2/mirai-docker` 2. 拉取新镜像并重新启动 `docker-compose up -d`
如果配置无误应该就能正常启动了🤔
辛苦!十分感谢XD
按照教程修改完配置之后,使用
docker-compose
启动, 第一个报错无法连接到127.0.0.1:8080
查看端口,mirai
未在8080
启动 在docker-compose.yml
指定8080
端口映射之后mirai在本机8080
端口启动成功 但是docker-compose
启动之后仍然提示无法连接到8080
端口, 尝试指定ip
地址为localhost
或者mirai
均未成功, 之后指定为eth0
网卡对应ip
,貌似可以连接到8080
端口 然后出现第二个报错 第二个报错提示/auth post failed http status 404
TG-EFB-QQ-Docker版本:
环境信息: