[BDS-18869] Port [19132] may be in use by another process Created: 27/Nov/23  Updated: 14/May/24  Resolved: 14/May/24

Status: Resolved
Project: Bedrock Dedicated Server
Affects Version/s: 1.20.41
Fix Version/s: None

Type: Bug
Reporter: ant177 Assignee: Unassigned
Resolution: Incomplete Votes: 2
Labels: None
Environment:

Linux Bedrock - Ubuntu 22.04.3 LTS


Confirmation Status: Unconfirmed

 Description   

I am experiencing the same issue as a previous user who created BDS-18482 (unfortunately they didn't follow the correct format for submitting bugs and the ticket was closed).

They were also using an older version but I still see the same behaviour with the latest version (1.20.41).

 

Steps to Reproduce

Download 1.20.41 for Linux

Execute server

Observed Result

NO LOG FILE! - setting up server logging...
[2023-11-27 16:54:54:834 INFO] Starting Server
[2023-11-27 16:54:54:834 INFO] Version: 1.20.41.02
[2023-11-27 16:54:54:834 INFO] Session ID: 9536223b-1e2c-45d0-aed5-f48f5ead37dc
[2023-11-27 16:54:54:834 INFO] Build ID: 19385779
[2023-11-27 16:54:54:834 INFO] Branch: r/20_u4
[2023-11-27 16:54:54:834 INFO] Commit ID: fb9e4a5f54462276397ac295c1afe7df03b900d6
[2023-11-27 16:54:54:834 INFO] Configuration: Publish
[2023-11-27 16:54:54:835 INFO] Level Name: Bedrock level
[2023-11-27 16:54:54:836 INFO] No CDN config file found for dedicated server
[2023-11-27 16:54:54:836 INFO] Game mode: 0 Survival
[2023-11-27 16:54:54:836 INFO] Difficulty: 1 EASY
[2023-11-27 16:54:54:837 INFO] Content logging to console is enabled.
[2023-11-27 16:54:55:270 INFO] Opening level 'worlds/Bedrock level/db'
[2023-11-27 16:54:55:886 ERROR] Port [19132] may be in use by another process. Free up port and re-run program or adjust server.properties file to use alternate ports for server
[2023-11-27 16:54:55:886 ERROR] Port [19133] may be in use by another process. Free up port and re-run program or adjust server.properties file to use alternate ports for server
[2023-11-27 16:54:55:886 ERROR] Exiting program


Expected Result

Server starts and binds successfully to port 19132

Additional Details

The output from

lsof -I -P -n | grep LISTEN

is

systemd         1            root   86u  IPv4      1214      0t0  TCP *:111 (LISTEN)
systemd         1            root   95u  IPv4  57739119      0t0  TCP *:9090 (LISTEN)
systemd-r  948947 systemd-resolve   14u  IPv4  57738395      0t0  TCP 127.0.0.53:53 (LISTEN)
docker-pr  950718            root    4u  IPv4  57746969      0t0  TCP *:9000 (LISTEN)
docker-pr  950735            root    4u  IPv4  57746986      0t0  TCP *:8000 (LISTEN)
rpcbind    976801            _rpc    4u  IPv4      1214      0t0  TCP *:111 (LISTEN)
sshd       976839            root    3u  IPv4  57772472      0t0  TCP *:22 (LISTEN)
xrdp-sesm  976855            root    7u  IPv4  57773783      0t0  TCP 127.0.0.1:3350 (LISTEN)
xrdp       976873            xrdp   11u  IPv4  57773834      0t0  TCP *:3389 (LISTEN)
cupsd      977008            root    6u  IPv4  57772774      0t0  TCP 127.0.0.1:631 (LISTEN)
Plex\x20M 1924431         anthony   10u  IPv4  89240391      0t0  TCP *:32400 (LISTEN)
Plex\x20M 1924431         anthony   11u  IPv4  89240393      0t0  TCP 127.0.0.1:32401 (LISTEN)
Plex\x20S 1924458         anthony    7u  IPv4  89238811      0t0  TCP 127.0.0.1:36653 (LISTEN)
Plex\x20T 1924497         anthony   10u  IPv4  89238815      0t0  TCP 127.0.0.1:32600 (LISTEN)
docker-pr 3126516            root    4u  IPv4  97003112      0t0  TCP *:18083 (LISTEN)
docker-pr 3126530            root    4u  IPv4  97005139      0t0  TCP *:1883 (LISTEN) 


 Comments   
Comment by [MCQA] Kinga Izdebska [ 14/May/24 ]

Cleaning up old tickets: This ticket had been set to 'Awaiting Response', but has not received a response from the reporter (~3 months+) so is being closed as Incomplete. If you feel this is still a valid issue then please comment, or create a new ticket following the Issue Guidelines which includes steps to reproduce the problem.

Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki

Comment by [MCQA] Kinga Izdebska [ 10/Jan/24 ]

Can you please try to configure your server with different ports?  You can do that by editing server.properties line: "server-port=19132" and "server-portv6=19133" be sure to turn off "enable-lan-visibility=true.
This will automatically reopen when you reply.

Comment by ant177 [ 08/Jan/24 ]

Hello, thank you for your response.

I added the log from the `lsof` output to the original ticket and 19132 does not appear in there.

Comment by [MCQA] v-magwar (Inactive) [ 08/Jan/24 ]

Have you tried to see if these commands would help you resolve the issue?
This should display user created process, if one exists: 

lsof -I -P -n | grep [Username]

This should display what uses this port:

lsof -I -P -n | grep 19132

This will automatically reopen when you reply.

Comment by DarylJReed [ 23/Dec/23 ]

I am also experiencing the same issue with version 1.20.51.01. I have tried directly on the server as well as in a docker.

Generated at Sat Jan 11 08:23:27 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.