MiraiForum

    • Register
    • Login
    • Search
    • Popular
    • Recent
    • Unsolved
    • Tags
    • Groups
    • 友情链接

    通过mcl启动mirai时报错

    BUG反馈
    1
    1
    118
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • VantHoff
      VantHoff last edited by

      问题描述

      启动mirai时报错

      复现

      1.使用stop命令停止
      2.使用./mcl启动
      3.报错产生

      mirai-core 版本

      2.12.1

      bot-protocol

      ANDROID_PHONE

      其他组件版本

      2022-08-30 17:53:06 I/plugin: Successfully loaded plugin ApexLookUp v1.6.0                                                                                                                  
      2022-08-30 17:53:06 I/plugin: Successfully loaded plugin net.mamoe.mirai-api-http v2.5.2                                                                                                    
      2022-08-30 17:53:06 I/plugin: Successfully loaded plugin OneBot v0.3.4                                                                                                                      
      2022-08-30 17:53:06 I/plugin: Successfully loaded plugin Chat Command v0.5.0                                                                                                                
      2022-08-30 17:53:06 I/plugin: Successfully loaded plugin MCL Addon v2.0.2  
      

      系统日志

      2022-08-30 17:53:09 E/main: NettyChannelException(message=null, cause=null)                                                                                                                 
      NettyChannelException(message=null, cause=null)                                                                                                                                             
              at net.mamoe.mirai.internal.network.impl.netty.NettyNetworkHandler.createConnection$lambda-3(NettyNetworkHandler.kt:177)
              at io.netty.util.concurrent.DefaultPromise.notifyListener0(DefaultPromise.java:578)
              at io.netty.util.concurrent.DefaultPromise.notifyListenersNow(DefaultPromise.java:552) 
              at io.netty.util.concurrent.DefaultPromise.notifyListeners(DefaultPromise.java:491)
              at io.netty.util.concurrent.DefaultPromise.setValue0(DefaultPromise.java:616)
              at io.netty.util.concurrent.DefaultPromise.setSuccess0(DefaultPromise.java:605)
              at io.netty.util.concurrent.DefaultPromise.trySuccess(DefaultPromise.java:104)
              at io.netty.channel.DefaultChannelPromise.trySuccess(DefaultChannelPromise.java:84)
              at io.netty.channel.AbstractChannel$CloseFuture.setClosed(AbstractChannel.java:1186)
              at io.netty.channel.AbstractChannel$AbstractUnsafe.doClose0(AbstractChannel.java:773)
              at io.netty.channel.AbstractChannel$AbstractUnsafe.close(AbstractChannel.java:749)
              at io.netty.channel.AbstractChannel$AbstractUnsafe.close(AbstractChannel.java:620)
              at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.closeOnRead(AbstractNioByteChannel.java:105)
              at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:174)
              at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:719)
              at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:655)
              at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:581)
              at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:493)
              at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
              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)
              Suppressed: java.util.concurrent.CancellationException: NetworkHandler closed
                      at kotlinx.coroutines.ExceptionsKt.CancellationException(Exceptions.kt:22)
                      at kotlinx.coroutines.JobKt__JobKt.cancel(Job.kt:596)
                      at kotlinx.coroutines.JobKt.cancel(Unknown Source)
                      at net.mamoe.mirai.internal.network.handler.NetworkHandlerSupport.close(NetworkHandlerSupport.kt:61)
                      at net.mamoe.mirai.internal.network.impl.netty.NettyNetworkHandler.close(NettyNetworkHandler.kt:205)
                      ... 22 more
              Caused by: [CIRCULAR REFERENCE: NettyChannelException(message=null, cause=null)]
              Suppressed: StateSwitchingException(old=StateLoading, new=StateClosed, cause=NettyChannelException(message=null, cause=null))
                      at net.mamoe.mirai.internal.network.handler.NetworkHandlerSupport.setStateImpl$mirai_core(NetworkHandlerSupport.kt:302)
                      at net.mamoe.mirai.internal.network.impl.netty.NettyNetworkHandler.close(NettyNetworkHandler.kt:422)
                      ... 22 more
              Caused by: [CIRCULAR REFERENCE: NettyChannelException(message=null, cause=null)]
              Suppressed: [CIRCULAR REFERENCE: java.util.concurrent.CancellationException: NetworkHandler closed]
      
      2022-08-30 17:53:09 I/Bot.1026152696: Bot cancelled: Bot closed
      

      网络日志

      网络日志.log

      补充信息

      该问题在断线一分钟后仍未重连 #1361,中出现过。

      1 Reply Last reply Reply Quote 0
      • 1 / 1
      • First post
        Last post
      Powered by Mamoe Technologies & NodeBB | 友情链接 | 服务监控 | Contact