Control: tags -1 moreinfo On 23.06.2016 21:42, dr4Ke wrote: > Package: minetest-server > Version: 0.4.14+repack-3 > Severity: normal > Tags: patch > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate *** > > * What led up to the situation? > Restarting the minetest-server service > > * What exactly did you do (or not do) that was effective (or > ineffective)? > I just restarted the minetest-server service > > * What was the outcome of this action? > Some mod data was not present at the next boot, because of two combined > issues: > - the mod is saving its data with register_on_shutdown which is not safe from > a server failure > - the systemd service kills the minetest-server process instead of shuting it > down properly. > > * What outcome did you expect instead? > We can shutdown the minetest-server properly with a kill signal: SIGINT. >
What minetest modification caused the server failure? How can we reproduce the data inconsistency? Restarting the server is equivalent with stopping and starting the server again. Systemd will send a SIGTERM signal by default to the server to terminate the running process. I don't see a reason why we should use a different KillSignal in this case. SIGINT means interrupting the process. I suggest to investigate the cause of the server failure and then report your findings to the mod developers. If they think it is rather a minetest bug, please get in contact with the minetest developers directly because this is the fastest way to get your issue solved. If you want to play with different service file settings, use a modified service file in /etc/systemd/system to override Debian's default settings. Regards, Markus
signature.asc
Description: OpenPGP digital signature
