Zeitgeisttt 创建的主题

求问大佬们，我尝试用ANDROID_PAD和ANDROID_WATCH登录，滑块验证之后会遇到io.netty.channel.DefaultChannelPipeline的报错然后卡住，想问一下是咋回事。其它protocol都会报235和237的错。

请使用 SakuraLoginSolver 打开 http://<ip>:35975/request/request/22440335 来完成验证 2023-03-17 22:51:59 W/io.netty.channel.DefaultChannelPipeline: An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception. java.lang.IllegalArgumentException: Duplicate handler name: post-msg-receiver at mirai-login-solver-sakura-0.0.7.mirai2.jar[private]//io.netty.channel.DefaultChannelPipeline.checkDuplicateName(DefaultChannelPipeline.java:1055) at mirai-login-solver-sakura-0.0.7.mirai2.jar[private]//io.netty.channel.DefaultChannelPipeline.filterName(DefaultChannelPipeline.java:284) at mirai-login-solver-sakura-0.0.7.mirai2.jar[private]//io.netty.channel.DefaultChannelPipeline.addBefore(DefaultChannelPipeline.java:247) at mirai-login-solver-sakura-0.0.7.mirai2.jar[private]//io.netty.channel.DefaultChannelPipeline.addBefore(DefaultChannelPipeline.java:237) at mirai-login-solver-sakura-0.0.7.mirai2.jar//com.kasukusakura.mlss.slovbroadcast.SakuraTransmitDaemon.processHttpMsg(SakuraTransmitDaemon.kt:269) at mirai-login-solver-sakura-0.0.7.mirai2.jar//com.kasukusakura.mlss.slovbroadcast.SakuraTransmitDaemon.access$processHttpMsg(SakuraTransmitDaemon.kt:48) at mirai-login-solver-sakura-0.0.7.mirai2.jar//com.kasukusakura.mlss.slovbroadcast.SakuraTransmitDaemon$HttpConnectHandler.channelRead(SakuraTransmitDaemon.kt:721) at mirai-login-solver-sakura-0.0.7.mirai2.jar[private]//io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:444) at mirai-login-solver-sakura-0.0.7.mirai2.jar[private]//io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420) at mirai-login-solver-sakura-0.0.7.mirai2.jar[private]//io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:412) at mirai-login-solver-sakura-0.0.7.mirai2.jar//com.kasukusakura.mlss.slovbroadcast.SakuraTransmitDaemon$processHttpMsg$4$1.channelRead(SakuraTransmitDaemon.kt:297) at mirai-login-solver-sakura-0.0.7.mirai2.jar[private]//io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:444) at mirai-login-solver-sakura-0.0.7.mirai2.jar[private]//io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420) at mirai-login-solver-sakura-0.0.7.mirai2.jar[private]//io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:412) at mirai-login-solver-sakura-0.0.7.mirai2.jar[private]//io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:346) at mirai-login-solver-sakura-0.0.7.mirai2.jar[private]//io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:333) at mirai-login-solver-sakura-0.0.7.mirai2.jar[private]//io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:454) at mirai-login-solver-sakura-0.0.7.mirai2.jar[private]//io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:290) at mirai-login-solver-sakura-0.0.7.mirai2.jar[private]//io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:444) at mirai-login-solver-sakura-0.0.7.mirai2.jar[private]//io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420) at mirai-login-solver-sakura-0.0.7.mirai2.jar[private]//io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:412) at mirai-login-solver-sakura-0.0.7.mirai2.jar[private]//io.netty.handler.timeout.IdleStateHandler.channelRead(IdleStateHandler.java:286) at mirai-login-solver-sakura-0.0.7.mirai2.jar[private]//io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:442) at mirai-login-solver-sakura-0.0.7.mirai2.jar[private]//io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420) at mirai-login-solver-sakura-0.0.7.mirai2.jar[private]//io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:412) at mirai-login-solver-sakura-0.0.7.mirai2.jar[private]//io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1410) at mirai-login-solver-sakura-0.0.7.mirai2.jar[private]//io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:440) at mirai-login-solver-sakura-0.0.7.mirai2.jar[private]//io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420) at mirai-login-solver-sakura-0.0.7.mirai2.jar[private]//io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:919) at mirai-login-solver-sakura-0.0.7.mirai2.jar[private]//io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:166) at mirai-login-solver-sakura-0.0.7.mirai2.jar[private]//io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:788) at mirai-login-solver-sakura-0.0.7.mirai2.jar[private]//io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:724) at mirai-login-solver-sakura-0.0.7.mirai2.jar[private]//io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:650) at mirai-login-solver-sakura-0.0.7.mirai2.jar[private]//io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:562) at mirai-login-solver-sakura-0.0.7.mirai2.jar[private]//io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997) at mirai-login-solver-sakura-0.0.7.mirai2.jar[private]//io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) at java.base/java.lang.Thread.run(Unknown Source)

版本是这样的：

MCL 已推出 2.1.0，更好的支持 Mirai 2.11 的插件系统，建议更新。 22:45:04 [INFO] Verifying "net.mamoe:mirai-console" v2.14.0 22:45:08 [INFO] Verifying "net.mamoe:mirai-console-terminal" v2.14.0 22:45:09 [INFO] Verifying "net.mamoe:mirai-core-all" v2.14.0 22:45:10 [INFO] Verifying "org.itxtech:mcl-addon" v2.1.1 22:45:11 [INFO] Verifying "net.mamoe:mirai-api-http" v2.9.1 22:45:11 [INFO] Verifying "net.mamoe:chat-command" v0.5.1 22:45:11 [WARN] Package "net.mamoe:chat-command" requires "net.mamoe:mirai-console" version 2.0-RC. Current version is 2.14.0

以及fix-protocol-version会说Mirai版本低，这个有关系吗：

2023-03-17 22:45:16 W/fix-protocol-version: Mirai版本低于预期，将升级协议版本

在Debian系统的服务器上运行bot几个小时后会出现HeartbeatFailedException然后自动下线。已经出现两次了。

2023-03-05 14:57:16 V/Bot.[qq号]: [发送者] -> Test 2023-03-05 23:44:05 V/Bot.[qq号]: Event: BotOfflineEvent.Dropped(bot=Bot([qq号]), cause=HeartbeatFailedException: [qq号].AliveHeartbeat, recoverable=true, cause=PacketTimeoutException(message=[qq号].AliveHeartbeat Scheduler: Timeout receiving action response, cause=kotlinx.coroutines.TimeoutCancellationException: Timed out waiting for 5000 ms), reconnect=true) 2023-03-05 23:44:05 W/Bot.[qq号]: Connection lost, reconnecting... (HeartbeatFailedException: [qq号].AliveHeartbeat, recoverable=true, cause=PacketTimeoutException(message=[qq号].AliveHeartbeat Scheduler: Timeout receiving action response, cause=kotlinx.coroutines.TimeoutCancellationException: Timed out waiting for 5000 ms)) 2023-03-05 23:44:26 I/Bot.[qq号]: Bot cancelled: Bot closed

Mirai版本是这样的

14:55:30 [INFO] Verifying "net.mamoe:mirai-console" v2.14.0 14:55:35 [INFO] Verifying "net.mamoe:mirai-console-terminal" v2.14.0 14:55:37 [INFO] Verifying "net.mamoe:mirai-core-all" v2.14.0 14:55:38 [INFO] Verifying "org.itxtech:mcl-addon" v2.1.1 14:55:39 [INFO] Verifying "net.mamoe:mirai-api-http" v2.8.0 14:55:39 [WARN] Package "net.mamoe:mirai-api-http" has newer version "2.9.1" 14:55:39 [INFO] Verifying "net.mamoe:chat-command" v0.5.1 14:55:39 [WARN] Run ./mcl -u to update packages. 14:55:39 [WARN] Package "net.mamoe:chat-command" requires "net.mamoe:mirai-console" version 2.0-RC. Current version is 2.14.0

想问一下是什么问题导致的，怎么修复？谢谢！