MiraiForum

    • 注册
    • 登录
    • 搜索
    • 热门
    • 最新
    • 未解决
    • 标签
    • 群组
    • 友情链接
    1. 主页
    2. FuYon
    3. 主题
    • 资料
    • 关注 2
    • 粉丝 0
    • 主题 2
    • 帖子 67
    • 最佳 4
    • 有争议的 0
    • 群组 2

    FuYon 创建的主题

    • FuYon

      已解决 【求助贴】Mirai点歌插件下配置ffmpeg_path导致端口被占用的问题
      使用交流 • • FuYon

      13
      0
      赞同
      13
      帖子
      1102
      浏览

      FuYon

      我发现错误出现的时间点是在我安装完Mirai点歌插件 后,并且在系统变量中配置好ffmpeg_path(用于在qq中发送amr语音) 之后,将ffmpeg.exe拖到mcl的根目录里。——————此时运行mcl会有如上的占用error;

      尝试删掉位于根目录下的ffmpeg.exe,再次运行mcl,仍然出现同样的error。

      再次删除:将系统变量path中删除M:\mirai\ffmpeg\bin,此时再次运行mcl,点歌插件提示:

      ecf5d29b-8176-4e0e-bf86-40be7e623950-image.png
      并且没有以上的占用报错出现。问题完美解决(误)

      于是乎,解决办法是不去使用此点歌插件的语音功能。

      但是不知道是否有兼容的解决办法。

      第一个错误
      E/net.mamoe.mirai-api-http: kotlinx.coroutines.JobCancellationException: LazyStandaloneCoroutine is cancelling; job=LazyStandaloneCoroutine{Cancelling}@476fde05
      kotlinx.coroutines.JobCancellationException: LazyStandaloneCoroutine is cancelling; job=LazyStandaloneCoroutine{Cancelling}@476fde05
      Caused by: java.net.BindException: Address already in use: bind
      at java.base/sun.nio.ch.Net.bind0(Native Method)
      at java.base/sun.nio.ch.Net.bind(Net.java:552)
      at
      java.base/sun.nio.ch.ServerSocketChannelImpl.netBind(ServerSocketChannelImpl.java:336)
      at java.base/sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:294)
      at java.base/sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:88)
      at io.ktor.network.sockets.ConnectUtilsJvmKt.bind(ConnectUtilsJvm.kt:32)
      at io.ktor.network.sockets.TcpSocketBuilder.bind(TcpSocketBuilder.kt:46)
      at io.ktor.network.sockets.TcpSocketBuilder.bind(TcpSocketBuilder.kt:30)
      at io.ktor.network.sockets.TcpSocketBuilder.bind$default(TcpSocketBuilder.kt:29)
      at io.ktor.server.cio.backend.HttpServerKt$httpServer$acceptJob$1.invokeSuspend(HttpServer.kt:46)
      at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
      at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
      at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:571)
      at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:750)
      at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:678)
      at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:665)
      **

      第二个错误
      E/MahKtorAdapter[http,ws]: java.net.BindException: Address already in use: bind
      java.net.BindException: Address already in use: bind
      at java.base/sun.nio.ch.Net.bind0(Native Method)
      at java.base/sun.nio.ch.Net.bind(Net.java:552)
      at java.base/sun.nio.ch.ServerSocketChannelImpl.netBind(ServerSocketChannelImpl.java:336)
      at java.base/sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:294)
      at java.base/sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:88)
      at io.ktor.network.sockets.ConnectUtilsJvmKt.bind(ConnectUtilsJvm.kt:32)
      at io.ktor.network.sockets.TcpSocketBuilder.bind(TcpSocketBuilder.kt:46)
      at io.ktor.network.sockets.TcpSocketBuilder.bind(TcpSocketBuilder.kt:30)
      at io.ktor.network.sockets.TcpSocketBuilder.bind$default(TcpSocketBuilder.kt:29)
      at io.ktor.server.cio.backend.HttpServerKt$httpServer$acceptJob$1.invokeSuspend(HttpServer.kt:46)
      at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
      at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
      at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:571)
      at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:750)
      at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:678)
      at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:665)

    • FuYon

      已解决 【求助帖】如何解决MCL登录后classpath中丢失log4j-core的问题~
      使用交流 • • FuYon

      7
      0
      赞同
      7
      帖子
      1393
      浏览

      FuYon

      200.png
      在mcl登陆账号成功后立即报错:

      W/stderr: SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
      W/stderr: SLF4J: Defaulting to no-operation (NOP) logger implementation
      W/stderr: SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
      W/stderr: ERROR StatusLogger Log4j2 could not find a logging implementation. Please add log4j-core to the classpath. Using SimpleLogger to log to the console...]

      官网给出的解决办法(大概):This warning message is reported when the class could not be loaded into memory. This happens when no appropriate SLF4J binding ould be found on the class path. Placing one (and only one) of slf4j-nop.jar slf4j-simple.jar, slf4j-log4j12.jar, slf4j-jdk14.jar or logback-classic.jar on the class path should solve the problem.

      意思是你把这几个jar其中之一添加到classpath应该就没问题了。(或者说根据上面的错误提示之还要进行一些操作?)

      但是百度了许多“如何将jar添加到classpath”的方法,发现貌似没有一个可以让我成功规避这个错误(也可能是我不会操作哈哈)。

      在这里求助一下解决方案,thanks for help >w<

    • 1 / 1