Hiya, I’m migrating my Meteor 2.16 app to Meteor 3.1. I’ve performed the migration but when I try to run the app I see this error:
/home/username/.meteor/packages/meteor-tool/.3.1.0.tsf1gs.dtdj++os.linux.x86_64+web.browser+web.browser.legacy+web.cordova/mt-os.linux.x86_64/dev_bundle/mongodb/bin/mongod:
error while loading shared libraries: libcrypto.so.3: cannot open shared object file: No such file or directory
Unexpected mongo exit code 127. Restarting.
I’ve read various posts about this error but am pretty confused… if it’s required for mongo, wouldn’t it be part of the Meteor system? And the instructions I’ve seen for adding it seem unclear to me.
I tried upgrading openssl via update manager, which seems to have added libcrypto.so.3 but has not solved the problem.
I think this worked because now have a different error! Unfortunately the new error is for libc and it seems that there is no newer version supported for Mint 20. It looks like I’ll need to upgrade my machine to a newer Linux in order to run Meteor 3, which is understandable but makes the whole thing even more of A Giant Project…
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34’ not found
In the scheme of things, Linux Mint 20 is supported until April 2025. I suggest upgrading to the recent LTS OS first before upgrading Meteor. That can lessen the headaches than upgrading both at the same time.
Hindsight is wonderful… I started the upgrade process without realising that my OS wasn’t supported.
I see the same problem has been reported (and fixed) before: v3 alpha release builds require glibc version change · Issue #12790 · meteor/meteor · GitHub so I’m not the first person to stumble over this… I agree that April 2025 is closer than it was, but I think it’s fair to call this a bug.
Previously, I advocated using Rocky Linux 8 to compile the builds for Meteor because it is supported until 2029 if I remember correctly. It is using glibc 2.28
…which should have supported Ubuntu 20’s glibc 2.31