Server wont start about minecraftbedrockserver

[TheRemote]

Impossible to say. There's no information there other than it failed to start. We may need to check a couple of other places here.

Have you tried launching the server manually? How about the log files in the "logs" folder? What's your distro? It's pretty unusual to have problems on a mainline distro that's functioning correctly.

It's natively compiled x86_64 C++ code so it's quite fast. This makes it unlikely to be system requirements related unless you're trying to run it on ARM or a 32 bit processor. Often when checking these it will be very obvious what it is as I often don't hear back after telling people to look at those.

I'm guessing that's because they feel embarrassed but they shouldn't because it's totally fine if it ends up being something obvious / easy and nobody should feel embarrassed by that as the interaction gets saved in the "Closed" issues and helps at least some XX% of people having the same issue (maybe even dozens or hundreds+ of people in some cases for really common issues over years of time)!

Modern servers are very complex and have a lot of moving parts and pieces and I'm always impressed by all the different use cases a lot of you have running the script. We can take a look at any of it if weird things are happening like this. I still see things I've never seen over years of the script regularly and even still have to fix bugs (and probably always will).

If there is no log file output then it would point to some other kind of system issue. The best way to find these is to launch manually.

You can launch manually by going to your minecraft server's folder and then using the weird instructions from https://www.minecraft.net/en-us/download/server/bedrock. This will throw any errors right to your console if it's being extra elusive and not turning up in any log files/anywhere. A manual launch will look something like this (from your server folder):

LD_LIBRARY_PATH=. ./bedrock_server

You can definitely post any of the log output here as well like you did the systemd log and we can get it going I'm sure!

[ActionHDYT]

If i start it manually It Shows me this Error:
glibc_2.27 Not found

[ActionHDYT]

Jan 03 19:57:27 rs-zap753258-1 bash[6108]: -T term Use term as $TERM for windows, rather than "screen".
Jan 03 19:57:27 rs-zap753258-1 bash[6108]: -U Tell screen to use UTF-8 encoding.
Jan 03 19:57:27 rs-zap753258-1 bash[6108]: -v Print "Screen version 4.05.00 (GNU) 10-Dec-16".
Jan 03 19:57:27 rs-zap753258-1 bash[6108]: -wipe [match] Do nothing, just clean up SockDir [on possible matches].
Jan 03 19:57:27 rs-zap753258-1 bash[6108]: -x Attach to a not detached screen. (Multi display mode).
Jan 03 19:57:27 rs-zap753258-1 bash[6108]: -X Execute as a screen command in the specified session.
Jan 03 19:57:27 rs-zap753258-1 bash[6108]: Error: Unknown option Logfile
Jan 03 19:57:27 rs-zap753258-1 sudo[6100]: pam_unix(sudo:session): session closed for user root
Jan 03 19:57:27 rs-zap753258-1 systemd[1]: BedrockServer.service: Control process exited, code=exited status=1
Jan 03 19:57:27 rs-zap753258-1 systemd[1]: Failed to start BedrockServer Minecraft Bedrock Server.
-- Subject: Unit BedrockServer.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support

-- Unit BedrockServer.service has failed.

-- The result is failed.
Jan 03 19:57:27 rs-zap753258-1 systemd[1]: BedrockServer.service: Unit entered failed state.
Jan 03 19:57:27 rs-zap753258-1 systemd[1]: BedrockServer.service: Failed with result 'exit-code'.
Jan 03 19:58:52 rs-zap753258-1 su[6193]: Successful su for root by BedrockServer
Jan 03 19:58:52 rs-zap753258-1 su[6193]: + /dev/pts/0 BedrockServer:root
Jan 03 19:58:52 rs-zap753258-1 su[6193]: pam_unix(su:session): session opened for user root by root(uid=1001)
Jan 03 19:58:52 rs-zap753258-1 su[6193]: pam_systemd(su:session): Cannot create session: Already running in a session

[TheRemote]

Hmmm, that's an interesting one. It looks like you have a non-standard version of screen. Which distro is this?

It's also too old of a distro to run Minecraft. glibc_2.27 Not found means you don't have the version of C installed that Minecraft was compiled against. That should not be possible unless this is not a 64 bit processor or is running a very old distro (like 3-5+ years outdated probably with no apt update or patches).

Theoretically you could remove the -LogFile option from start.sh manually to see if it runs fine otherwise. The error you posted is complaining that your version of screen does not have the -LogFile option. I've literally never seen it before so I'm curious what this is running on.

Given that your manual launch though says you're missing the C library I don't think fixing the screen command will help. My guess is this is a 32 bit distro or is missing 5+ years of patches and needs updates. Whatever it is, it's not compatible with the Minecraft Bedrock server. Whether it can be fixed with updates is the question.

Can you post the output from your:

cat /etc/os-release

and

uname -a?

It's not actually possible to be missing glibc (the Linux kernel itself and all built in utilities use it, it wouldn't work or even boot without it). It means your distro's version of glibc it is using is way too old and needs updates / a complete reimage/reinstall usually. For example Ubuntu 16.04 is no longer supported and 18.04 might not be that far behind if it's not supported already.

Technically Ubuntu is the only supported OS (for Linux) according to https://www.minecraft.net/en-us/download/server/bedrock. Lots of people use other ones though but they do need to be up to date. It's distro related for sure, and if you have a 32 bit processor it won't be possible to run at all.

That screen version of 4.5.0 actually dates your system pretty well to right where I expected. That is from ~2016 so we are looking at no patches for at least 5-6 years. Here's a hack for it that will root your entire server: https://cxsecurity.com/issue/WLB-2017010196. This is an extremely dangerous version of screen to have in 2022. That exploit has already been public for 5 years. This box needs updates from apt or whatever your package manager is ASAP. It may be rooted already as that can often explain these broken updates (it's intentional on the attacker's part).

Every time I've seen this (this isn't the first) they ended up reinstalling a newer OS and everything was fine after that. I would assume that box is compromised at this point if there is even a single port forwarded to it. Screen isn't the only thing unpatched with critical vulnerabilities, it will be everything including your kernel and there's THOUSANDS of exploits out there for your entire 2016 configuration.

This actually reminds me of this situation here: https://jamesachambers.com/minecraft-bedrock-edition-ubuntu-dedicated-server-guide/#comment-11497. This individual also had 4-5 year old packages on their system. He was trying to run apt and it said it was up to date but he was running a 2018 kernel all the same (newer than this one, he actually got much further before weird things started happening since he was a year closer to up to date than this one).

The entire ordeal could probably be fixed within 1-2 hours if you reinstall the latest fresh copy of the Linux you want to use (preferably Ubuntu for this but others can work). It will also probably make whatever else you're doing with that server work 100x better as it did for Jonathan.

Let's see what those commands show!

[ActionHDYT]

PRETTY_NAME="Debian GNU/Linux 9 (stretch)"
NAME="Debian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
VERSION_CODENAME=stretch
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

[ActionHDYT]

Linux rs-zap753258-1 4.9.0-16-amd64 #1 SMP Debian 4.9.272-2 (2021-07-19) x86_64 GNU/Linux

[TheRemote]

I wonder why Stretch doesn't have an update in LTS for screen. It's too old though. Look at what version of glibc stretch uses at https://packages.debian.org/source/stretch/glibc:

2.24

Stretch's LTS support ends in June of this year. This is basically the Debian equivalent though of still running Ubuntu 16.04/18.04. The glibc is too old for the newer Minecraft versions. You'd have to download a build of the Minecraft Bedrock dedicated server that is several years old for it to run on that.

Debian 10 (buster) has glibc 2.28 and will work as will all newer ones. It looks like you will have to upgrade though even though you're caught at the very tail end of LTS for Stretch. Hopefully that gets it for you!

[ActionHDYT]

How can i upgrade to debian 10 without loosing my data?

[TheRemote]

Is this a VPS or dedicated server you are leasing? Or do you actually have this server physically? If you are leasing a private server it's honestly easier to just rent a new one that comes with Debian 10 or higher and then transfer everything and delete the old one.

Either way you'd want to make sure you have everything backed up. Things can definitely go wrong upgrading old systems.

Here's the instructions, but you shouldn't try them until you can say "I am not concerned about losing my data because I have made the proper backups": https://www.cyberciti.biz/faq/update-upgrade-debian-9-to-debian-10-buster/

It's supposed to be easy, but that's assuming everything on the system is working correctly. It seems to be best I can tell (your kernel is up to date so you're at least getting the latest versions you're going to get with Stretch) but you would know that better than I would.

Either way, don't risk it without proper backups first. It's all at your own risk and I wouldn't risk it in my job without backups, but if you have those it should be pretty easy and is only a small handful of commands in the link above.

[ActionHDYT]

Its a server from ZapHosting

[ActionHDYT]

Are there any important settings I should save or just my files?

I have used the server only for the java server AllTheMods3

[ActionHDYT]

With Debian 10 it finally worked! Thanks for your help!

[TheRemote]

I was really relieved to see this! I got a little nervous when you asked about the backups as I have personally ran into problems doing upgrades like this many times. I mean usually it's fine at least 95%+ of the time but the small % where it's not are really dicey if there's no backups.

Congratulations on getting it working, enjoy and have fun!