OS: Ubuntu 20.04.2 LTS
Java: java version "15.0.1" 2020-10-20
UBUNTU SERVER
When executing bedrock_server as a none root user I get the following:
NO LOG FILE! - setting up server logging...
[2021-04-09 19:05:10 INFO] Starting Server
[2021-04-09 19:05:10 INFO] Version 1.16.220.02
[2021-04-09 19:05:10 INFO] Session ID c99cc735-51b0-4afe-af9e-0ec80fb338bb
[2021-04-09 19:05:10 INFO] Level Name: world
[2021-04-09 19:05:10 ERROR] Error opening allow list file: whitelist.json
[2021-04-09 19:05:10 INFO] Game mode: 0 Survival
[2021-04-09 19:05:10 INFO] Difficulty: 1 EASY
[INFO] opening worlds/world/db
[INFO] IPv4 supported, port: 0
[INFO] IPv6 supported, port: 0
[INFO] Package: com.mojang.minecraft.dedicatedserver
Version: 1.16.220.02
OS: Linux
Server start: 2021-04-09 19:05:10 EDT
Dmp timestamp: 2021-04-09 19:05:11 EDT
Upload Date: 2021-04-09 19:05:11 EDT
Session ID: c99cc735-51b0-4afe-af9e-0ec80fb338bb
Commit hash: 83dca9ce456063492dfe4a5f8f0ee6894c94b963
Build id: 5667913
CrashReporter Key: 201a5b52-21df-3391-8c78-e26feb03b5f7
Crash
[INFO]
Failed to open curl lib from binary, use libcurl.so instead
I made sure that bedrock_server is executable with 775 and 777
Linked issues
is duplicated by 14
Comments 69
I have been having this exact same issue. Presumably this is a bug. I have tried manually linking the libcurl.so library to the execution of ./bedrock_server, but nothing fixes it. I have restarted a reboot of my machine fixes it occasionally, but temporarily. Regardless of if I'm root or not, this error still occurs.
ubuntu@vps-6458aed1:~/MCscripts$ sudo LD_LIBRARY_PATH=. ./bedrock_server
NO LOG FILE! - setting up server logging...
[2021-04-10 00:03:55 INFO] Starting Server
[2021-04-10 00:03:55 INFO] Version 1.16.220.02
[2021-04-10 00:03:55 INFO] Session ID f4e072ae-f092-4ae6-81e5-804bfb1d05df
[2021-04-10 00:03:55 INFO] Level Name: Bedrock level
[2021-04-10 00:03:55 INFO] Game mode: 0 Survival
[2021-04-10 00:03:55 INFO] Difficulty: 1 EASY
[INFO] opening worlds/Bedrock level/db
[INFO] IPv4 supported, port: 0
[INFO] IPv6 supported, port: 0
[INFO] Package: com.mojang.minecraft.dedicatedserver
Version: 1.16.220.02
OS: Linux
Server start: 2021-04-10 00:03:55 UTC
Dmp timestamp: 2021-04-10 00:03:56 UTC
Upload Date: 2021-04-10 00:03:56 UTC
Session ID: f4e072ae-f092-4ae6-81e5-804bfb1d05df
Commit hash: 83dca9ce456063492dfe4a5f8f0ee6894c94b963
Build id: 5667913
CrashReporter Key: abe274b2-d47d-37d1-baa9-a846bbbe292f
Crash
[INFO]
Failed to open curl lib from binary, use libcurl.so instead
Here is my crash report as well. As previously mentioned, I have tried a multitude of library linking methods to try to link to the libcurl.so library. I know for a fact that I have permissions to execute bedrock_server as I have given myself, permission, in addition as try this directly at root. Nothing has fixed it. I've only had this issue since 1.16.220.
Also getting this error when attempting to launch Bedrock 1.16.220.02 on Ubuntu 20.04.2 LTS.
Note: No errors encountered with Bedrock 1.16.210.06.
Interesting note:
Running $ ldd bedrock_server for the 210.06 version lists 49 shared libraries, including libcurl.
But, ldd of the newer bedrock_server only lists 13 libraries. libcurl doesn't not appear in the list.
Here is the list:
linux-vdso.so.1 (0x00007fff2fdbb000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007fc2d33fb000)
libnsl.so.1 => /lib/x86_64-linux-gnu/libnsl.so.1 (0x00007fc2d33de000)
libssl.so.1.1 => /lib/x86_64-linux-gnu/libssl.so.1.1 (0x00007fc2d334b000)
libcrypto.so.1.1 => /lib/x86_64-linux-gnu/libcrypto.so.1.1 (0x00007fc2d3075000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fc2d306f000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007fc2d3064000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fc2d2f13000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fc2d2ef0000)
libstdc+.so.6 => /lib/x86_64-linux-gnu/libstdc+.so.6 (0x00007fc2d2d0f000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007fc2d2cf4000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fc2d2b02000)
/lib64/ld-linux-x86-64.so.2 (0x00007fc2d341f000)
Also getting this error when attempting to launch Bedrock 1.16.220.02 on Ubuntu 20.04.2 LTS.
Note: No errors encountered with Bedrock 1.16.210.06.
Interesting note:
Running $ ldd bedrock_server for the 210.06 version lists 49 shared libraries, including libcurl.
But, ldd of the newer bedrock_server only lists 13 libraries. libcurl doesn't not appear in the list.
Here is the list:
linux-vdso.so.1 (0x00007fff2fdbb000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007fc2d33fb000)
libnsl.so.1 => /lib/x86_64-linux-gnu/libnsl.so.1 (0x00007fc2d33de000)
libssl.so.1.1 => /lib/x86_64-linux-gnu/libssl.so.1.1 (0x00007fc2d334b000)
libcrypto.so.1.1 => /lib/x86_64-linux-gnu/libcrypto.so.1.1 (0x00007fc2d3075000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fc2d306f000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007fc2d3064000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fc2d2f13000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fc2d2ef0000)
libstdc+.so.6 => /lib/x86_64-linux-gnu/libstdc+.so.6 (0x00007fc2d2d0f000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007fc2d2cf4000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fc2d2b02000)
/lib64/ld-linux-x86-64.so.2 (0x00007fc2d341f000)
Hey guys i might can give u a clue here. If you get the error that says Failed to open curl lib from binary, use libcurl.so instead ** we've found out that this is no libary issue it is mostly due to that the server can't bind it's ports correctly.
Also new since this version is that IPv6 is working, which it kinda wasn't beforehand. So you also might wanna check if there are any conflicts regarding those ports.
I started getting the same error message as in duplicate ticket BDS-17206.
I'm running on Ubuntu 18.04.6 on AWS Lightsail and when executing "apt-get upgrade" I received this message:
The following package was automatically installed and is no longer required:
*linux-aws-5.4-headers-5.4.0-1083*
Use 'sudo apt autoremove' to remove it.
{*}I removed that package, but then when I tried launching bedrock_server, I started getting the error from this bug{*}:
[2022-xx-xx xx:xx:xx:xxx INFO] at gsignal (UnknownFile:?)
at abort (UnknownFile:?)
at __libc_start_main (UnknownFile:?)
Failed to open curl lib from binary, use libcurl.so instead
I rolled back to a previous server snapshot and things are resolved, though I'm getting the message again about linux-aws-5.4-headers being no longer required. I won't bother removing the package this time.
Sharing my experience/ resolution because I have a pretty common setup, having used online guides for setting up this server on Lightsail. I figure others will run into the same thing.
I started getting the same error message as in duplicate ticket BDS-17206.
I'm running on Ubuntu 18.04.6 on AWS Lightsail and when executing "apt-get upgrade" I received this message:
The following package was automatically installed and is no longer required:
*linux-aws-5.4-headers-5.4.0-1083*
Use 'sudo apt autoremove' to remove it.
{*}I removed that package, but then when I tried launching bedrock_server, I started getting the error from this bug{*}:
[2022-xx-xx xx:xx:xx:xxx INFO] at gsignal (UnknownFile:?)
at abort (UnknownFile:?)
at __libc_start_main (UnknownFile:?)
Failed to open curl lib from binary, use libcurl.so instead
I rolled back to a previous server snapshot and things are resolved, though I'm getting the message again about linux-aws-5.4-headers being no longer required. I won't bother removing the package this time.
Sharing my experience/ resolution because I have a pretty common setup, having used online guides for setting up this server on Lightsail. I figure others will run into the same thing.
This, or something ?related is still happening in 1.19.50.02.
Actually It's appears more like the bug reported in BDS-14895 and there's no mention of libcurl in the error log but that has been closed as a duplicate of this so that led me here.
It anecdotally seems to be related to portal use but it's not every time so it's hard to pin down.
[2022-12-18 02:29:08]: terminate called after throwing an instance of 'std::length_error'
[2022-12-18 02:29:08]: what(): basic_string::_M_create
[2022-12-18 02:29:08] [INFO]: Package: com.mojang.minecraft.dedicatedserver
[2022-12-18 02:29:08]: Version: 1.19.50.02
[2022-12-18 02:29:08]: OS: Linux
[2022-12-18 02:29:08]: Server start: Etc
[2022-12-18 02:29:08]: Dmp timestamp: Etc
[2022-12-18 02:29:08]: Upload Date: Etc
[2022-12-18 02:29:08]: Session ID: 0a5ef2a2-2ca8-4629-8ff1-bcec096e4491
[2022-12-18 02:29:08]: Commit hash: 5d857f742e68c08c522fe18490be059b15c50f68
[2022-12-18 02:29:08]: Build id: 12558004
[2022-12-18 02:29:08]: CrashReporter Key: 8c4937c1-64cb-3532-a8dc-1deb28f67293
[2022-12-18 02:29:08]: Crash
[2022-12-18 02:29:08] [INFO]: at gsignal (UnknownFile:?)
[2022-12-18 02:29:08]: at abort (UnknownFile:?)
Just saw this recently in version 1.20 of BDS. The server is running in a Debian 10 LXC container. I don't recall what was happening at the time.
[2023-09-12 16:28:44] terminate called after throwing an instance of 'std::length_error'
what(): vector::_M_default_append
[2023-09-12 16:28:44] [2023-09-12 16:28:44:977 INFO] Package: com.mojang.minecraft.dedicatedserver
[2023-09-12 16:28:44] Version: 1.20.14.01
[2023-09-12 16:28:44] OS: Linux
[2023-09-12 16:28:44] Server start: 2023-09-12 04:31:41 EDT
[2023-09-12 16:28:44] Dmp timestamp: 2023-09-12 16:28:44 EDT
[2023-09-12 16:28:44] Upload Date: 2023-09-12 16:28:44 EDT
[2023-09-12 16:28:44] Session ID: 58368b28-58ea-4b05-8161-94729c7e534b
[2023-09-12 16:28:44] Commit hash: aa6bec6a6021d5effb36cb2e97bd7e4ec54baf67
[2023-09-12 16:28:44] Build id: 17242466
[2023-09-12 16:28:44] CrashReporter Key: 8c4937c1-64cb-3532-a8dc-1deb28f67293
[2023-09-12 16:28:44]
[2023-09-12 16:28:44] Crash
[2023-09-12 16:28:44] [2023-09-12 16:28:44:977 INFO] at gsignal (UnknownFile:?)
[2023-09-12 16:28:44] at abort (UnknownFile:?)
[2023-09-12 16:28:44] at clone (UnknownFile:?)
[2023-09-12 16:28:44] e929f04d-b59e-4d92-88b2-e984647a5ee6
Just saw this recently in version 1.20 of BDS. The server is running in a Debian 10 LXC container. I don't recall what was happening at the time.
[2023-09-12 16:28:44] terminate called after throwing an instance of 'std::length_error'
what(): vector::_M_default_append
[2023-09-12 16:28:44] [2023-09-12 16:28:44:977 INFO] Package: com.mojang.minecraft.dedicatedserver
[2023-09-12 16:28:44] Version: 1.20.14.01
[2023-09-12 16:28:44] OS: Linux
[2023-09-12 16:28:44] Server start: 2023-09-12 04:31:41 EDT
[2023-09-12 16:28:44] Dmp timestamp: 2023-09-12 16:28:44 EDT
[2023-09-12 16:28:44] Upload Date: 2023-09-12 16:28:44 EDT
[2023-09-12 16:28:44] Session ID: 58368b28-58ea-4b05-8161-94729c7e534b
[2023-09-12 16:28:44] Commit hash: aa6bec6a6021d5effb36cb2e97bd7e4ec54baf67
[2023-09-12 16:28:44] Build id: 17242466
[2023-09-12 16:28:44] CrashReporter Key: 8c4937c1-64cb-3532-a8dc-1deb28f67293
[2023-09-12 16:28:44]
[2023-09-12 16:28:44] Crash
[2023-09-12 16:28:44] [2023-09-12 16:28:44:977 INFO] at gsignal (UnknownFile:?)
[2023-09-12 16:28:44] at abort (UnknownFile:?)
[2023-09-12 16:28:44] at clone (UnknownFile:?)
[2023-09-12 16:28:44] e929f04d-b59e-4d92-88b2-e984647a5ee6
I have been having this exact same issue. Presumably this is a bug. I have tried manually linking the libcurl.so library to the execution of ./bedrock_server, but nothing fixes it. I have restarted a reboot of my machine fixes it occasionally, but temporarily. Regardless of if I'm root or not, this error still occurs.
ubuntu@vps-6458aed1:~/MCscripts$ sudo LD_LIBRARY_PATH=. ./bedrock_server
NO LOG FILE! - setting up server logging...
[2021-04-10 00:03:55 INFO] Starting Server
[2021-04-10 00:03:55 INFO] Version 1.16.220.02
[2021-04-10 00:03:55 INFO] Session ID f4e072ae-f092-4ae6-81e5-804bfb1d05df
[2021-04-10 00:03:55 INFO] Level Name: Bedrock level
[2021-04-10 00:03:55 INFO] Game mode: 0 Survival
[2021-04-10 00:03:55 INFO] Difficulty: 1 EASY
[INFO] opening worlds/Bedrock level/db
[INFO] IPv4 supported, port: 0
[INFO] IPv6 supported, port: 0
[INFO] Package: com.mojang.minecraft.dedicatedserver
Version: 1.16.220.02
OS: Linux
Server start: 2021-04-10 00:03:55 UTC
Dmp timestamp: 2021-04-10 00:03:56 UTC
Upload Date: 2021-04-10 00:03:56 UTC
Session ID: f4e072ae-f092-4ae6-81e5-804bfb1d05df
Commit hash: 83dca9ce456063492dfe4a5f8f0ee6894c94b963
Build id: 5667913
CrashReporter Key: abe274b2-d47d-37d1-baa9-a846bbbe292f
Crash
[INFO]
Failed to open curl lib from binary, use libcurl.so instead
Here is my crash report as well. As previously mentioned, I have tried a multitude of library linking methods to try to link to the libcurl.so library. I know for a fact that I have permissions to execute bedrock_server as I have given myself, permission, in addition as try this directly at root. Nothing has fixed it. I've only had this issue since 1.16.220.