Massive Block Removal

Discussion in 'Bukkit Help' started by iBstoneyDave, Mar 17, 2011.

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

    iBstoneyDave

    So a large area covering over 100,000+ blocks the entire map has all its stone removed, thus ruining my server map. Not only this but around the same time my users kept getting kicked off for an I/O error (dissconnect.overflow) as can be seen in the logs below(and this is still happening despite an update to latest CB rec build. At the time this happened I was running CB #531

    I've tried to ascertain how it happened and the only thing that shows up in my logs is this:
    Code:
    011-03-17 01:14:0401:14:04 [INFO] §c[Mod] canadiancow§f§7:§f tya
    
    2011-03-17 01:14:04 [INFO] §c[Mod] canadiancow§f§7:§f tya
    2011-03-17 01:14:11 [INFO] §9[PLAYER_COMMAND] canadiancow: /list
    2011-03-17 01:14:1101:14:11 [INFO] §9[PLAYER_COMMAND] canadiancow: /list
    
    2011-03-17 01:15:0201:15:02 [INFO] /74.207.241.234:53142 lost connection
    
    2011-03-17 01:15:02 [INFO] /74.207.241.234:53142 lost connection
    2011-03-17 01:15:3301:15:33 [INFO] /173.234.147.81:38796 lost connection
    
    2011-03-17 01:15:33 [INFO] /173.234.147.81:38796 lost connection
    2011-03-17 01:17:16 [INFO] More than 1000000 updates, aborting lighting updates
    2011-03-17 01:17:1601:17:16 [INFO] More than 1000000 updates, aborting lighting updates
    
    2011-03-17 01:17:20 [INFO] More than 1000000 updates, aborting lighting updates
    2011-03-17 01:17:2001:17:20 [INFO] More than 1000000 updates, aborting lighting updates
    
    2011-03-17 01:17:24 [INFO] More than 1000000 updates, aborting lighting updates
    2011-03-17 01:17:2401:17:24 [INFO] More than 1000000 updates, aborting lighting updates
    
    2011-03-17 01:17:39 [INFO] More than 1000000 updates, aborting lighting updates
    2011-03-17 01:17:3901:17:39 [INFO] More than 1000000 updates, aborting lighting updates
    
    2011-03-17 01:17:41 [INFO] More than 1000000 updates, aborting lighting updates
    2011-03-17 01:17:4101:17:41 [INFO] More than 1000000 updates, aborting lighting updates
    
    2011-03-17 01:17:44 [INFO] More than 1000000 updates, aborting lighting updates
    2011-03-17 01:17:4401:17:44 [INFO] More than 1000000 updates, aborting lighting updates
    
    2011-03-17 01:18:01 [INFO] More than 1000000 updates, aborting lighting updates
    2011-03-17 01:18:0101:18:01 [INFO] More than 1000000 updates, aborting lighting updates
    
    2011-03-17 01:18:17 [INFO] More than 1000000 updates, aborting lighting updates
    2011-03-17 01:18:1701:18:17 [INFO] More than 1000000 updates, aborting lighting updates
    
    2011-03-17 01:18:57 [WARNING] Can't keep up! Did the system time change, or is the server overloaded?
    2011-03-17 01:18:5701:18:57 [WARNING] Can't keep up! Did the system time change, or is the server overloaded?
    
    2011-03-17 01:19:18 [INFO] More than 1000000 updates, aborting lighting updates
    2011-03-17 01:19:1801:19:18 [INFO] More than 1000000 updates, aborting lighting updates
    
    2011-03-17 01:19:19 [INFO] /63.135.6.249:65504 lost connection
    2011-03-17 01:19:19 [INFO] /63.135.6.249:65514 lost connection
    2011-03-17 01:19:1901:19:19 [INFO] /63.135.6.249:65504 lost connection
    
    2011-03-17 01:19:1901:19:19 [INFO] /63.135.6.249:65514 lost connection
    
    2011-03-17 01:19:57 [INFO] canadiancow lost connection: disconnect.overflow
    2011-03-17 01:19:5701:19:57 [INFO] canadiancow lost connection: disconnect.overflow
    
    2011-03-17 01:20:08 [INFO] Freed 1377.4469909667969 MB.
    2011-03-17 01:20:0801:20:08 [INFO] Freed 1377.4469909667969 MB.
    
    2011-03-17 01:20:14 [WARNING] Can't keep up! Did the system time change, or is the server overloaded?
    2011-03-17 01:20:1401:20:14 [WARNING] Can't keep up! Did the system time change, or is the server overloaded?
    Any help you could provide would be appreciated. If there is any method of recovering this lost stone i'd love it since I have no backups from before it that i can restore to. Thanks.
     
Thread Status:
Not open for further replies.

Share This Page