What in the world is causing these time outs?

Discussion in 'Bukkit Help' started by QuackzMcDuck, Apr 24, 2011.

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

    QuackzMcDuck

    Well since moving to a VPS I've been getting timeouts. I've tried everything to fix this, except remove plugins 1 by 1 to find the problem. I was wondering if anyone had some input as to what might be causing this. I have a thought that it's a memory leak problem but I have no clue what's causing it.

    2010 x86_64 GNU/Linux
    java version "1.6.0_24"
    Java(TM) SE Runtime Environment (build 1.6.0_24-b07)
    Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02, mixed mode)

    Command to start the server: rtoolkit.sh - From RemoteToolkit plugin.

    My server is a 2GB VPS, 1500MB allocated to it with optimized garbage collection, running off of the RemoteToolkit Wrapper.

    We also have mobs enabled and limited to spawn 250 at the max. Not running nether either.

    Plugins:
    [​IMG]

    We top around 1920 Mb/2068MB and then for some reason, we spike up and time out..This happens with no one on the server or 30 people. Player cap is not a factor.

    It's also not RemoteToolkit because we added that to help combat the time outs.
    It's not Craftbukkit build specific either.


    Any thoughts on a memory leak? Or any other possible problem?

    Thanks for reading and for help.
     
  2. Offline

    AgentKid

    Any way you could get a screenshot of what's happening on the server itself? (use top from command line)
     
  3. Offline

    Miauw62

    Yeah, that would be very usefull.
     
  4. Offline

    QuackzMcDuck

    I would, but since moving to CB714 all that happens is it disconnects everyone with no errors and gives them the read time out error.
     
  5. Offline

    AgentKid

    just SSH into the server when it happens and use the command "top".
     
  6. Offline

    QuackzMcDuck

    Java spikes to 120% CPU and then it sticks there and crashes..No errors no nothing...
     
Thread Status:
Not open for further replies.

Share This Page