[BDS-12751] Failed to open curl lib from binary, use libcurl.so instead Created: 09/Apr/21  Updated: 04/Jan/24  Resolved: 04/Jan/24

Status: Resolved
Project: Bedrock Dedicated Server
Affects Version/s: 1.17.11 Hotfix, 1.16.200, 1.16.201 Hotfix, 1.16.201.03 Hotfix, 1.16.210, 1.16.220, 1.17.1, 1.17.2, 1.17.30, 1.18.0, 1.18.2 Hotfix, 1.19.2 Hotfix
Fix Version/s: None

Type: Bug
Reporter: yoni Assignee: Unassigned
Resolution: Fixed Votes: 40
Labels: None
Environment:

java version "15.0.1" 2020-10-20
OS: Ubuntu 20.04.2 LTS


Issue Links:
Duplicate
is duplicated by BDS-12667 bedrock server not launching Resolved
is duplicated by BDS-12695 Release 1.16.220.02 is broken Resolved
is duplicated by BDS-13318 Failure to open curl lib causing crash Resolved
is duplicated by BDS-13752 Server crash randomly Resolved
is duplicated by BDS-13806 Client Version leads to Corrupt World Resolved
is duplicated by BDS-14212 bds crashing randomly Resolved
is duplicated by BDS-14895 Server crashes Resolved
is duplicated by BDS-14979 Failed to open curl lib from binary, ... Resolved
is duplicated by BDS-15577 Server Crashing Resolved
is duplicated by BDS-15864 server (bedrock dedicated server) shu... Resolved
is duplicated by BDS-16472 Bedrock server does not start on Linu... Resolved
is duplicated by BDS-16726 Failed to open curl lib from binary, ... Resolved
is duplicated by BDS-17206 bedrock dedicated server for ubuntu w... Resolved
is duplicated by MCPE-147907 Client and server crash due to stuck ... Resolved
Confirmation Status: Community Consensus
ADO: 614346

 Description   

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 



 Comments   
Comment by mrtumnus [ 22/Sep/23 ]

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 
Comment by RotatedOwlFace [ 18/Dec/22 ]

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:?)

Comment by Rob Farley [ 23/Sep/22 ]

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.

 

 

Comment by Omar Berrow [ 08/Jul/22 ]

it seems like restarting the computer bedrock_server was running on fixes the problem at least for some time

Comment by Owen Brooks [ 04/Jul/22 ]

This has happened twice now after recently switching to Linux hosting from Windows 10. First time was a failed start, ran bedrock_server_symbols.debug and all was fine. This seems to resolve the problem in the short term.

The second time, Player reports destroying their old Portal just before the crash.  Location of Player was around 3000, , 6000 blocks from spawn when the portal was broken.

Crash report that was generated for the second crash:

[2022-07-04 14:27:45:303 INFO] Package: com.mojang.minecraft.dedicatedserver
Version: 1.19.2.02
OS: Linux
Server start: 2022-07-04 12:19:41 EDT
Dmp timestamp: 2022-07-04 14:27:45 EDT
Upload Date: 2022-07-04 14:27:45 EDT
Session ID: cd45c973-227f-409d-a04d-7b70da613319
Commit hash: b3394b7158e4fbb6c99df8addd52f13420b1dcf8
Build id: 10134919
CrashReporter Key: 8c4937c1-64cb-3532-a8dc-1deb28f67293

Crash
[2022-07-04 14:27:45:303 INFO]     at clone (UnknownFile:?)
Failed to open curl lib from binary, use libcurl.so instead

Comment by Thomas Mackey [ 10/Jun/22 ]

This is an update for what I found about this bug. The server only appears to throw this error when having a used map on person after traveling a decent distance or when coming into render distance with something like a village while having currently used map in the inventory.

Hope this helps to narrow the issue down. 

Comment by Thomas Mackey [ 08/Jun/22 ]

Been getting this bug still in 1.19. Below is the general info it gives. I have noticed that the crash is most commonly triggered when mapping out or traveling a long distance. The crash tends to happen after 1000 to 3000 blocks are traveled. The crash chance is greatly increased when using elytra with fireworks, being every min or two. The crash is further increased when in old regions or near old mobs/villages. There have also been a few accounts where this bug wouldn't fully crash the server and simply freeze up the world around the player keeping the player from fully disconnecting and needing a server reboot to kick the player and fix the problem. 

CrashReporter Key: 8c4937c1-64cb-3532-a8dc-1deb28f67293
08.06 16:59:39 [Server] INFO Crash
08.06 16:59:39 [Server] INFO [2022-06-08 16:59:39:538 INFO] at clone (UnknownFile:?)
08.06 16:59:39 [Server] INFO Failed to open curl lib from binary, use libcurl.so instead
08.06 16:59:40 [Server] INFO 5492212c-6e3e-4b10-bed2-33141f36c13d

 

Comment by Maksym Botsuliak [ 04/May/22 ]

I have the same problem, server just have crushed 2 times within an hour 

 

04.05 12:18:26 [Server] INFO Failed to open curl lib from binary, use libcurl.so instead
04.05 12:18:26 [Server] INFO [2022-05-04 12:18:26:461 INFO] Package: com.mojang.minecraft.dedicatedserver
04.05 12:18:26 [Server] INFO Version: 1.18.31.04
04.05 12:18:26 [Server] INFO OS: Linux
04.05 12:18:26 [Server] INFO Server start: 2022-05-04 01:19:14 UTC
04.05 12:18:26 [Server] INFO Dmp timestamp: 2022-05-04 12:18:26 UTC
04.05 12:18:26 [Server] INFO Upload Date: 2022-05-04 12:18:26 UTC
04.05 12:18:26 [Server] INFO Session ID: 02c0e3ae-74c2-467e-9971-cee5d91f7cff
04.05 12:18:26 [Server] INFO Commit hash: f267293d6b408ce0e742f4de3782cd93a836c004
04.05 12:18:26 [Server] INFO Build id: 9507213
04.05 12:18:26 [Server] INFO CrashReporter Key: f807d0f7-03c9-3bfd-adcf-74de3b6ce352
04.05 12:18:26 [Server] INFO Crash
04.05 12:18:26 [Server] INFO [2022-05-04 12:18:26:461 INFO] at clone (UnknownFile:?)
04.05 12:18:28 [Multicraft] Server shut down (running) 

Important info: we did use nether portals, a lot. Maybe bug is portal-related, hope that helps

Comment by Spazmonkey92 [ 02/May/22 ]

I'm also having this issue.
Ive had a bedrock world active for about a year on our server, hosted on ggservers.com

 

recently we've had a bunch of players repeatedly get kicked from the server, sometimes the server will crash when a player just logs in.

on the server console we keep getting the error: 

INFO Failed to open curl lib from binary, use libcurl.so instead

 

Heres our server console, when the crash happened:


  1. 01.05 12:57:12 [Server] INFO Package: com.mojang.minecraft.dedicatedserver

  2. 01.05 12:57:12 [Server] INFO Version: 1.18.30.04

  3. 01.05 12:57:12 [Server] INFO OS: Linux

  4. 01.05 12:57:12 [Server] INFO Server start: 2022-05-01 02:38:51 BST

  5. 01.05 12:57:12 [Server] INFO Dmp timestamp: 2022-05-01 12:57:12 BST

  6. 01.05 12:57:12 [Server] INFO Upload Date: 2022-05-01 12:57:12 BST

  7. 01.05 12:57:12 [Server] INFO Session ID: a309fd36-967a-43e8-a19e-780e824ae83e

  8. 01.05 12:57:12 [Server] INFO Commit hash: 49c247f9e920c88ad8f8aa0d338313c739e3d554

  9. 01.05 12:57:12 [Server] INFO Build id: 9208238

  10. 01.05 12:57:12 [Server] INFO CrashReporter Key: 8c4937c1-64cb-3532-a8dc-1deb28f67293

  11. 01.05 12:57:12 [Server] INFO Crash

  12. 01.05 12:57:12 [Server] INFO at clone (UnknownFile:?)

  13. 01.05 12:57:12 [Server] INFO Failed to open curl lib from binary, use libcurl.so instead

  14. 01.05 12:57:13 [Server] INFO 67a9881b-1272-48a5-9aae-12109fcc3ab4

  15. 01.05 12:57:13 [Multicraft] Server shut down (running)

  16. 01.05 12:57:13 [Multicraft] Restarting crashed server in 600.0 seconds

  17. 01.05 12:57:13 [Multicraft] Looks like a crash, check the server console. Return value: 1

  18. 01.05 12:57:13 [Multicraft] Server stopped

 

 

I have no idea what to do, or how to fix this.
GGsupport have reccomended to revert to a backup, but the best backups we have are from about a month ago, and i think back then, we were still getting this error just not as frequently.

Now we crash multiple times a day, and the server is crashing, more than its not.
The admins cant keep up with having to reset the server this often.

Comment by [Mojang] CornerHard [ 19/Feb/22 ]

Thanks for the info!

Comment by Lyarrah [ 18/Feb/22 ]

After a few more of these I can confirm that while it is far more likely to happen directly after someone goes through an End Portal (and is probably the easiest way for the devs to induce the problem if they'd like), it's not the only time. Out of the two servers I'm monitoring I've been seeing 1-2 of these crashes a day and out of the ~10 per week, ~7 are directly after entering or leaving the End (within 60 seconds after) and the other ~3 are not.

My current best theory is that it's got something to do with loading chunks that haven't yet been loaded since the server last restarted, especially because rapidly jumping in and out of the end doesn't seem to cause it if the initial entrance didn't.

Comment by Rayth [ 18/Feb/22 ]

Package: com.mojang.minecraft.dedicatedserver
Version: 1.18.12.01
OS: Linux
Server start: 2022-02-17 19:00:13 UTC
Dmp timestamp: 2022-02-18 05:54:27 UTC
Upload Date: 2022-02-18 05:54:27 UTC
Session ID: 30510f84-d336-43f5-a815-39277db1f073
Commit hash: ababe07645d9aae365226bc6b1959aab3584ed2c
Build id: 8537581
CrashReporter Key: 8c4937c1-64cb-3532-a8dc-1deb28f67293
Crash
[2022-02-18 05:54:27:890 INFO]  at clone (UnknownFile:?)
Failed to open curl lib from binary, use libcurl.so instead

Started watching console again after the new logging got added but doesn't appear to be anything new.

Some things I have noticed:

  • I've never encountered this on really small worlds with only 1-3 people. Seems to affect larger servers (1gb+ size)
  • Doesn't seem to matter how many people are online at a given time. Have seen it with as little as just 1.
  • Doesn't matter how much RAM, type of CPU or hard drive is in use. I've checked multiple different server hosts who have encountered this and the specifications are all different.
  • It's not regular. I can see days on a server that's set to restart every 12 hours and have no crash, then have the same server crash 2+ times in a 12hour period.
Comment by Manuel H [ 02/Feb/22 ]

Had this happening 3 days ago & yesterday:

 

[2022-01-30 20:44:00] [2022-01-30 20:44:00:326 INFO] Package: com.mojang.minecraft.dedicatedserver
[2022-01-30 20:44:00] Version: 1.18.2.03
[2022-01-30 20:44:00] OS: Linux
[2022-01-30 20:44:00] Server start: 2022-01-30 04:00:50 UTC
[2022-01-30 20:44:00] Dmp timestamp: 2022-01-30 20:44:00 UTC
[2022-01-30 20:44:00] Upload Date: 2022-01-30 20:44:00 UTC
[2022-01-30 20:44:00] Session ID: e429f216-d0e5-44a3-8d98-d116430c557a
[2022-01-30 20:44:00] Commit hash: 74c6ce6eb10dfe6b481aa14578b375b50a5d2028
[2022-01-30 20:44:00] Build id: 7966228
[2022-01-30 20:44:00] CrashReporter Key: 8c4937c1-64cb-3532-a8dc-1deb28f67293
[2022-01-30 20:44:00] 
[2022-01-30 20:44:00] Crash
[2022-01-30 20:44:00] [2022-01-30 20:44:00:326 INFO]    at clone (UnknownFile:?)
Failed to open curl lib from binary, use libcurl.so instead
[2022-01-30 20:44:01] de2ce7f7-a04f-4819-b7ab-97c8d5fbc028


[2022-02-01 22:09:17] [2022-02-01 22:09:17:127 INFO] Package: com.mojang.minecraft.dedicatedserver 
[2022-02-01 22:09:17] Version: 1.18.2.03 
[2022-02-01 22:09:17] OS: Linux 
[2022-02-01 22:09:17] Server start: 2022-02-01 04:00:46 UTC 
[2022-02-01 22:09:17] Dmp timestamp: 2022-02-01 22:09:17 UTC 
[2022-02-01 22:09:17] Upload Date: 2022-02-01 22:09:17 UTC 
[2022-02-01 22:09:17] Session ID: 685a4b94-a414-4dcd-9dd2-82b10a47fd55 
[2022-02-01 22:09:17] Commit hash: 74c6ce6eb10dfe6b481aa14578b375b50a5d2028 
[2022-02-01 22:09:17] Build id: 7966228 
[2022-02-01 22:09:17] CrashReporter Key: 8c4937c1-64cb-3532-a8dc-1deb28f67293 
[2022-02-01 22:09:17]  
[2022-02-01 22:09:17] Crash 
[2022-02-01 22:09:17] [2022-02-01 22:09:17:127 INFO]    at clone (UnknownFile:?) 
Failed to open curl lib from binary, use libcurl.so instead 
[2022-02-01 22:09:18] 778749a4-f1c2-4dac-9d97-b0f5ee64cdcf
Comment by Rayth [ 28/Jan/22 ]

Just had this as well with players reporting a rollback

 

[2022-01-28 06:27:45:139 INFO] Package: com.mojang.minecraft.dedicatedserver
Version: 1.18.2.03
OS: Linux
Server start: 2022-01-27 19:00:07 UTC
Dmp timestamp: 2022-01-28 06:27:45 UTC
Upload Date: 2022-01-28 06:27:45 UTC
Session ID: 84a35f14-e878-4309-8428-e267d252e594
Commit hash: 74c6ce6eb10dfe6b481aa14578b375b50a5d2028
Build id: 7966228
CrashReporter Key: 8c4937c1-64cb-3532-a8dc-1deb28f67293Crash
[2022-01-28 06:27:45:139 INFO]  at clone (UnknownFile:?)
Failed to open curl lib from binary, use libcurl.so instead

Comment by Lyarrah [ 21/Jan/22 ]

Had one of these happen yet again tonight, managed to grab the logs:

[2022-01-20 20:22:03] [INFO]: Package: com.mojang.minecraft.dedicatedserver
[2022-01-20 20:22:03]: Version: 1.18.2.03
[2022-01-20 20:22:03]: OS: Linux
[2022-01-20 20:22:03]: Server start: Etc
[2022-01-20 20:22:03]: Dmp timestamp: Etc
[2022-01-20 20:22:03]: Upload Date: Etc
[2022-01-20 20:22:03]: Session ID: 8c78d232-3a2d-47b8-b2e1-abc3ef2f9dc3
[2022-01-20 20:22:03]: Commit hash: 74c6ce6eb10dfe6b481aa14578b375b50a5d2028
[2022-01-20 20:22:03]: Build id: 7966228
[2022-01-20 20:22:03]: CrashReporter Key: 8c4937c1-64cb-3532-a8dc-1deb28f67293
[2022-01-20 20:22:03]: Crash
[2022-01-20 20:22:03] [INFO]: at clone (UnknownFile:?)
[2022-01-20 20:22:03]: Failed to open curl lib from binary, use libcurl.so instead 

This is happening about once every 1-2 days on both Linux servers I'm on. Sometimes it seems to be linked to people traveling to/from the End but a few cases have not involved that.

Generally, the crashes have caused a rollback of the game world but not of the players, of about 90 seconds. So for example, I placed down a shulker box about a minute before the crash happened, but when the server came back up it was no longer placed AND no longer in my inventory.

While this is fortunately not a constant problem like some crashes that were happening during Village & Pillage update, it's still enough that it's making people scared to lose things when they play. Very frustrating.

 

Edit: happened again just a few minutes ago, since mine's still the latest comment I'm just adding it in:

[2022-01-21 21:43:17] [INFO]: Package: com.mojang.minecraft.dedicatedserver
[2022-01-21 21:43:17]: Version: 1.18.2.03
[2022-01-21 21:43:17]: OS: Linux
[2022-01-21 21:43:17]: Server start: Etc
[2022-01-21 21:43:17]: Dmp timestamp: Etc
[2022-01-21 21:43:17]: Upload Date: Etc
[2022-01-21 21:43:17]: Session ID: 170b2275-63d3-45d2-b2ad-99de291bd79f
[2022-01-21 21:43:17]: Commit hash: 74c6ce6eb10dfe6b481aa14578b375b50a5d2028
[2022-01-21 21:43:17]: Build id: 7966228
[2022-01-21 21:43:17]: CrashReporter Key: 8c4937c1-64cb-3532-a8dc-1deb28f67293
[2022-01-21 21:43:17]: Crash
[2022-01-21 21:43:17] [INFO]: at clone (UnknownFile:?)
[2022-01-21 21:43:17]: Failed to open curl lib from binary, use libcurl.so instead
 
Comment by Usman Masood [ 28/Dec/21 ]

Any word on this?

Comment by Usman Masood [ 25/Dec/21 ]

+1 facing same issue on Ubuntu 20.04 server

 

NO LOG FILE! - [] setting up server logging...
[2021-12-25 14:00:19:379 INFO] Starting Server
[2021-12-25 14:00:19:379 INFO] Version 1.18.2.03
[2021-12-25 14:00:19:379 INFO] Session ID 9dca8f86-db12-4667-85a5-1fbd9bd6f8f3
[2021-12-25 14:00:19:380 INFO] Level Name: my_minecraft_world1
[2021-12-25 14:00:19:387 INFO] Game mode: 0 Survival
[2021-12-25 14:00:19:387 INFO] Difficulty: 1 EASY
[2021-12-25 14:00:19:455 INFO] opening worlds/my_minecraft_world1/db
[2021-12-25 14:00:20:347 INFO] IPv4 supported, port: 0
[2021-12-25 14:00:20:347 INFO] IPv6 supported, port: 0
[2021-12-25 14:00:20:373 INFO] Package: com.mojang.minecraft.dedicatedserver
Version: 1.18.2.03
OS: Linux
Server start: 2021-12-25 14:00:19 CET
Dmp timestamp: 2021-12-25 14:00:20 CET
Upload Date: 2021-12-25 14:00:20 CET
Session ID: 9dca8f86-db12-4667-85a5-1fbd9bd6f8f3
Commit hash: 74c6ce6eb10dfe6b481aa14578b375b50a5d2028
Build id: 7966228
CrashReporter Key: 3b0e9a7c-df2a-3539-9e19-562856ad8772Crash
[2021-12-25 14:00:20:373 INFO] 
Failed to open curl lib from binary, use libcurl.so instead
87c02a26-7e2a-45d6-bda4-24fc7ffc70b2 
Comment by Vincent Vermilya [ 07/Dec/21 ]

Weird, I run as a system user without issue but if the ports are used (example: I already have a 2nd server using the same ports) I get the curl lib shared object file error.

Comment by Patrick Mitchell [ 27/Nov/21 ]

Same issue server version 1.17.41.01  on Ubuntu Server 20.04

Please Update ticket to reflect latest server ver still has issue

Initially had libcurl.so error:

NO LOG FILE! - [] setting up server logging...
[2021-11-27 10:32:26:128 INFO] Starting Server
[2021-11-27 10:32:26:128 INFO] Version 1.17.41.01
[2021-11-27 10:32:26:129 INFO] Session ID d5d9a49d-1bff-4735-b56e-a4785e4b4485
[2021-11-27 10:32:26:129 INFO] Level Name: a5BeYHv8BQA
[2021-11-27 10:32:26:152 INFO] Game mode: 1 Creative
[2021-11-27 10:32:26:152 INFO] Difficulty: 1 EASY
[INFO] opening worlds/a5BeYHv8BQA/db
[INFO] IPv4 supported, port: 0
[INFO] IPv6 supported, port: 0
[INFO] Package: com.mojang.minecraft.dedicatedserver
Version: 1.17.41.01
OS: Linux
Server start: 2021-11-27 10:32:26 UTC
Dmp timestamp: 2021-11-27 10:32:26 UTC
Upload Date: 2021-11-27 10:32:26 UTC
Session ID: d5d9a49d-1bff-4735-b56e-a4785e4b4485
Commit hash: acc2f92abaaeeaac31618942103e410b5305a3fc
Build id: 7568584
CrashReporter Key: baf51ecb-2966-34c3-a742-7d2375a74672Crash
[INFO]
Failed to open curl lib from binary, use libcurl.so instead
2b358c1c-4c4e-449d-8755-f30a866803de

so out of habit tried running with elevated privileges, the server seems to start, with two instances though, as there are two sets of port bindings. But it doesn't crash, and any mention of missing curl missing has disappeared

[INFO] opening worlds/a5BeYHv8BQA/db
[INFO] IPv4 supported, port: 19132
[INFO] IPv6 supported, port: 19133
[INFO] Server started.
[INFO] IPv4 supported, port: 36212
[INFO] IPv6 supported, port: 35954

 

Out of curiosity made sure there was nothing holding onto those ports in netstat using netstat -uplnt | less

--Yeilding--

 Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      752/sshd
tcp        0      0 0.0.0.0:9080            0.0.0.0:*               LISTEN      758/nginx: master p
tcp        0      0 0.0.0.0:443             0.0.0.0:*               LISTEN      758/nginx: master p
tcp        0      0 127.0.0.1:9000          0.0.0.0:*               LISTEN      670/php-fpm: master
tcp        0      0 127.0.0.1:3306          0.0.0.0:*               LISTEN      721/mysqld
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      758/nginx: master p
tcp6       0      0 :::22                   :::*                    LISTEN      752/sshd
tcp6       0      0 :::9090                 :::*                    LISTEN      1/init
tcp6       0      0 :::21                   :::*                    LISTEN      673/vsftpd
tcp6       0      0 :::53                   :::*                    LISTEN      669/coredns
udp        0      0 0.0.0.0:19132           0.0.0.0:*                           1865/./bedrock_serv
udp        0      0 139.180.172.134:68      0.0.0.0:*                           539/systemd-network
udp        0      0 0.0.0.0:41119           0.0.0.0:*                           1865/./bedrock_serv
udp6       0      0 :::54605                :::*                                1865/./bedrock_serv
udp6       0      0 :::19133                :::*                                1865/./bedrock_serv
udp6       0      0 :::53                   :::*                                669/coredns

So Minecraft is binding to these ports whether the server is running correctly or not

 

Annoyingly no mention is made of what version of curl is missing so I installed 

libcurl3
libcurl4
libcurl4-openssl-dev 

And this brought back the original error and stopped it from binding to any ports

 

I then tried manually installing the library from the package

$ mkdir ~/libcurl3 && cd ~/libcurl3
$ apt-get download -o=dir::cache=~/libcurl3 libcurl3
$ ar x libcurl3* data.tar.xz
$ tar xf data.tar.xz
$ cp -L ~/libcurl3/usr/lib/x86_64-linux-gnu/libcurl.so.4 /usr/lib/libcurl.so.3
$ cd && rm -rf ~/libcurl3 

With no luck   I have tried a fresh BDS install and am this close to trying a fresh ubuntu server install 

After trying yoni's solution in relation to ipv6 and a restart im back with a seemingly functional server but am unable to connect with either port the log provides

NO LOG FILE! - [] setting up server logging...
[2021-11-27 11:02:01:714 INFO] Starting Server
[2021-11-27 11:02:01:714 INFO] Version 1.17.41.01
[2021-11-27 11:02:01:714 INFO] Session ID f545d6e1-606a-4af0-8c23-0f536ff53c95
[2021-11-27 11:02:01:716 INFO] Level Name: a5BeYHv8BQA
[2021-11-27 11:02:01:746 INFO] Game mode: 1 Creative
[2021-11-27 11:02:01:746 INFO] Difficulty: 1 EASY
[INFO] opening worlds/a5BeYHv8BQA/db
[INFO] IPv4 supported, port: 19132
[INFO] IPv6 supported, port: 19133
[INFO] Server started.
[INFO] IPv4 supported, port: 57341
[INFO] IPv6 supported, port: 43746 
Comment by Eoin O'Neill [ 22/Nov/21 ]
NO LOG FILE! - [] setting up server logging...
[2021-11-22 21:43:12:624 INFO] Starting Server
[2021-11-22 21:43:12:624 INFO] Version 1.17.41.01
[2021-11-22 21:43:12:624 INFO] Session ID c116c9d9-9b5c-4977-8f55-6f77d86148d9
[2021-11-22 21:43:12:624 INFO] Level Name: Bedrock level
[2021-11-22 21:43:12:642 INFO] Package: com.mojang.minecraft.dedicatedserver
Version: 1.17.41.01
OS: Linux
Server start: 2021-11-22 21:43:12 UTC
Dmp timestamp: 2021-11-22 21:43:12 UTC
Upload Date: 2021-11-22 21:43:12 UTC
Session ID: c116c9d9-9b5c-4977-8f55-6f77d86148d9
Commit hash: acc2f92abaaeeaac31618942103e410b5305a3fc
Build id: 7568584
CrashReporter Key: 8c4937c1-64cb-3532-a8dc-1deb28f67293Crash
[2021-11-22 21:43:12:642 INFO]  at __libc_start_main (UnknownFile:?)
Failed to open curl lib from binary, use libcurl.so instead
bb699e24-c3bb-4526-b99b-ab7d92818c8a 

Same issue here

Comment by 云梦梦梦子 [ 03/Oct/21 ]

centos8 with “dnf install libcurl”and “shutdown -r now”
but it still...

Comment by 云梦梦梦子 [ 03/Oct/21 ]

NO LOG FILE! - setting up server logging...
[2021-10-03 03:24:52:478 INFO] Starting Server
[2021-10-03 03:24:52:479 INFO] Version 1.17.32.02
[2021-10-03 03:24:52:479 INFO] Session ID f1d748b8-21a3-4000-a731-e9cbf4759d83
[2021-10-03 03:24:52:479 INFO] Level Name: Bedrock level[2021-10-03 03:24:52:561 INFO] Game mode: 0 Survival
[2021-10-03 03:24:52:561 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.17.32.02
OS: Linux
Server start: 2021-10-03 03:24:51 EDT
Dmp timestamp: 2021-10-03 03:24:53 EDT
Upload Date: 2021-10-03 03:24:53 EDT
Session ID: f1d748b8-21a3-4000-a731-e9cbf4759d83
Commit hash: af849e3a59b21dcf3460c88e02b4438405416dcc
Build id: 7338473
CrashReporter Key: 7beff209-51af-3b79-bd52-3d62f18553da

Crash
[INFO]
Failed to open curl lib from binary, use libcurl.so instead
2f5f9bd6-043b-45e3-875c-7dd5b502de28

Comment by Stephen Higgs [ 26/Sep/21 ]

I also ran into this issue:

 

[INFO] IPv4 supported, port: 19132
[INFO] IPv6 supported, port: 19133
[INFO] Server started.
[INFO] IPv4 supported, port: 54090
[INFO] IPv6 supported, port: 34820
[INFO] Package: com.mojang.minecraft.dedicatedserver
Version: 1.17.31.01
OS: Linux
Server start: 2021-09-26 18:05:54 EDT
Dmp timestamp: 2021-09-26 18:07:37 EDT
Upload Date: 2021-09-26 18:07:37 EDT
Session ID: 108c34fc-97b9-4604-9b88-83bcaab40ad7
Commit hash: 2dd5d99c159e01bbcceac2f435589019533d22fa
Build id: 7296126
CrashReporter Key: 7678bd4c-50f4-33f5-b4ce-841d68c48e99Crash
[INFO] 	at clone (UnknownFile:?)
Failed to open curl lib from binary, use libcurl.so instead

Comment by Markus Stein [ 23/Sep/21 ]

I have this again on 1.17.30, but different ports are configured in server.properties. But log shows:

 

[INFO] IPv4 supported, port: 19152
[INFO] IPv6 supported, port: 19153
[INFO] Server started.
[INFO] IPv4 supported, port: 19132
[INFO] IPv6 supported, port: 19133 

So seems it uses default port and the configured one?!?

Comment by Scott Harman [ 21/Jul/21 ]

Yoni's suggestion was a good fix for linux - I've been using ipv6 for ages, and it's only been an issue since updating to the latest build

https://bugs.mojang.com/browse/BDS-12751?focusedCommentId=970916&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-970916

 

Comment by Bill Ewing [ 25/Jun/21 ]

FWIW, this appears to occur when a JSON file is malformed as well. In particular, the whitelist.json file was malformed after a reboot; it is unclear if it was from a user modifying it or from something that may have occurred between the change from 1.16.x or 1.17.1.01 to 1.17.2.01.

Comment by Jens Hoffmann [ 22/Jun/21 ]

Somehow we have the same Error Message → BDS-13806

Comment by Andras Katona [ 14/Jun/21 ]

It's happening with 1.17.0.03 too, but slightly different logging.

[INFO] Package: com.mojang.minecraft.dedicatedserver
Version: 1.17.0.03
OS: Linux
Server start: 2021-06-14 04:00:11 CEST
Dmp timestamp: 2021-06-14 20:30:41 CEST
Upload Date: 2021-06-14 20:30:41 CEST
Session ID: 8c01ce06-c45f-4bc8-884f-6a6f73ae2272
Commit hash: 2dd065fae9ec68c4bad3c4621ec546be5c100416
Build id: 6274177
CrashReporter Key: d210ab83-12c9-38ec-8491-ad409c7bd8ab

Crash
[INFO]  at clone (UnknownFile:?)
Failed to open curl lib from binary, use libcurl.so instead

This is the extra

[INFO]  at clone (UnknownFile:?)

It crashes when I went to the overworld and it tried to load/generate new chunks, I never been there before. Re logged in, re-entered the portal, walked around, tried to load the distance too, crashed again.

Comment by FrankWu [ 12/Jun/21 ]

when i changed the port, it worked! thanks a lot...

Comment by Markus Stein [ 09/Jun/21 ]

Then it would be great if the error message would be more precise... for example "port already in use" or something like that...

Comment by Epic Puppy [ 22/Apr/21 ]

The best way I found to fix this is to change the IPv6 port to be 1 more than the IPv4 port such as 19132 —> 19133

Comment by arfan riyamy [ 15/Apr/21 ]

i have the same error what i did was change the port from 19132 and 19132 to 19232 and 19233 and it worked 

Comment by yoni [ 12/Apr/21 ]

OMG I finally figured it out after 2 weeks!!!

 

So the issue is not with  the Bedrock release they should probably log better! but the issue is with IPV6 support (on a linux server) minecraft is trying to share the port with ipv4 so the fix for this is to tell the actual linux server to not share the connection and force ipv6 to have a dedicated connection this is how you do it

 

  1. as root open /etc/sysctl.conf 
  2. append to the bottom of the file:  net.ipv6.bindv6only=1
  3. save and exit
  4. in the command line type the following in order to commit: sysctl -p 

 

I have tried to disable ipv6 with minecraft and still it didn't work but the above worked for me.

Comment by nierik [ 12/Apr/21 ]

Here we discussed some similar issues: BDS-12695

Comment by nierik [ 12/Apr/21 ]

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.

Comment by Mark Conover [ 11/Apr/21 ]

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)

Comment by Jonah Miller [ 10/Apr/21 ]

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.

Generated at Sat Jan 11 08:00:36 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.