Paper Spigot 1.12.2 crashing

Discussion in 'Paper Help' started by Hoster, Feb 12, 2018.

  1. Hoster

    Hoster New Member


    I got a lot of crashes since Paper versions > 1310
    I happens frequently when a user login, so I thought it was Authme, but I updated it.

    I can attach my paper log, but it's very long...

    See how it starts:

    [09:02:24 ERROR]: The server has stopped responding!
    [09:02:24 ERROR]: Please report this to
    [09:02:24 ERROR]: Be sure to include ALL relevant console errors and Minecraft crash reports
    [09:02:24 ERROR]: Paper version: git-Paper-1322 (MC: 1.12.2)
    [09:02:24 ERROR]: ------------------------------
    [09:02:24 ERROR]: Server thread dump (Look for plugins here before reporting to Paper!):
    [09:02:24 ERROR]: ------------------------------
    [09:02:24 ERROR]: Current Thread: Server thread
    [09:02:24 ERROR]: PID: 18 | Suspended: false | Native: true | State: RUNNABLE
    [09:02:24 ERROR]: Stack:
    [09:02:24 ERROR]: org.sqlite.core.NativeDB.step(Native Method)
    [09:02:24 ERROR]: org.sqlite.core.DB.execute(
    [09:02:24 ERROR]: org.sqlite.core.DB.executeUpdate(
    [09:02:24 ERROR]: org.sqlite.jdbc3.JDBC3PreparedStatement.executeUpdate(
    [09:02:24 ERROR]: fr.xephi.authme.datasource.SQLite.updateQuitLoc(
    [09:02:24 ERROR]: fr.xephi.authme.process.quit.AsynchronousQuit.processQuit(
    [09:02:24 ERROR]: fr.xephi.authme.process.Management.lambda$performQuit$7(
    [09:02:24 ERROR]: fr.xephi.authme.process.Management$$Lambda$310/ Source)
    [09:02:24 ERROR]: fr.xephi.authme.service.BukkitService.runTaskOptionallyAsync(
    [09:02:24 ERROR]: fr.xephi.authme.process.Management.runTask(
    [09:02:24 ERROR]: fr.xephi.authme.process.Management.performQuit(
    [09:02:24 ERROR]: fr.xephi.authme.listener.PlayerListener.onPlayerQuit(
    [09:02:24 ERROR]: com.destroystokyo.paper.event.executor.asm.generated.GeneratedEventExecutor729.execute(Unknown Source)
    [09:02:24 ERROR]: org.bukkit.plugin.EventExecutor$2.execute(
    [09:02:24 ERROR]: co.aikar.timings.TimedEventExecutor.execute(
    [09:02:24 ERROR]: org.bukkit.plugin.RegisteredListener.callEvent(
    [09:02:24 ERROR]: org.bukkit.plugin.SimplePluginManager.fireEvent(
    [09:02:24 ERROR]: org.bukkit.plugin.SimplePluginManager.callEvent(
    [09:02:24 ERROR]: net.minecraft.server.v1_12_R1.PlayerList.disconnect(
    [09:02:24 ERROR]: net.minecraft.server.v1_12_R1.PlayerConnection.a(
    [09:02:24 ERROR]: net.minecraft.server.v1_12_R1.NetworkManager.handleDisconnection(
    [09:02:24 ERROR]: net.minecraft.server.v1_12_R1.ServerConnection.c(
    [09:02:24 ERROR]: net.minecraft.server.v1_12_R1.MinecraftServer.D(
    [09:02:24 ERROR]: net.minecraft.server.v1_12_R1.DedicatedServer.D(
    [09:02:24 ERROR]: net.minecraft.server.v1_12_R1.MinecraftServer.C(
    [09:02:24 ERROR]:
    [09:02:24 ERROR]:
  2. electronicboy

    electronicboy New Member

    Authme is doing sql transactions on the main thread, which is what caused your server to crash according to that report.
  3. Hoster

    Hoster New Member

    Yes but I had no issues before few days ago... I also updated Authme.... And it's working on SQLite
  4. electronicboy

    electronicboy New Member

    And magically databases grow, and performing updates and any other operation also grows in time required. maybe even a slow disk; but your issue here seemingly boils down to authme being stupid and doing transactions on the main thread.
  5. ShelLuser

    ShelLuser New Member

    At the risk of stating something obvious but the best way to rule out any influence from a plugin is to take it out of the equation and then test again. In other words: instead of merely updating set up a test environment, move the plugin out of the way and see if the same thing happens.

    This is in some cases a very tedious task, but the best way to rule out any other possible cause for a crash.
  6. Brayjamin

    Brayjamin New Member

    Yea I would suggest AuthMeReloaded, which is a newer version of AuthMe that is updated still. I have had no issues with it so far!

    Also consider updating to a newer version of paper, like 1400 which is the next release.

Share This Page