Server Crash

Discussion in 'Bukkit Help' started by lawina, Jan 19, 2011.

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

    lawina

    Hello guys, just ocurred a crash on my server where everyone was booted out, but I could still login to the server/console and issue commands. After I logged into console and issued the "list" command it still showed everyone online, while they were booted out.

    This is what I found in the logs when it happened:

    Any ideas what could have caused this (ArrayIndexOutOfBoundsException -1)?

    Looking forward to any replies.

    Thank you

    lawina
     
  2. Offline

    TnT

    Haven't seen that yet. What plugins are you running? What build #? What have you tried already?
     
  3. Offline

    lawina

    Thank you for your reply. The problem is, I have no idea which build I am running and as far as I was told there is no way to find out either. I use the following plugins: General, BackupArea, Guardian, MyHome, Whiteliste.

    It looks like the server is running again now, I'll see if it happens again. Hopefully it was a one-time error :)
     
  4. Offline

    Kirb

    I ran into the (ArrayIndexOutOfBoundsException -1) error a few times on my server.

    In my experience, it usually occurred when a person was trying to enter a corrupted chunk. I had to clear their file from the players folder in the world folder to get them out and to stop crashing the server.
     
  5. Offline

    Kane

    This error is common. Bukkit dev team does not want to touch it and it's not their bug it's for sure Minecraft's but no one will fix it they even know about it.

    There was a wonderful fix in 1.1 that no one brought back in 1.2 and tons of info on the error from 1.1 to 1.2 and Bukkit 1.2

    If you don't mind bumping this thread and linking it here also:
    http://forums.bukkit.org/threads/critical-smp-bug-plague-some-servers-none-bukkit-bug.949/

    Also the Get Satisfaction Bug Report:
    http://getsatisfaction.com/mojang/t...la_java_lang_arrayindexoutofboundsexception_1
     
Thread Status:
Not open for further replies.

Share This Page