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.

Bug Port already in use after auto restart from server crash.

Discussion in 'Bugs & Feature Requests' started by Squirzy, Jan 3, 2013.

  1. I have seemed to have the issue a fair few times over the past few days that when my server restarts itself automatically after crashing, I would get the message that the port is already in use:

    [INFO] Starting minecraft server version 1.4.6
    [INFO] Loading properties
    [INFO] Default game type: SURVIVAL
    [INFO] Generating keypair
    [INFO] Starting Minecraft server on *:25565
    [WARNING] **** FAILED TO BIND TO PORT!
    [WARNING] The exception was: java.net.BindException: Address already in use
    [WARNING] Perhaps a server is already running on that port?

    Thanks,
    Squirzy
     
  2. May I add, the console said the server had crashed and gave the exact same error above, but at the same time - I am still on the server moving around and players talking in chat???

    I am 110% this is the correct console as well.
     
  3. You may be running some dead screens? try clearing them with screen -wipe (or whatever the command is these days)
     
  4. Code (Text):
    killall screen
    As alternative.
     
  5. I have used that command and I am still getting the same issue
     
  6. Open Task Manager (Assuming it's windows home hosted) and look for any Java processes, If you find one, Kill it. This will stop any communication through that port.
     
  7. Its not windows, its debian.
     
  8. then run top or htop and do the same.
     
  9. I have killed all screens and didn't work. I restarted my two dedicated servers about an hour ago, I will see if that has fixed it
     
  10. I am having the same issue.
    Whenever the auto restart does its thing, the server gets the error bind of port
     
  11. If you're on linux, type this:
    Replace 25565 with the port.
     
    • Informative Informative x 1
  12. I know this thread is REALLY old, but I still had this problem.
    So for anyone finding this topic with the problem:
    Don't run your server with the normal command (Like java -Xmx blablabla)
    Create the start.sh file and when you start your seerver, use 'sh start.sh'.
    Server starts andstarts on crash or whatever