Server quitting for no reason

Discussion in 'Bukkit Discussion' started by langkid1, Nov 21, 2011.

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

    langkid1

    Since I updated to build #1467(git-Bukkit-1.8.1-R4-10-gfb96d87-b1467jnks) the server has been printing '>Killed' and stopping without saving or disabling plugins. It seems that it prints '[WARNING] Can't keep up! Did the system time change, or is the server overloaded?' before it does this but I'm not sure that's the root of the problem.
    I am running Debian 6 with Java 1.6 on a Virtual Private Server. The log (not sure if it'll help) is at http://langserv.tk/s/Server/server.log Is anyone else having this problem?

    That may be, but only localhost can connect to the MySQL databases on my server :)
    EDIT: Oh sorry that ^^ up there was really off topic

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: Nov 26, 2016
  2. Offline

    shadrxninga

    Has this happened before on 1.8.1 builds? It is probably a bug in 1.0.0 version of Craftbukkit, bear in mind that Craftbukkit for 1.0.0 is not recommend and the only builds available are development builds.

    Please report any bugs you find here.

    Also, I suggest that your sever should not be inside your webfolder and available to the public, if you have any plugins that use MySQL databases the passwords to those database will be in the config files and anyone can view them.

    @langkid1
    I don't think my post was Offtopic
    I was asking you if this has ever happened before? It is probably because of the 1.0.0 Craftbukkit builds.

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: Dec 12, 2016
  3. Offline

    langkid1

    @shadrxninga
    sorry, you misunderstood. I meant MY post:
    not yours :)
     
  4. Offline

    shadrxninga

    Oh, ok :p

    So... still having problems? Or have you fixed it?
     
  5. Offline

    langkid1

    @shadrxninga well, I was asking around on the #debian channel on FreeNode and they said it's probably a RAM problem because I have the server set to -Xmx1G when there's about 512MB of RAM. So I added more SWAP, but that didn't do so great, so another user suggested I switch -Xmx1G to -Xmx400MB, and I did and now it works fine :D
     
  6. Offline

    shadrxninga

    Yes... that would explain it. Glad you fixed the problem.
     
  7. Offline

    langkid1

    Thanks for taking the time to help me!
     
Thread Status:
Not open for further replies.

Share This Page