Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

使用自动登陆有时会发生Connection timed out: no further information错误 #2809

Open
KJZH001 opened this issue Oct 9, 2023 · 0 comments

Comments

@KJZH001
Copy link

KJZH001 commented Oct 9, 2023

问题描述

和标题相同,启动mcl后有时会登录失败,但是重启mcl后大概率会成功登录

复现

配置完毕自动登陆和签名服务后,直接启动mcl.cmd
等待登录结果,如果成功则一切正常,如果失败则返回下方的日志

mirai-core 版本

Mirai console 2.16.0-RC

bot-protocol

ANDROID_PAD

其他组件版本

Running MiraiConsole v2.16.0-RC, built on 2023-09-03 23:55:17.
Frontend Terminal: version 2.16.0-RC, provided by Mamoe Technologies

Permission Service: Built In Permission Service

Plugins: Chat Command v0.5.0, net.mamoe.mirai-api-http v2.6.2, QRLogin v0.1.6, mirai-device-generator v1.1.3, mirai-login-solver-sakura v0.0.10, 空梦云-萌界核心 v0.1.7, QSign v1.0.7, MCL Addon v2.1.1

Object Pending Finalization Count: 0
committed | init | used | max
Heap Memory: 94.0MB | 252.0MB | 45.39MB | 3.9GB
Non-Heap Memory: 72.75MB | 7.31MB | 70.44MB | -1

系统日志

2023-10-09 22:11:57 E/main: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection timed out: no further information: msfwifi.3g.qq.com/36.155.*.*:8080
io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection timed out: no further information: msfwifi.3g.qq.com/36.155.*.*:8080
        Suppressed: NettyChannelException(message=Failed to connect msfwifi.3g.qq.com/<unresolved>:8080, cause=io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection timed out: no further information: msfwifi.3g.qq.com/36.155.*.*:8080)
                at net.mamoe.mirai.internal.network.impl.netty.NettyNetworkHandler.createConnection$suspendImpl(NettyNetworkHandler.kt:116)
                at net.mamoe.mirai.internal.network.impl.netty.NettyNetworkHandler$createConnection$1.invokeSuspend(NettyNetworkHandler.kt)
                at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
                at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:104)
                at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:570)
                at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:750)
                at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:677)
                at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:664)
        Caused by: [CIRCULAR REFERENCE: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection timed out: no further information: msfwifi.3g.qq.com/36.155.*.*:8080]
Caused by: java.net.ConnectException: Connection timed out: no further information
        at java.base/sun.nio.ch.Net.pollConnect(Native Method)
        at java.base/sun.nio.ch.Net.pollConnectNow(Net.java:672)
        at java.base/sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:946)
        at io.netty.channel.socket.nio.NioSocketChannel.doFinishConnect(NioSocketChannel.java:337)
        at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:334)
        at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:776)
        at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:724)
        at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:650)
        at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:562)
        at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997)
        at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
        at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
        at java.base/java.lang.Thread.run(Thread.java:833)

2023-10-09 22:11:57 V/Bot.447509623: Event: AutoLoginEvent.Failure(bot=447509623, protocol=ANDROID_PAD, cause=io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection timed out: no further information: msfwifi.3g.qq.com/36.155.*.*:8080)
2023-10-09 22:11:57 I/main: mirai-console started successfully.
2023-10-09 22:11:57 I/Bot.447509623: Bot cancelled: Bot closed

网络日志

�[93m2023-10-09 22:11:57 W/Net 447509623: Exception in resumeConnection.
NettyChannelException(message=Failed to connect msfwifi.3g.qq.com/<unresolved>:8080, cause=io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection timed out: no further information: msfwifi.3g.qq.com/36.155.*.*:8080)
	at net.mamoe.mirai.internal.network.impl.netty.NettyNetworkHandler.createConnection$suspendImpl(NettyNetworkHandler.kt:116)
	at net.mamoe.mirai.internal.network.impl.netty.NettyNetworkHandler$createConnection$1.invokeSuspend(NettyNetworkHandler.kt)
	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
	at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:104)
	at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:570)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:750)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:677)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:664)
Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection timed out: no further information: msfwifi.3g.qq.com/36.155.*.*:8080
Caused by: java.net.ConnectException: Connection timed out: no further information
	at java.base/sun.nio.ch.Net.pollConnect(Native Method)
	at java.base/sun.nio.ch.Net.pollConnectNow(Net.java:672)
	at java.base/sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:946)
	at io.netty.channel.socket.nio.NioSocketChannel.doFinishConnect(NioSocketChannel.java:337)
	at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:334)
	at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:776)
	at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:724)
	at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:650)
	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:562)
	at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997)
	at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
	at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
	at java.base/java.lang.Thread.run(Thread.java:833)
�[0m
�[93m2023-10-09 22:11:57 W/Net 447509623: Network selector received exception, closing bot. (NettyChannelException(message=Failed to connect msfwifi.3g.qq.com/<unresolved>:8080, cause=io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection timed out: no further information: msfwifi.3g.qq.com/36.155.*.*:8080))�[0m

补充信息

出于潜在的风险考虑,上方日志中的ip信息我手工替换最后的末端为了*.*

C:\Users\>ping 36.155.*.*

正在 Ping 36.155.*.* 具有 32 字节的数据:
来自 36.155.*.* 的回复: 字节=32 时间=20ms TTL=53
来自 36.155.*.* 的回复: 字节=32 时间=20ms TTL=53
来自 36.155.*.* 的回复: 字节=32 时间=24ms TTL=53
来自 36.155.*.* 的回复: 字节=32 时间=25ms TTL=53

36.155.*.* 的 Ping 统计信息:
    数据包: 已发送 = 4,已接收 = 4,丢失 = 0 (0% 丢失),
往返行程的估计时间(以毫秒为单位):
    最短 = 20ms,最长 = 25ms,平均 = 22ms

并且这个ip去ping是能够ping通的,所以我感觉应该不是请求在链路上被阻断的问题

另外近期bot掉线比较严重,不知道是不是也有一定关联

2023-10-08 21:11:58 V/Bot.447*****: Event: BotOfflineEvent.Dropped(bot=Bot(447*****), cause=HeartbeatFailedException: 447*****.AliveHeartbeat, recoverable=true, cause=PacketTimeoutException(message=447*****.AliveHeartbeat Scheduler: Timeout receiving action response, cause=kotlinx.coroutines.TimeoutCancellationException: Timed out waiting for 5000 ms), reconnect=true)
2023-10-08 21:11:58 W/Bot.447*****: Connection lost, reconnecting... (HeartbeatFailedException: 447*****.AliveHeartbeat, recoverable=true, cause=PacketTimeoutException(message=447*****.AliveHeartbeat Scheduler: Timeout receiving action response, cause=kotlinx.coroutines.TimeoutCancellationException: Timed out waiting for 5000 ms))
2023-10-08 21:11:58 I/QSignService: register 447*****
2023-10-08 21:11:59 I/QSignService: energy 810_a
2023-10-08 21:11:59 I/Bot.447*****: Saved account secrets to local cache for fast login.
2023-10-08 21:11:59 I/Bot.447*****: Login successful.
2023-10-08 21:11:59 V/Bot.447*****: Event: BotOnlineEvent(bot=Bot(447*****))
2023-10-08 21:11:59 V/Bot.447*****: Event: BotReloginEvent(bot=Bot(447*****), cause=null)
2023-10-08 21:11:59 I/Bot.447*****: Reconnected successfully in 1.827s.
2023-10-08 21:11:59 I/com.github.unidbg.linux.AndroidSyscallHandler: Return default pipe pair.
2023-10-08 21:11:59 I/com.github.unidbg.linux.ARM64SyscallHandler: fork

网络服务提供商:浙江移动

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant