Server Restart = Corrupted Players

Discussion in 'Bukkit Help' started by wow4201, Jan 16, 2012.

Thread Status:
Not open for further replies.
  1. Offline

    wow4201

    Problem:
    I restart the server every 4 hours automatically.
    It first kicks all the players, 15sec later then does save-all, 20sec later does /stop

    Sometimes (about 5%-10% of the time) It seems player data becomes corrupted.
    Players inventories can no longer be saved and console spams
    [WARNING] Failed to save player data for <playername> <----This is replaced with playername

    My theory is that everyone is frantically logging back in and while their doing this
    the server is stopping therefore some player data sometimes become corrupted.

    Anyone have a solution?

    I think what would work best is to prevent people logging back in after I kick them,
    Before running the save-all and stop command. Must be some kind of plugin to prevent
    users from logging in?

    Can anyone help please? I'm having to roll back player data every time this happens
     
  2. Offline

    pyraetos

    What plugin are you using to restart it automatically?
     
  3. Offline

    wow4201

    Its not a plugin to restart it automatically.
    Its ConsoleScheduler plugin to run commands at certain times
    It runs the commands in this order

    /kickall
    /save-all (15sec after ^)
    /stop (30sec after ^)
     
  4. Offline

    pyraetos

    And how does it restart the server?
    Also, why kickall. Stopping the server kicks em anyway.
     
    Ragnarrok1 likes this.
  5. Offline

    wow4201

    The server restarts it self when it restarts. Just by editing the .bat
    I do kickall before save-all so that it saves them correctly.

    Will doing a /stop save the player data automatically? I know that it kicks them obviously but does it save them
     
  6. Offline

    Ragnarrok1

    the server should save it self'? Think it saves it self...I have never got that problem :p
    But isent it bether to us a backup plugin?
     
Thread Status:
Not open for further replies.

Share This Page