Server crash after /ontime (only once) #516

  • New
  • Defect
Assigned to _ForgeUser8455416
  • _ForgeUser16573995 created this issue Sep 20, 2014

    NOTE: If you supply copies of your .yml or console log files, please use pastebin, dropbox, or other service and provide link,  instead of copy/paste of the file into this report. Thanks!

    What Version of OnTime and Bukkit are you using?
    OnTime: v.3.13.4
    Bukkit: Spigot Build #1649 (with Spigot Patcher)

    What storage option are you using? (YML or MYSQL) ?
    What permissions plugin are you using? (Groupmanager, PEX,bPermissions, etc.)
    Please provide a link to a copy of your plugins/OnTime/config.yml:
    What steps will reproduce the problem?
    1. Player executed command /ontime
    2. Server stopped responding

    However, the error hasn't appeared again...

    What is the expected output? What do you see instead?
    It shouldn't crash :)

    Do you have an console log of what happened?

    Are you having a "rewards" problem?  Please provide a link to a copy of your /plugins/OnTime/rewards.yml :

    Did you turn on OnTime logging (/ontime logfile enable 1)?  If so, provide a link to that file too.
    I unfortunately didn't turn it on :/

    Please provide any additional information below.

    [09/20/2014 11:19:05] {lineout [current] rollover map for cool__man not found.
    Could this have caused the error? It was around the same time...

    Thank you for looking at this ticket :)

  • _ForgeUser16573995 added the tags New Defect Sep 20, 2014
  • _ForgeUser8455416 posted a comment Oct 7, 2014

    Hi, first I don't think it is related to the rollover map issue, but thanks for bringing that to my attention anyway.

    It looks like your SQL server was somehow locked up, and each time OnTime tried to access the DB it got hung in a 'waiting' state, and eventually enough process threads ended up in that state that your sever eventually failed.

    If the issue is not repeating itself, it will be very hard to impossible to figure out what happened this one time.

    I will play around a little bit with my test system to see if I can create a similar situation, because I would have thought that the OnTime calls to the sever would just have returned a 'fail' code and moved on, and not been hung.

    If you ever see this again, please let me know. If I find anything in my experiments I'll add a message to this ticket.

    But my expectation is that I am not going to find anything useful and will eventually close this ticket, just because it is so hard to figure out a one time only failure that is not clearly the fault of OnTime.

    BR, Edge

To post a comment, please login or register a new account.