[SERVER-55968] Unable to start mongod daemon after upgrading OS from Ubuntu 16 to 18 Created: 09/Apr/21  Updated: 22/Jun/22  Resolved: 09/Apr/21

Status: Closed
Project: Core Server
Component/s: Build
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Bharath Kumar CM Assignee: Edwin Zhou
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File mongo_log.txt    
Operating System: ALL
Steps To Reproduce:

***Did anyone face similar issues ?
How to fix this issue ?***

Participants:

 Description   

**Unable to start mongod daemon after upgrading OS from Ubuntu 16 to 18**

root@dummy2:~# mongod --version
db version v4.0.4
git version: f288a3bdf201007f3693c58e140056adf8b04839
OpenSSL version: OpenSSL 1.1.1 11 Sep 2018
allocator: tcmalloc
modules: none
build environment:
distmod: ubuntu1804
distarch: x86_64
target_arch: x86_64

root@dummy2:~#
cat /etc/*-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04.4 LTS"
NAME="Ubuntu"
VERSION="18.04.4 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.4 LTS"
VERSION_ID="18.04"

root@dummy2:~# /usr/bin/mongod --config /etc/mongo/db8303/mongodb.conf &
/usr/lib/x86_64-linux-gnu/libcurl.so.4: version `CURL_OPENSSL_3' not found (required by /usr/bin/mongod)

The difference that I'm seeing before and after OS upgrade on libcurl version:

before:

root@dummy2:~# ls -lrt /usr/lib/x86_64-linux-gnu/libcurl*
/usr/lib/x86_64-linux-gnu/libcurl.so.4 -> libcurl.so.4.4.0
/usr/lib/x86_64-linux-gnu/libcurl.so.3 -> libcurl.so.4
/usr/lib/x86_64-linux-gnu/libcurl-gnutls.so.4 -> libcurl-gnutls.so.4.4.0
/usr/lib/x86_64-linux-gnu/libcurl-gnutls.so.3 -> libcurl-gnutls.so.4
/usr/lib/x86_64-linux-gnu/libcurl.so.4.4.0
/usr/lib/x86_64-linux-gnu/libcurl-gnutls.so.4.4.0

After:

root@dummy2:~# ls -lrt /usr/lib/x86_64-linux-gnu/libcurl
/usr/lib/x86_64-linux-gnu/libcurl.so.4 -> libcurl.so.4.5.0
/usr/lib/x86_64-linux-gnu/libcurl-gnutls.so.4 -> libcurl-gnutls.so.4.5.0
/usr/lib/x86_64-linux-gnu/libcurl-gnutls.so.3 -> libcurl-gnutls.so.4
/usr/lib/x86_64-linux-gnu/libcurl.so.4.5.0
/usr/lib/x86_64-linux-gnu/libcurl-gnutls.so.4.5.0

 



 Comments   
Comment by Bharath Kumar CM [ 09/Apr/21 ]

thanks Edwin

Comment by Edwin Zhou [ 09/Apr/21 ]

Hi bharath_achar@outlook.com,

I apologize for being unclear earlier, the log files I was referring to are located in your data directory and are named mongod.log.

We're thrilled to hear you were able to resolve your issue by using the MongoDB distribution for Ubuntu 18.04. Additionally, we do provide distributions for each platform separately. While it may be possible to get our Ubuntu 16.04 distribution working on Ubuntu 18.04, we recommend against doing so. Instead, you can download the corresponding distribution for your operating system for MongoDB v4.0.23 Community here.

Best,
Edwin

Comment by Bharath Kumar CM [ 09/Apr/21 ]

Edwin, I just attached the log; I had also mentioned in the issue description.

I found the solution myself for this issue. 

 

I tried following different options :I tried following different options :
Option1: with Ubuntu-16 mongo binaries (before option3 step2); if we are okay with libcurl3
    1. apt-get remove libcurl4    2. apt-get install libcurl3    3. able to start the daemon

Option2: didn’t work
    1. apt-get remove libcurl4    2. apt-get install libcurl4    3. /etc/init.d/mongo_db7020    /usr/bin/mongod: /usr/lib/x86_64-linux-gnu/libcurl.so.4: version `CURL_OPENSSL_3' not found (required by /usr/bin/mongod) 
Option3: copying mongodb 18 binaries worked
    1. apt-get remove libcurl4    2. rsync -asvh mongoserver:/usr/bin/mongodb-linux-x86_64-ubuntu1804-4.0.4/bin/* /usr/bin/mongodb-linux-x86_64-ubuntu1604-4.0.4/bin    3. apt-get install libcurl4    4. able to start the daemon
Option 1 & 3 worked fine for me.

https://dba.stackexchange.com/questions/289521/unable-to-start-mongod-daemon-after-upgrading-os-from-ubuntu-16-to-18

 

 But I would like to understand this behavior why OS upgrade is causing this issue.

 

Comment by Edwin Zhou [ 09/Apr/21 ]

Hi bharath_achar@outlook.com,

Thanks for reporting this issue. Would you please attach log files which cover your attempts to start mongod and attach it to this ticket?

Kind regards,
Edwin

Generated at Thu Feb 08 05:37:57 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.