mojira.dev
BDS-847

SIGTERM doesn't make Ubuntu Bedrock Server save and quit gracefully.

Resolved
Duplicate
0

When the minecraft dedicated server gets a SIGTERM signal, it doesn't save and quit gracefully. It just immediately kills the process without saving.

I'm currently running BDS as a systemd service, so I'd like to not lose data if I have to call "systemctl stop minecraft".

Linked issues

duplicates 1

Comments 23

I am having this issue also.
If terminated 'ungracefully', ports get tied up and the server cannot restart without freeing those ports or a system reboot.

I am having this issue also.
If terminated 'ungracefully', ports get tied up and the server cannot restart without freeing those ports or a system reboot.

I am having this issue also.
If terminated 'ungracefully', ports get tied up and the server cannot restart without freeing those ports or a system reboot.

For now you can use tmux to work around it.

ExecStart=/usr/bin/tmux new -ds mcbe 'LD_LIBRARY_PATH=. ./bedrock_server'`

ExecStop=/usr/bin/tmux sendkeys -t mcbe:0.0 stop Enter

You can't have more than 1 instance per tmux socket, but you can use the -S flag for that if you must. Hopefully they change their handling of SIGTERM from apathetically to cleanly.

Hi,

Is this still an issue in 1.14.32.1?

I know enough about linux to be dangerous and help test some of the issues here but this one is a little outside my wheel house.

If someone is able to test and confirm that would be amazing.

Ionic

13 more comments

I can confirm server version 1.16.201.3 on ubuntu and windows do not handle SIGTERM correctly. The server process ends immediately and does not shut down correctly.

 

What I expected to happen was...:

When I type ctrl+c, I expect the server to shut down as if I had issued the stop command.

 

What actually happened was...:

Instead, the process exits immediately without properly shutting down. 

 

Steps to Reproduce:

  1. Start the server

  2. With the server's terminal window active, press ctrl+c

I can confirm server version 1.16.201.3 on ubuntu and windows do not handle SIGTERM correctly. The server process ends immediately and does not shut down correctly.

 

What I expected to happen was...:

When I type ctrl+c, I expect the server to shut down as if I had issued the stop command.

 

What actually happened was...:

Instead, the process exits immediately without properly shutting down. 

 

Steps to Reproduce:

  1. Start the server

  2. With the server's terminal window active, press ctrl+c

Thank you for your report!
We're tracking this issue in BDS-203, so this ticket is being resolved and linked as a duplicate.

If you would like to add a vote and any extra information to the main ticket it would be appreciated.

If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.

Quick Links:
📓 Bug Tracker Guidelines – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 BDS Wiki – 📖 FAQs

Thank you for your report!
We're tracking this issue in BDS-203, so this ticket is being resolved and linked as a duplicate.

If you would like to add a vote and any extra information to the main ticket it would be appreciated.

If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.

Quick Links:
📓 Bug Tracker Guidelines – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 BDS Wiki – 📖 FAQs

Thank you for your report!
We're tracking this issue in BDS-203, so this ticket is being resolved and linked as a duplicate.

If you would like to add a vote and any extra information to the main ticket it would be appreciated.

If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.

Quick Links:
📓 Bug Tracker Guidelines – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 BDS Wiki – 📖 FAQs

migrated

(Unassigned)

Plausible

awaiting-response

Retrieved