systemd minecraft service failure

[stxdigitizing]

I have been using this script for a while now. works great every time until something unknown happens. This isn't the first time I've had issues with starting the minecraft server. usually when the SYSTEMD fails I can manually start the server using the ./bedrock_server command. but this time didn't work... I receive this error when starting the service.

Aug 27 14:02:28 minecraftrm bash[1677]: % Total % Received % Xferd Average Speed Time Time Time Current Aug 27 14:02:28 minecraftrm bash[1677]: Dload Upload Total Spent Left Speed Aug 27 14:02:28 minecraftrm bash[1677]: [237B blob data] Aug 27 14:02:28 minecraftrm bash[1677]: Minecraft Bedrock server is up to date... Aug 27 14:02:28 minecraftrm bash[1677]: Starting Minecraft server. To view window type screen -r Realm Aug 27 14:02:28 minecraftrm bash[1677]: To minimize the window and let the server run in the background, press Ctrl+A then Ctrl+D Aug 27 14:02:28 minecraftrm systemd[1]: Started Realm Minecraft Bedrock Server. Aug 27 14:02:28 minecraftrm bash[1737]: Server is not currently running! Aug 27 14:02:28 minecraftrm systemd[1]: Realm.service: Control process exited, code=exited status=1 Aug 27 14:02:28 minecraftrm systemd[1]: Realm.service: Failed with result 'exit-code'. I do not see any other errors...

I have already deleted all instances of the server and did a fresh install but does the same thing...

any thoughts?

[TheRemote]

Can you post the output from the latest file in your "logs" folder? I'm not seeing anything useful that will help us in the systemd output here so it doesn't look service related. I'm guessing the server is crashing/failing to start in a way that the logs will make a lot more clear!

[stxdigitizing]

That's the weird thing... log files are there but they are blank 0 kilobyte files.

[TheRemote]

The files being 0kb would indicate your partition/HDD is corrupt and needs an fsck/reimage or perhaps that you're somehow missing the screen application but since you said you ran the installer fresh that would have replaced the "screen" dependency if it was missing. There should always be something in there even if it's a launch error or permissions error etc. and having 0kb files would point to unstable storage.

What does it say when you start bedrock_server manually? It should just output what is going wrong on the screen in that case.

[stxdigitizing]

When I start it manually it tells me anything server does not start at all. this is what it looks like. no output

jlopez@minecraftrm:~/minecraftbe/Realm$ ./bedrock_server jlopez@minecraftrm:~/minecraftbe/Realm$

[TheRemote]

Hmmm, that should not be possible. You probably know this from launching the server manually before but when you launch it manually there is no "screen" application or background. The console literally opens in your terminal and can't really be dismissed to the background.

It doesn't even seem like it's crashing. I don't see any error messages or output of any kind. This application is not a background daemon though and doesn't have those capabilities (which is why I had to wrap it in screen). It just seems like it's silently closing itself but I've never seen anything like it in all the years the Bedrock server has been around.

Can you try running ./fixpermissions.sh from inside the server folder? It's supposed to do this on startup but yours is so broken I think we better try it manually.

What does ldd bedrock_server say? How about file bedrock_server? Let's see the file permissions too with ls -la. I'd seriously recommend giving it a fsck by just doing sudo touch /forcefsck and then rebooting because of the 0kb logs thing though and this mystery silently won't launch with zero output of any kind. Never seen anything like it and definitely not normal behavior!

[stxdigitizing]

Leave it up to me to find the weird stuff...

i ran the ./fixpermissions.sh twice already same issue.

ldd bedrock_server not a dynamic executable file bedrock_server bedrock_server: empty

drwxrwxr-x 17 jlopez jlopez 4096 Aug 27 13:24 . drwxrwxr-x 3 jlopez jlopez 4096 Jul 3 17:28 .. drwxrwxr-x 2 jlopez jlopez 4096 Aug 27 15:05 backups -rwxr-xr-x 1 jlopez jlopez 0 Aug 5 19:26 bedrock_server -rw-rw-r-- 1 jlopez jlopez 0 Aug 5 19:14 bedrock_server_how_to.html -rwxrwxr-x 1 jlopez jlopez 0 Aug 5 19:26 bedrock_server_symbols.debug drwxr-xr-x 17 jlopez jlopez 4096 Jul 14 04:00 behavior_packs -rw-r--r-- 1 jlopez jlopez 0 Aug 9 17:45 Dedicated_Server.txt drwxr-xr-x 9 jlopez jlopez 4096 Jun 15 15:59 definitions drwxr-xr-x 2 jlopez jlopez 4096 Jul 3 17:29 development_behavior_packs drwxr-xr-x 2 jlopez jlopez 4096 Jul 3 17:29 development_resource_packs drwxr-xr-x 2 jlopez jlopez 4096 Jul 3 17:29 development_skin_packs drwxrwxr-x 2 jlopez jlopez 4096 Aug 9 17:45 downloads -rwxr-xr-x 1 jlopez jlopez 2064 Aug 27 13:22 fixpermissions.sh drwxrwxr-x 2 jlopez jlopez 4096 Aug 27 15:05 logs drwxr-xr-x 2 jlopez jlopez 4096 Jul 3 17:29 minecraftpe -rw-r--r-- 1 jlopez jlopez 315 Jul 3 17:38 permissions.json drwxr-xr-x 2 jlopez jlopez 4096 Jul 3 17:29 premium_cache -rw-rw-r-- 1 jlopez jlopez 0 Aug 5 19:14 release-notes.txt drwxr-xr-x 4 jlopez jlopez 4096 Jun 15 15:59 resource_packs -rwxr-xr-x 1 jlopez jlopez 2874 Aug 27 13:22 restart.sh -rw-r--r-- 1 jlopez jlopez 2641 Jul 3 17:42 server-icon.png -rw-r--r-- 1 jlopez jlopez 4936 Aug 27 13:22 server.properties -rwxr-xr-x 1 jlopez jlopez 4671 Aug 27 13:22 start.sh -rwxr-xr-x 1 jlopez jlopez 2801 Aug 27 13:22 stop.sh drwxr-xr-x 14 jlopez jlopez 4096 Jun 15 15:59 structures drwxr-xr-x 3 jlopez jlopez 4096 Jul 3 17:29 treatments -rwxr-xr-x 1 jlopez jlopez 497 Aug 27 13:22 update.sh -rw-r--r-- 1 jlopez jlopez 2865 Aug 9 17:45 valid_known_packs.json -rw-r--r-- 1 jlopez jlopez 3 Jun 15 15:37 whitelist.json drwxrwxr-x 3 jlopez jlopez 4096 Jul 3 17:37 worlds drwxr-xr-x 2 jlopez jlopez 4096 Jul 3 17:29 world_templates

[TheRemote]

Ahh yeah that explains it. The bedrock_server file is also empty (0 bytes) like your log files. Everything that comes out of the zip is but the scripts themselves (start.sh etc.) actually aren't 0 bytes but release-notes, etc. are.

You definitely have some sort of corrupt disk/partition going on here for sure. A fsck might not even do it if there's this many missing files that are 0kb but I would definitely start there!

You could also reinstall again and see if you can get the files to not be 0kb but that is very, very strange! I suspect a reinstall using the script will get these to not be 0kb but you'll come back and check after trying to launch and they will magically be 0 bytes again. It's classic disk corruption/partition tables symptoms!

[stxdigitizing]

let me give it a go and i'll report back.

[TheRemote]

Sounds good, with any luck just a quick fsck will fix it if it's just one or two bad entries in the partition table (pretty common). All the 0 byte files are concerning but let's see what it finds, it could still be just one or two bad entries in a particularly disastrous place!

You'll want to reinstall using the script and restore from a backup again fresh when you do this as fixing the table will restore various versions of copies throughout this whole process it recovers and other nasty things like this resulting in a mish-mashed install of different versions from different points in time so make sure you start clean after any fixes (not to mention most of your server dependencies are hollow and 0 bytes)!

You'll also want to double check that the backup you are restoring isn't corrupted and full of 0 byte files. Maybe the backup itself is the problem and you'll want to use an older one. If you haven't been saving your rotated backups out of the folder now would be the time to grab the oldest ones in there before attempting any more starts which will cycle another backup through each time.

[stxdigitizing]

so I deleted folder and curl'd it again to install it worked however getting this now after i backed it up.

[2021-08-27 16:19:26] NO LOG FILE! - setting up server logging... [2021-08-27 16:19:26] [2021-08-27 16:19:26 INFO] Starting Server [2021-08-27 16:19:26] [2021-08-27 16:19:26 INFO] Version 1.17.11.01 [2021-08-27 16:19:26] [2021-08-27 16:19:26 INFO] Session ID 5f98e8aa-b556-4293-9a65-35f798646cec [2021-08-27 16:19:26] [2021-08-27 16:19:26 INFO] Level Name: Realm [2021-08-27 16:19:26] [2021-08-27 16:19:26 INFO] Game mode: 0 Survival [2021-08-27 16:19:26] [2021-08-27 16:19:26 INFO] Difficulty: 1 EASY [2021-08-27 16:19:26] [INFO] opening worlds/Realm/db [2021-08-27 16:19:26] [ERROR] DBStorage chain is invalid. Possibly encryption-related, or bad DBStorageConfig passed. Reason: Unable to decipher/decrypt LevelDB. [2021-08-27 16:19:26] [ERROR] Network port occupied, can't start server.

[TheRemote]

It says the network port is already occupied, are there multiple servers running?

The backup might be bad as well and you may want to try several to see if the behavior changes between the backups at all.

It could also be some problem with your system's certificate store and it really can't validate the certificate/encryption but the network port thing makes it sound like there might be multiple servers running.

I would give your whole system a reboot now and see if it runs normally!

[stxdigitizing]

No luck on the backups... the location /worlds/Realm/db the .log, CURRENT and Manifest files are all 0 kilobytes...

i have not good backup, so i just deleted those three files and it started right up fresh... with the same seed I had... it will be ok i guess. Just have to rebuild and start over...

[TheRemote]

Ugh, I'm sorry that didn't lead to a better outcome! Thanks for posting the resolution/outcome and for bearing with me. These are pretty hard to troubleshoot sometimes. Take care!

[stxdigitizing]

no it's good, with out problems arising you don't learn... what I learned now is to make a script that takes the backup folder and pushes it to an folder on my NAS and some how set args to warn if any of the important file have zero kilobytes before it overwrites. not sure if it's possible but going to give it a go.

I appreciate your help!

[stxdigitizing]

found this on Reddit and i was able to fix my world.

Minecraft Bedrock

The steps to recover a save on the bedrock edition are surprisingly similar to those shown in the video. They are different, however. Using the video I figured out how to recover a world in the bedrock edition after my own world became corrupted. Here are the steps:

Step 1: Same as java edition. Identify the problem.

If your problem is the same as the one in my example you may need to set your difficulty to peaceful before loading the fixed save, as it may crash again.

Step 2: Create a new world.

Again the same as java edition. This creates new, uncorrupted files that we need to repair the old world.

Step 3: Open your worlds directory.

This directory is a tough one to find. And a long one at that. Too long for me to type on mobile, so Here is a link to an answer on stack exchange on how to reach the directory.

Step 4: Find your new world folder.

After opening your minecraftworlds folder you should see files with names like "1g4AAHBsAQA=". These are your worlds. You can tell what world is what by opening the file and opening levelname.txt.

Step 5: Copy the new Level.dat and Level.dat_old files. Note that level.dat may display as only level in the world folder

Step 6: Go to the corrupt world and replace the two corrupt level.dat files with the two new ones.

This will fix your save and make it playable once again. You won't spawn in some random spot like in java edition and you will keep all of your items.

I hope this guide was able to help you fix your corrupt saves. And thanks to YouTuber KaysPlays for creating an amazing guide to help me recover my own world.

Have fun and enjoy playing on your worlds!