Mojira Archive
BDS-13252

Silent Fail if port is already in use

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...

  1. Run a server using the Dedicated Server or an unofficial server software using the default 19132 port
  2. While the other server is running, start the dedicated server
  3. 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: 19133

Since 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: 0

And 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.

Environment

Windows 10

Linked Issues

is duplicated by1

BDS-18641Running Multiple BDS Instances on same hard drive CRASH.Duplicate

Comments3

Michael Malloy

I updated this to include a few ideas and to reformat the description with a more readable format.

[MCQA] Kinga Izdebska

Is this still an issue in the latest version? If so, can you please add it to the affected versions (or mention it if you are not the reporter).
This ticket will automatically reopen when you reply.

Michael Malloy

This bug still exists in the latest version.

History14

Michael Malloy

Added labels: server crash

Removed labels:

Michael Malloy

Changed description:

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.

0

Normally it would output:

0
0
0[INFO] IPv4 supported, port: 191320[INFO] IPv6 supported, port: 191330
0
0

But will instead output:

0
0
0[INFO] IPv4 supported, port: 00[INFO] IPv6 supported, port: 00
0
0

And then stop running without any more cues as to what the issue may be.

0

 

0

This is an issue on the Windows version, I haven't tested the Unix version yet.

Summary
0When 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.

0

Steps to reproduce...

0
    0
  1. Run a server using the Dedicated Server or an unofficial server software using the default 19132 port
    2. 0
  2. While the other server is running, start the dedicated server
    3. 0
  3. Issue happens as it tries to open the port
    4. 0
0

What actually happened...
0The server outputs:

0
0
0[INFO] IPv4 supported, port: 191320[INFO] IPv6 supported, port: 191330
0
0

And then stop running without any more cues as to what the issue may be.

0

What should happen...

0

Notes...
0On Java the global cap scales with the number of loaded chunks. This means the more players online, the higher the cap.
0While 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.
0On 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.

0
0

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.

0

Normally it would output:

0
0
0[INFO] IPv4 supported, port: 191320[INFO] IPv6 supported, port: 191330
0
0

But will instead output:

0
0
0[INFO] IPv4 supported, port: 00[INFO] IPv6 supported, port: 00
0
0

And then stop running without any more cues as to what the issue may be.

0

 

0

This is an issue on the Windows version, I haven't tested the Unix version yet.

Michael Malloy

Changed description:

Summary
0When 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.

00

Steps to reproduce...

0
    0
  1. Run a server using the Dedicated Server or an unofficial server software using the default 19132 port
    2. 0
  2. While the other server is running, start the dedicated server
    3. 0
  3. Issue happens as it tries to open the port
    4. 0
0

What actually happened...0
0The server outputs:

0
0
0[INFO] IPv4 supported, port: 191320[INFO] IPv6 supported, port: 191330
0
0

And then stop running without any more cues as to what the issue may be.

0

What should happen...

0

Notes...
0On Java the global cap scales with the number of loaded chunks. This means the more players online, the higher the cap.
0While 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.
0On 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.

0
0

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.0On Java the global cap scales with the number of loaded chunks. This means the more players online, the higher the cap.

0

Normally it would output:

0
0
0[INFO] IPv4 supported, port: 191320[INFO] IPv6 supported, port: 191330
0
0

But will instead output:

0
0
0[INFO] IPv4 supported, port: 00[INFO] IPv6 supported, port: 00
0
0

And then stop running without any more cues as to what the issue may be.0On 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.

0

 

0

This is an issue on the Windows version, I haven't tested the Unix version yet.

Summary
0 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.

0

Steps to reproduce...

00
    0
  1. Run a server using the Dedicated Server or an unofficial server software using the default 19132 port
    2. 0
  2. While the other server is running, start the dedicated server
    3. 0
  3. Issue happens as it tries to open the port
    4. 0
0

What I expected to happen...
0 Normally the server outputs the following:

0
0
0[INFO] IPv4 supported, port: 191320[INFO] IPv6 supported, port: 191330
0
00000

Since this wouldn't be true though, a message of some sort should appear.
0 A potential message could be "The port [port number] cannot be used. Please make sure no other software is currently using the port."

0

What actually happened...
0 The server outputs:

0000
0
0[INFO] IPv4 supported, port: 00[INFO] IPv6 supported, port: 00
0
0

And then stops running without any more cues as to what the issue may be.
0Notes...

00
    0
  • I have experienced this issue on Windows, and am currently unsure if Linux is affected.
    • 0
0

Michael Malloy

Changed description:

Summary
0 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.

0

Steps to reproduce...

0
    0
  1. Run a server using the Dedicated Server or an unofficial server software using the default 19132 port
    2. 0
  2. While the other server is running, start the dedicated server
    3. 0
  3. Issue happens as it tries to open the port
    4. 0
0

What I expected to happen...
0 Normally the server outputs the following:

0
0
0[INFO] IPv4 supported, port: 191320[INFO] IPv6 supported, port: 191330
0
0

Since this wouldn't be true though, a message of some sort should appear.
0 A potential message could be "The port [port number] cannot be used. Please make sure no other software is currently using the port."

0

What actually happened...
0 The server outputs:

0
0
0[INFO] IPv4 supported, port: 00[INFO] IPv6 supported, port: 00
0
0

And then stops running without any more cues as to what the issue may be.
0Notes...

0
    0
  • I have experienced this issue on Windows, and am currently unsure if Linux is affected.
    • 0
0

Summary
0 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.

0

Steps to reproduce...

0
    0
  1. Run a server using the Dedicated Server or an unofficial server software using the default 19132 port
    2. 0
  2. While the other server is running, start the dedicated server
    3. 0
  3. Issue happens as it tries to open the port
    4. 0
0

What I expected to happen...
0 Normally the server outputs the following:

0
0
0[INFO] IPv4 supported, port: 191320[INFO] IPv6 supported, port: 191330
0
0

Since this wouldn't be true though, a message of some sort should appear.
0 A potential message could be "The port [port number] cannot be used. Please make sure no other software is currently using the port."

0

What actually happened...
0 The server outputs:

0
0
0[INFO] IPv4 supported, port: 00[INFO] IPv6 supported, port: 00
0
0

And then stops running without any more cues as to what the issue may be.
0Notes...

0
    0
  • 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.
    • 0
  • I have experienced this issue on Windows, and am currently unsure if Linux is affected.
    • 0
0

Michael Malloy

Changed summary:

Silent Fail if port is taken Silent Fail if port is already in use

[MCQA] Kinga Izdebska

Resolution: Unresolved → Awaiting Response

Michael Malloy

Added affects versions: 1.17.2

[Bot] Arisa

Resolution: Awaiting Response → Unresolved

Michael Malloy

Added affects versions: 1.17.10

Maciej Piornik

Confirmation Status: Unconfirmed → Confirmed

Maciej Piornik

Added is duplicated by link:
BDS-18641Running Multiple BDS Instances on same hard drive CRASH.Duplicate

[Bot] Arisa

Added affects versions: 1.20.12 Hotfix

Unresolved
Michael Malloy
1
4
Confirmed
603657
crash server
1.17.10 1.16.220 1.17.2 1.20.12 Hotfix