BDS-324PLEASE CLOSE as not an issue: Alpha Server has stopped listening on its TCP ports
Since some time in the afternoon of 21st December 2018 the server has stopped listening on its TCP ports. Confirmed with netstat -atn. Things that don't help:
- Restarting the server
- Starting the server with a new world
- Completely re-downloading and unzipping from scratch the bedrock-server-1.8.0.24.zip and starting from scratch
- Rebooting the host
- Changing the listening ports to other values
- Running as root
Not tried (limitations of my hosting provider prevent me): resetting my clock back 24 hours!
I do not believe any system updates have been applied today.
No errors or issues are logged either by the server or by Linux - to all evidence the server starts normally, claims to be running on the specified ports, but is not.
strace output (attached, with minor edits to remove IP addresses and other identifying information) suggests the sockets are created and bound successfully (but possibly are abandoned later in the startup process?)
Environment
Ubuntu Linux 18.04 LTS virtual server running alpha bedrock-server-1.8.0.24
Attachments1
Comments1
History3
Changed description:
Since some time in the afternoon of 21st December 2018 the server has stopped listening on its TCP ports. Confirmed with netstat -atn. Things that don't help:
0- 0
- Restarting the server 0
- Starting the server with a new world 0
- Completely re-downloading and unzipping from scratch the bedrock-server-1.8.0.24.zip and starting from scratch 0
- Rebooting the host 0
- Changing the listening ports to other values 0
- Running as root
Not tried (limitations of my hosting provider prevent me): resetting my clock back 24 hours!
0I do not believe any system updates have been applied today.
00
No errors or issues are logged either by the server or by Linux - to all evidence the server starts normally, claims to be running on the specified ports, but is not.
00
strace output (attached, with minor edits to remove IP addresses and other identifying information) suggests the sockets are created and bound successfully (but possibly are abandoned later in the startup process?)
Resolution: Unresolved → Invalid
For shame: