Michael Malloy
- TheShadowEevee
- JIRAUSER643907
- America/Chicago
- Yes
- No
BDS-13252Summary
When starting the server, if a port the server tries to use (IE. 19132) is already taken by another program it silently fails. This effects the current version as well as previous versions of the server software.Steps to reproduce...
- Run a server using the Dedicated Server or an unofficial server software using the default 19132 port
- While the other server is running, start the dedicated server
- Issue happens as it tries to open the port
What actually happened...
The server outputs:[INFO] IPv4 supported, port: 19132 [INFO] IPv6 supported, port: 19133And then stop running without any more cues as to what the issue may be.
What should happen...
Notes...
On Java the global cap scales with the number of loaded chunks. This means the more players online, the higher the cap.
While mob farms (eg chicken cookers) with tens/hundreds of mobs could be considered overkill they are also part of the sandbox. With no indication you've gone over this invisible cap many don't understand why nothing is spawning for them.
On larger servers there's very little admins can do to prevent hitting the cap. Just general play by everyone online, without massive farms, will fill the cap.
When starting the server, if a port the server tries to use (IE. 19132) is already taken by another program it silently fails. This effects the current version as well as previous versions of the server software.
Normally it would output:
[INFO] IPv4 supported, port: 19132 [INFO] IPv6 supported, port: 19133But will instead output:
[INFO] IPv4 supported, port: 0 [INFO] IPv6 supported, port: 0And then stop running without any more cues as to what the issue may be.
This is an issue on the Windows version, I haven't tested the Unix version yet.
Summary
When starting the server, if a port the server tries to use (IE. 19132) is already taken by another program it silently fails. This effects the current version as well as previous versions of the server software.Steps to reproduce...
- Run a server using the Dedicated Server or an unofficial server software using the default 19132 port
- While the other server is running, start the dedicated server
- Issue happens as it tries to open the port
What
actuallyhappened...
The server outputs:[INFO] IPv4 supported, port: 19132 [INFO] IPv6 supported, port: 19133And then stop running without any more cues as to what the issue may be.
What should happen...
Notes...On Java the global cap scales with the number ofloaded chunks. This means the more players online, the higher the cap.
While mob farms (eg chicken cookers) with tens/hundreds of mobs could be considered overkill they are also part of the sandbox. With no indication you've gone over this invisible cap many don't understand why nothing is spawning for them.
On larger servers there's very little admins can do to prevent hitting the cap. Just general play by everyone online, without massive farms, will fill the cap.
When starting the server, if a port the server tries to use (IE. 19132) is already taken by another program it silently fails. This effects the current version as well as previous versions of the server software.
Normally it would output:
[INFO] IPv4 supported, port:19132[INFO] IPv6 supported, port:19133But will instead output:
[INFO] IPv4 supported, port: 0 [INFO] IPv6 supported, port: 0And then stop running without any more cues as to what the issue may be.
This is an issue on the Windows version, I haven't tested the Unix version yet.
Summary
When starting the server, if a port the server tries to use (IE. 19132) is already taken by another program it silently fails. This effects the current version as well as previous versions of the server software.Steps to reproduce...
- Run a server using the Dedicated Server or an unofficial server software using the default 19132 port
- While the other server is running, start the dedicated server
- Issue happens as it tries to open the port
What I expected to happen...
Normally the server outputs the following:[INFO] IPv4 supported, port: 19132 [INFO] IPv6 supported, port: 19133Since this wouldn't be true though, a message of some sort should appear.
A potential message could be "The port [port number] cannot be used. Please make sure no other software is currently using the port."What actually happened...
The server outputs:[INFO] IPv4 supported, port: 0 [INFO] IPv6 supported, port: 0And then stops running without any more cues as to what the issue may be.
Notes...
- I have experienced this issue on Windows, and am currently unsure if Linux is affected.
Summary
When starting the server, if a port the server tries to use (IE. 19132) is already taken by another program it silently fails. This effects the current version as well as previous versions of the server software.Steps to reproduce...
- Run a server using the Dedicated Server or an unofficial server software using the default 19132 port
- While the other server is running, start the dedicated server
- Issue happens as it tries to open the port
What I expected to happen...
Normally the server outputs the following:[INFO] IPv4 supported, port: 19132 [INFO] IPv6 supported, port: 19133Since this wouldn't be true though, a message of some sort should appear.
A potential message could be "The port [port number] cannot be used. Please make sure no other software is currently using the port."What actually happened...
The server outputs:[INFO] IPv4 supported, port: 0 [INFO] IPv6 supported, port: 0And then stops running without any more cues as to what the issue may be.
Notes...
I have experienced this issue on Windows, and am currently unsure if Linux is affected.Summary
When starting the server, if a port the server tries to use (IE. 19132) is already taken by another program it silently fails. This effects the current version as well as previous versions of the server software.Steps to reproduce...
- Run a server using the Dedicated Server or an unofficial server software using the default 19132 port
- While the other server is running, start the dedicated server
- Issue happens as it tries to open the port
What I expected to happen...
Normally the server outputs the following:[INFO] IPv4 supported, port: 19132 [INFO] IPv6 supported, port: 19133Since this wouldn't be true though, a message of some sort should appear.
A potential message could be "The port [port number] cannot be used. Please make sure no other software is currently using the port."What actually happened...
The server outputs:[INFO] IPv4 supported, port: 0 [INFO] IPv6 supported, port: 0And then stops running without any more cues as to what the issue may be.
Notes...
- The server could potentially ask for a new port, or ask if the user wants to use the default port if the current port is not the default 19132 port.
- I have experienced this issue on Windows, and am currently unsure if Linux is affected.
Silent Fail if port istakenSilent Fail if port is already in use
I updated this to include a few ideas and to reformat the description with a more readable format.
This bug still exists in the latest version.