Çözüldü MYSql Sunucu Çökmesi

  • Konuyu Başlatan Konuyu Başlatan lordkena
  • Başlangıç tarihi Başlangıç tarihi
  • Görüntüleme 506
Durum
Üzgünüz bu konu cevaplar için kapatılmıştır...

lordkena

Birisi mi Spawnlandı?
Katılım
29 Ocak 2024
Mesajlar
9
Elmaslar
0
Puan
355
Yaş
23
Konum
istanbull
Minecraft
NoxAves

Discord:

d.kena

Sunucum 7 8 saatte bir şu şekilde çöküyor :

[20:22:40] [Craft Scheduler Thread - 6849/INFO]: TwiLight » Yerdeki eşyalar 30 saniye içerisinde temizlenecek!
[20:22:42] [Server thread/INFO]: 0956m issued server command: /warp boss
[20:22:49] [User Authenticator #108/WARN]: [User Authenticator #108] WARN fr.xephi.authme.libs.com.zaxxer.hikari.pool.PoolBase - AuthMeMYSQLPool - Failed to validate connection com.mysql.cj.jdbc.ConnectionImpl@505a9f30 (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
[20:22:49] [User Authenticator #108/WARN]: [User Authenticator #108] WARN fr.xephi.authme.libs.com.zaxxer.hikari.pool.PoolBase - AuthMeMYSQLPool - Failed to validate connection com.mysql.cj.jdbc.ConnectionImpl@6140eae6 (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
[20:24:19] [User Authenticator #108/WARN]: [User Authenticator #108] WARN fr.xephi.authme.libs.com.zaxxer.hikari.pool.PoolBase - AuthMeMYSQLPool - Failed to validate connection com.mysql.cj.jdbc.ConnectionImpl@3452dada (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
[20:24:19] [User Authenticator #119/WARN]: [AuthMe] Error during SQL operation: [SQLTransientConnectionException]: AuthMeMYSQLPool - Connection is not available, request timed out after 30002ms.
[20:24:19] [User Authenticator #118/WARN]: [AuthMe] Error during SQL operation: [SQLTransientConnectionException]: AuthMeMYSQLPool - Connection is not available, request timed out after 30000ms.
[20:24:19] [Netty Server IO #1/INFO]: [SpigotGuard] [1] Player 0956m tried to crash the server, packet: PacketPlayInPositionLook, details: packet limit exceed, how to fix if false positive: can't be fixed)
[20:24:19] [Netty Server IO #3/INFO]: [SpigotGuard] [1] Player Anzeo tried to crash the server, packet: PacketPlayInPositionLook, details: packet limit exceed, how to fix if false positive: can't be fixed)
[20:24:19] [Paper Watchdog Thread/ERROR]: --- DO NOT REPORT THIS TO PAPER - THIS IS NOT A BUG OR A CRASH - git-Paper-794 (MC: 1.16.5) ---
[20:24:19] [pool-27-thread-1/INFO]: [Vulcan] 0956m position was updated for being on a ghost block! (arena, 18, 18, 330) [96]
[20:24:19] [Server thread/INFO]: mahmur issued server command: /claim ev
[20:24:19] [Paper Watchdog Thread/ERROR]: The server has not responded for 10 seconds! Creating thread dump
[20:24:19] [Paper Watchdog Thread/ERROR]: ------------------------------
[20:24:19] [Paper Watchdog Thread/ERROR]: Server thread dump (Look for plugins here before reporting to Paper!):
[20:24:19] [User Authenticator #115/WARN]: [User Authenticator #115] WARN fr.xephi.authme.libs.com.zaxxer.hikari.pool.PoolBase - AuthMeMYSQLPool - Failed to validate connection com.mysql.cj.jdbc.ConnectionImpl@1b89144a (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
[20:24:19] [User Authenticator #117/WARN]: [User Authenticator #117] WARN fr.xephi.authme.libs.com.zaxxer.hikari.pool.PoolBase - AuthMeMYSQLPool - Failed to validate connection com.mysql.cj.jdbc.ConnectionImpl@69c1fbeb (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
[20:24:19] [User Authenticator #116/WARN]: [User Authenticator #116] WARN fr.xephi.authme.libs.com.zaxxer.hikari.pool.PoolBase - AuthMeMYSQLPool - Failed to validate connection com.mysql.cj.jdbc.ConnectionImpl@3a1ba4c5 (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
[20:24:19] [User Authenticator #114/WARN]: [User Authenticator #114] WARN fr.xephi.authme.libs.com.zaxxer.hikari.pool.PoolBase - AuthMeMYSQLPool - Failed to validate connection com.mysql.cj.jdbc.ConnectionImpl@3cf69cf4 (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
[20:24:19] [User Authenticator #113/WARN]: [User Authenticator #113] WARN fr.xephi.authme.libs.com.zaxxer.hikari.pool.PoolBase - AuthMeMYSQLPool - Failed to validate connection com.mysql.cj.jdbc.ConnectionImpl@69d59d90 (No operations allowed after connection closed.). Possibly consider using a shorter maxLifetime value.
[20:24:19] [Paper Watchdog Thread/ERROR]: ------------------------------
[20:24:19] [Paper Watchdog Thread/ERROR]: Current Thread: Server thread
[20:24:19] [Paper Watchdog Thread/ERROR]: PID: 24 | Suspended: false | Native: false | State: BLOCKED
[20:24:19] [User Authenticator #113/WARN]: [AuthMe] Error during SQL operation: [SQLTransientConnectionException]: AuthMeMYSQLPool - Connection is not available, request timed out after 51622ms.
[20:24:19] [Paper Watchdog Thread/ERROR]: Stack:
[20:24:19] [Paper Watchdog Thread/ERROR]: app//org.apache.logging.log4j.core.async.AsyncLoggerDisruptor.enqueueLogMessageWhenQueueFull(AsyncLoggerDisruptor.java:236)
[20:24:19] [Paper Watchdog Thread/ERROR]: app//org.apache.logging.log4j.core.async.AsyncLogger.handleRingBufferFull(AsyncLogger.java:246)
[20:24:19] [Paper Watchdog Thread/ERROR]: app//org.apache.logging.log4j.core.async.AsyncLogger.publish(AsyncLogger.java:230)
[20:24:19] [Paper Watchdog Thread/ERROR]: app//org.apache.logging.log4j.core.async.AsyncLogger.logWithThreadLocalTranslator(AsyncLogger.java:225)
[20:24:19] [Paper Watchdog Thread/ERROR]: app//org.apache.logging.log4j.core.async.AsyncLogger.access$000(AsyncLogger.java:67)
[20:24:19] [Paper Watchdog Thread/ERROR]: app//org.apache.logging.log4j.core.async.AsyncLogger$1.log(AsyncLogger.java:152)
[20:24:19] [Paper Watchdog Thread/ERROR]: app//org.apache.logging.log4j.core.async.AsyncLogger.log(AsyncLogger.java:136)
[20:24:19] [Paper Watchdog Thread/ERROR]: app//org.apache.logging.log4j.spi.AbstractLogger.tryLogMessage(AbstractLogger.java:2205)
[20:24:19] [Paper Watchdog Thread/ERROR]: app//org.apache.logging.log4j.spi.AbstractLogger.logMessageTrackRecursion(AbstractLogger.java:2159)
[20:24:19] [Paper Watchdog Thread/ERROR]: app//org.apache.logging.log4j.spi.AbstractLogger.logMessageSafely(AbstractLogger.java:2142)
[20:24:19] [Paper Watchdog Thread/ERROR]: app//org.apache.logging.log4j.spi.AbstractLogger.logMessage(AbstractLogger.java:2040)
[20:24:19] [Paper Watchdog Thread/ERROR]: app//org.apache.logging.log4j.spi.AbstractLogger.logIfEnabled(AbstractLogger.java:1907)
[20:24:19] [Paper Watchdog Thread/ERROR]: app//org.apache.logging.log4j.spi.AbstractLogger.warn(AbstractLogger.java:2789)
[20:24:19] [Paper Watchdog Thread/ERROR]: app//net.minecraft.server.v1_16_R3.MinecraftServer.w(MinecraftServer.java:1105)
[20:24:19] [Paper Watchdog Thread/ERROR]: app//net.minecraft.server.v1_16_R3.MinecraftServer.lambda$a$0(MinecraftServer.java:291)
[20:24:19] [Paper Watchdog Thread/ERROR]: app//net.minecraft.server.v1_16_R3.MinecraftServer$$Lambda$3158/0x00000008012dfa98.run(Unknown Source)
[20:24:19] [Paper Watchdog Thread/ERROR]: [email protected]/java.lang.Thread.run(Thread.java:831)
[20:24:19] [Paper Watchdog Thread/ERROR]: ------------------------------
[20:24:19] [Paper Watchdog Thread/ERROR]: --- DO NOT REPORT THIS TO PAPER - THIS IS NOT A BUG OR A CRASH ---

Bu saldırı sonucu mu oluyor, napmalıyım authme port falan mı değiştireyim?
 
Son düzenleme:
Merhaba sunucunuza crash saldırısı yapılıyor crash yüzünden mysql veritabanına erişimde problem oluyor sunucunuzun kapanmasının sebebi mysql değil crash.

LPX Adlı eklentiyi satın alıp kurduğunuzda sorununuz çözülecektir.
 
Makinanızın donanım özelliklerini iletirmisiniz?
 
Merhaba sunucunuza crash saldırısı yapılıyor crash yüzünden mysql veritabanına erişimde problem oluyor sunucunuzun kapanmasının sebebi mysql değil crash.

LPX Adlı eklentiyi satın alıp kurduğunuzda sorununuz çözülecektir.
Spigot Guard vardı ama o iş yapmıyo sanırsam, dediğinizi de deneyeceğim
 
en güzel koruamyı söylüyorum sana xCord kur bungeecord forku olarak exploit-monitor'u aktif et
 
Durum
Üzgünüz bu konu cevaplar için kapatılmıştır...

Hala Discord sunucumuza katılmadın mı?

Büyük bir topluluğun parçası ol, etkinliklere katıl ve özel hediyeler kazanma şansı yakala!

Şimdi Katıl
Üst