[Serious] MySQL write error #482


  • New
  • Defect
  • Replied
Open
Assigned to _ForgeUser8455416
  • _ForgeUser7748315 created this issue Jun 22, 2014

    Ive made many tickets before so if you need more information you should check there. I use this plugin to rank up players from the default rank, but now Im getting a ton of these in the console log:
    [06/22/2014 13:37:47] [ONTIME] {savePlayerDataMySQL} MYSQL Write Error:
    Instead of just dumping all my information, I think it would make more sense for you to tell me what information you need (i can tell you Im using the latest version of ontime and bukkit.

  • _ForgeUser7748315 added the tags New Defect Jun 22, 2014
  • _ForgeUser8455416 posted a comment Jun 22, 2014

    There should be more information following that error message, so please provide that or tell me there is nothing else displayed. Or better yet give me a sample of your console log that contains more than one of those error messages.

    If there is an OnTimeERROR.txt file in your plugins/OnTime directory, provide a link to a copy of that file.

    And I know you said you have the 'latest' versions, but please be explicit of the OnTime version and bukkit versions you are using so that there is no confusion.

  • _ForgeUser7748315 posted a comment Jun 23, 2014

    Startup: http://hastebin.com/xoxosoqoca.vhdl

    OnTimeERROR.txt: http://hastebin.com/awafurekiz.vbs

    OnTimeLog.txt: http://hastebin.com/okanusapoc.vbs

    You'll notice in the ontimelog that the plugin gives a referral reward to the same player over and over for one referral. This is the key issue. (see [06/20/2014 15:39:39] )

    If you need any more information, just ask. Thank you for your help.

  • _ForgeUser7748315 removed a tag Waiting Jun 23, 2014
  • _ForgeUser7748315 added a tag Replied Jun 23, 2014
  • _ForgeUser8455416 posted a comment Jun 24, 2014

    @gustebeast: Go

    Thanks. Please also share a link to your current OnTime/config.yml flie

  • _ForgeUser8455416 removed a tag Replied Jun 24, 2014
  • _ForgeUser8455416 added a tag Waiting Jun 24, 2014
  • _ForgeUser7748315 posted a comment Jun 25, 2014
  • _ForgeUser7748315 posted a comment Jun 29, 2014

    Is there any more information you need?

  • _ForgeUser8455416 posted a comment Jun 29, 2014

    @gustebeast: Go Sorry for not getting back to you. I have been looking at this and am not 100% what is going on, but there is one significant error, that could be the root of a lot of things.

    From both the console log and the ontimeLog, it looks like you are somehow missing a key entry from your MySQL database. There should be an entry with a "player name" of "ontime-data", this is key info that should have been auto created and maintained, but for some reason looks to be missing.

    I suggest that you remove your "ontime-players" table, and let OnTime start all over with a fresh DB. If there already is a lot of player data in your current DB, you can try to export the player data to a YML file, and the re-import the data after you remove the corrupt MySQL data table. See here for export and import of YML files:

    http://dev.bukkit.org/bukkit-plugins/ontime/pages/other-functions/

    At this point it is best option I can offer, so please give this a try and let me know the results.

  • _ForgeUser8455416 removed a tag Replied Jun 30, 2014
  • _ForgeUser8455416 added a tag Started Jun 30, 2014
  • _ForgeUser8455416 removed a tag Started Jun 30, 2014
  • _ForgeUser8455416 added a tag Waiting Jun 30, 2014
  • _ForgeUser7748315 posted a comment Jul 1, 2014

    I exported my data to a yml, and now I am using yml as my data store method. All the correct data is there. Now I am trying to switch back to mysql and the "/ontime export mysql" command isnt seeming to work. It print out messages as if it is successful, but when I check the table it remains unchanged. I used a truncate to get rid of the existing data in the table.

  • _ForgeUser7748315 removed a tag Waiting Jul 1, 2014
  • _ForgeUser7748315 added a tag Replied Jul 1, 2014
  • _ForgeUser8455416 posted a comment Jul 1, 2014

    @gustebeast: Go

    Are there any new messages in the OnTImeERROR.txt file?

    Instead of just truncating the old table, I suggest that you drop it completely, and then try again.

  • _ForgeUser7748315 posted a comment Jul 2, 2014

    By deleting the table, the transfer worked correctly. Now I just need to wait and see if any errors pop up.

    Im noticing some little anomolies with the data, for example it says some players joined the server 16253 days ago. Also when I check the top monthly time some players have played 6 days even though the month just started. My thought is that it is just a transfer issue and will iron itself out over time. Playtime seems to be accurate though and thats what matters.


    Edited Jul 2, 2014
  • _ForgeUser8455416 posted a comment Jul 4, 2014

    @gustebeast: Go

    ok. Glad to hear you got it working (mostly anyway).

    Having the "16253" days error means that the player's 'first login' got reset to zero, which is a result of the migration to and from YML. This should get fixed the next time the player logs in. Not sure about the 6 days at the start of the month, but this too could be the import/export issue.

    I'll leave this ticket open for a while in case you see more of this issue.


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