mojira.dev
MC-81879

RCON is not listening on port.

Hi!

I noticed that sometimes, when I tried to connect to my Minecraft server via rcon, the connection failed. After getting the same problem a few times I began to test and tried to pinpoint what was different when it works and when it does not.
I wrote a simple script to start the server and stop it via a rcon connection. After some time and a seemingly random number of succeeding iterations of this script, the rcon connection fails. I then checked the Minecraft startup log (attached): everything normal.
Then I checked if the Minecraft server process was listening on the rcon port, but "lsof -i:25575" showed me no process listening on that port, although the server log says it is.
I can reproduce this with different ports on two different machines running OS X. The same script is running on my Ubuntu Server at the moment, so far I am at 1000 iterations and counting (1000 starts and stops via rcon) without any issues. So this seems to be OS X specific.

Since there is no error in the log, the Minecraft server does not seem to realise that the start of the rcon service failed.

latest.log

[17:32:45] [Server thread/INFO]: Starting minecraft server version 1.8.7
[17:32:45] [Server thread/INFO]: Loading properties
[17:32:45] [Server thread/INFO]: Default game type: SURVIVAL
[17:32:45] [Server thread/INFO]: Generating keypair
[17:32:45] [Server thread/INFO]: Starting Minecraft server on *:25565
[17:32:45] [Server thread/INFO]: Using default channel type
[17:32:46] [Server thread/INFO]: Preparing level "world"
[17:32:46] [Server thread/INFO]: Preparing start region for level 0
[17:32:47] [Server thread/INFO]: Preparing spawn area: 85%
[17:32:47] [Server thread/INFO]: Done (1,293s)! For help, type "help" or "?"
[17:32:47] [Server thread/INFO]: Starting remote control listener
[17:32:47] [RCON Listener #1/INFO]: RCON running on 0.0.0.0:25575

Comments 2

Is this still an issue in the current Minecraft Snapshot 15w49b or later? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.

I was having this exact same issue in 1.9.2, but on Arch Linux. This was fixed for me in 1.10.

Roman

(Unassigned)

Unconfirmed

Minecraft 1.8.7

Minecraft 1.10.2

Retrieved