-
Bug
-
Resolution: Invalid
-
None
-
1.16.4
-
None
-
Minecraft dedicated Server
OS: Ubuntu 20.04.1 LTS x86_64
Kernel: 5.4.65-1-pve
CPU: AMD Ryzen 5 2600 (4) @ 3.400GHz
GPU: 22:00.0 ASPEED Technology, Inc. ASPEED Graphics Family
Memory: 6144MiB
Note: The Server is running within an LXC container.
openjdk 13.0.3 2020-04-14
OpenJDK Runtime Environment (build 13.0.3+3-Ubuntu-1ubuntu2)
OpenJDK 64-Bit Server VM (build 13.0.3+3-Ubuntu-1ubuntu2, mixed mode, sharing)Minecraft dedicated Server OS: Ubuntu 20.04.1 LTS x86_64 Kernel: 5.4.65-1-pve CPU: AMD Ryzen 5 2600 (4) @ 3.400GHz GPU: 22:00.0 ASPEED Technology, Inc. ASPEED Graphics Family Memory: 6144MiB Note: The Server is running within an LXC container. openjdk 13.0.3 2020-04-14 OpenJDK Runtime Environment (build 13.0.3+3-Ubuntu-1ubuntu2) OpenJDK 64-Bit Server VM (build 13.0.3+3-Ubuntu-1ubuntu2, mixed mode, sharing)
-
Unconfirmed
-
(Unassigned)
The problem:
The Server console became unresponsive. I could not do anything via the server console and had to kill the server via `kill -9 <pid>` as `kill <pid>` did not kill the server. While the lag was most likely caused by the lava cast (picture below), it should not make the server console unresponsive that you cannot stop it via the console.
What I expected:
I expected that despite the server lagging, I could still stop it normally and interact with the server console or atleast execute `kill <pid>` instead of `kill -9 <pid>`.
I don't know if it is relevant to this particular issue, but the lava cast did cause a server crash a few hours before (crash log below).
