1. Guest, as per the stickied thread, this forum has not been in use since 2014. All bugs and feature requests should be posted to JIRA.

Crash on #934 spigot

Discussion in 'Bugs & Feature Requests' started by zRA1Nz, Jun 23, 2013.

  1. Error
    23.06 22:13:35 [Server] SEVERE Current Thread: Thread-19
    23.06 22:13:35 [Server] SEVERE ------------------------------
    23.06 22:13:35 [Server] SEVERE java.lang.Thread.run(Thread.java:722)
    23.06 22:13:35 [Server] SEVERE java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
    23.06 22:13:35 [Server] SEVERE java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130)
    23.06 22:13:35 [Server] SEVERE java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1068)
    23.06 22:13:35 [Server] SEVERE java.util.concurrent.SynchronousQueue.poll(SynchronousQueue.java:942)
    23.06 22:13:35 [Server] SEVERE java.util.concurrent.SynchronousQueue$TransferStack.transfer(SynchronousQueue.java:359)
    23.06 22:13:35 [Server] SEVERE java.util.concurrent.SynchronousQueue$TransferStack.awaitFulfill(SynchronousQueue.java:460)
    23.06 22:13:35 [Server] SEVERE java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:226)
    23.06 22:13:35 [Server] SEVERE sun.misc.Unsafe.park(Native Method)
    23.06 22:13:35 [Server] SEVERE Stack:
    23.06 22:13:35 [Server] SEVERE PID: 54 | Suspended: false | Native: false | State: TIMED_WAITING
    23.06 22:13:35 [Server] SEVERE Current Thread: process reaper
    23.06 22:13:35 [Server] SEVERE ------------------------------
    23.06 22:13:34 [Server] SEVERE Current Thread State:
    23.06 22:13:34 [Server] SEVERE Spigot version: git-Spigot-934 (MC: 1.5.2)
    23.06 22:13:34 [Server] SEVERE Be sure to include ALL relevant console errors and Minecraft crash reports
    23.06 22:13:34 [Server] SEVERE Please report this to http://www.spigotmc.org/
    23.06 22:13:34 [Server] SEVERE The server has stopped responding!

    The crash file wasn't created so this the best I can post...
     
  2. joehot200

    Supporter

    Unfortunatley we cant really help without the whole trace, and it is unlikley that the error will just be in that little bit (Nor does it look like it is)
     
  3. externo6

    Supporter

    It will be in the server log, not a crash report.
     
  4. externo6

    Supporter

    Is there anything above that?
     
  5. externo6

    Supporter

    Nothing in that pastebin will help us debug the issue. There is just not enough information.
     
  6. joehot200

    Supporter

    "23.06 22:36:43 [Multicraft] Skipped 352 lines due to rate limit (30/s)"

    If you want to catch errors in the console, Dont use MultiCraft.
    In fact, if you are running a server that large, just dont use MultiCraft for regular daily use and as a standard SSH client at all.
     
    #8 joehot200, Jun 23, 2013
    Last edited: Jun 23, 2013
    • Disagree Disagree x 2
    • Agree Agree x 1
  7. Why whats bad about multicraft?
     
    • Like Like x 1
  8. joehot200

    Supporter

    For example, the line rate limting, and a few other things. Its all right and a good control panel, but relying on multicraft alone is not a good tactic, and though there are other things apart from the rate limiting, think about there - You could have had the whole stack trace, but no, Multicraft limited the rate of the lines coming through, so now we cant help you, etc.
    I would recommend MultiCraft as being a panel that you can give to your administrators or moderators for them to be able to easily shutdown, restart the server, etc (if you want to give server staff such perms), and not as an actual client that you use all the time daily.


    Anyway, im getting off topic, so sorry about that xD
     
    • Agree Agree x 2