So I'm having trouble starting my minecraft server within screen. I try running it and I get the following output below. And I even stop the server, try running it, and it happens again.
bash-3.2# java -Xms768M -Xmx768M -jar minecraft_server.jar nogui
2011-04-25 21:58:05 [INFO] Starting minecraft server version Beta 1.4
2011-04-25 21:58:05 [INFO] Loading properties
2011-04-25 21:58:05 [INFO] Starting Minecraft server on *:25565
2011-04-25 21:58:05 [WARNING] **** FAILED TO BIND TO PORT!
2011-04-25 21:58:05 [WARNING] The exception was: java.net.BindException: Address already in use
2011-04-25 21:58:05 [WARNING] Perhaps a server is already running on that port?
stop
java.lang.NullPointerException
at kv.a(SourceFile:254)
at kv.a(SourceFile:33)
at net.minecraft.server.MinecraftServer.b(SourceFile:356)
at net.minecraft.server.MinecraftServer.run(SourceFile:277)
at bg.run(SourceFile:375)
2011-04-25 21:58:08 [SEVERE] Unexpected exception
java.lang.NullPointerException
at kv.a(SourceFile:254)
at kv.a(SourceFile:33)
at net.minecraft.server.MinecraftServer.b(SourceFile:356)
at net.minecraft.server.MinecraftServer.run(SourceFile:277)
at bg.run(SourceFile:375)
2011-04-25 21:58:10 [INFO] Unknown console command. Type "help" for help.
stop
2011-04-25 21:58:11 [INFO] Stopping server
bash-3.2# java -Xms768M -Xmx768M -jar minecraft_server.jar nogui
2011-04-25 21:58:18 [INFO] Starting minecraft server version Beta 1.4
2011-04-25 21:58:18 [INFO] Loading properties
2011-04-25 21:58:18 [INFO] Starting Minecraft server on *:25565
2011-04-25 21:58:18 [WARNING] **** FAILED TO BIND TO PORT!
2011-04-25 21:58:18 [WARNING] The exception was: java.net.BindException: Address already in use
2011-04-25 21:58:18 [WARNING] Perhaps a server is already running on that port?
Clearly, because I've been waiting for the moment for you to log on to post this so I can waste your precious forum lurking time.
Google does an excellent job of searching these forums, It would help you in the long run to do some research as I'm positive you will find a **** ton of posts with the same.
The two common causes of that error:
1) You have two instances of the server running... restart you 'puter and that should go away.
2) You have filled out server-ip in server.properties. Leave that blank, unless you know what you are doing (looks like you don't) that will ALWAYS be blank.
he is running it without the ip in the config. 1st update the mincraft server.jar or .exe, 2nd make sure there is no *.lck file in the folder it is running in.
he is running it without the ip in the config. 1st update the mincraft server.jar or .exe, 2nd make sure there is no *.lck file in the folder it is running in.
Damn... that's what I get for not looking at the logs he posted.. :\
First, just try restarting your system to see if that helps any. Also, it looks like you're trying to run under 1.4 Beta. Since Notch updated the game, you have to get the new Minecraft Server software off of the site.Try updating your server and retrying it.
I'm posting this here in case anyone else finds this looking for a solution to the posted problem, since literally no one read the logs (if they had, they'd know what really is going on).
THIS:
011-04-25 21:58:05 [INFO] Starting Minecraft server on *:25565
2011-04-25 21:58:05 [WARNING] **** FAILED TO BIND TO PORT!
2011-04-25 21:58:05 [WARNING] The exception was: java.net.BindException: Address already in use
2011-04-25 21:58:05 [WARNING] Perhaps a server is already running on that port?
Does NOT say "Perhaps another minecraft server is already running on that port?". It actually says, Perhaps A server is already running on that port. In other words, something else on your computer is listening on the port 25565. It literally DOES NOT MATTER what else it is. In windows, you can use the Resource monitor to find out what program is running on that port, and if its not a necessary system program, you can even terminate the process from the same window. Since this error is still worded this way, this information still applies, and it applies to ANY OTHER software that has a server that tells you that its unable to bind a port because its already in use. Changing the IP address also wouldn't change anything, as most servers are written to bind to any interface with the specified port.
Clearly, because I've been waiting for the moment for you to log on to post this so I can waste your precious forum lurking time.
Google does an excellent job of searching these forums, It would help you in the long run to do some research as I'm positive you will find a **** ton of posts with the same.
The two common causes of that error:
1) You have two instances of the server running... restart you 'puter and that should go away.
2) You have filled out server-ip in server.properties. Leave that blank, unless you know what you are doing (looks like you don't) that will ALWAYS be blank.
Lulz
Damn... that's what I get for not looking at the logs he posted.. :\
Lulz
and see if your running a server on another screen session (which you probably are)
and
to connect to one, or just do
My public free build survival server: http://westcraft.ddns.net
I'm posting this here in case anyone else finds this looking for a solution to the posted problem, since literally no one read the logs (if they had, they'd know what really is going on).
THIS:
011-04-25 21:58:05 [INFO] Starting Minecraft server on *:25565
2011-04-25 21:58:05 [WARNING] **** FAILED TO BIND TO PORT!
2011-04-25 21:58:05 [WARNING] The exception was: java.net.BindException: Address already in use
2011-04-25 21:58:05 [WARNING] Perhaps a server is already running on that port?
Does NOT say "Perhaps another minecraft server is already running on that port?". It actually says, Perhaps A server is already running on that port. In other words, something else on your computer is listening on the port 25565. It literally DOES NOT MATTER what else it is. In windows, you can use the Resource monitor to find out what program is running on that port, and if its not a necessary system program, you can even terminate the process from the same window. Since this error is still worded this way, this information still applies, and it applies to ANY OTHER software that has a server that tells you that its unable to bind a port because its already in use. Changing the IP address also wouldn't change anything, as most servers are written to bind to any interface with the specified port.