Red Hat Bugzilla – Bug 973843
mongo client lookup error
Last modified: 2014-10-01 07:43:28 EDT
Created attachment 760337 [details] strace mongo 2>mongo.strace Description of problem: mongo client tells: mongo: symbol lookup error: mongo: undefined symbol: _ZN2v86LockerC1EPNS_7IsolateE Version-Release number of selected component (if applicable): 2.2.4 How reproducible: always Steps to Reproduce: 1. run "mongo" from terminal 2. no connection to mongo 3. Actual results: [patachou@patrice-desktop-home ~]$ mongo MongoDB shell version: 2.2.4 mongo: symbol lookup error: mongo: undefined symbol: _ZN2v86LockerC1EPNS_7IsolateE Expected results: a mongo shell Additional info: This append after some yum updates. I'm unable to tell when it crashes first. At first I had some segfault, I decided to do "yum reinstall" on mongodb and mongodb-server. Now, the error is a symbol lookup error. I restarted mongoserver, resintall libmongodb... etc... mongoimport, mongoexport, mongodump etc... works as expected, but the mongo command crashes... and it's very problematic because I have lot of request to do. I give the strace
I had the same problem. Solved it by removing chromium from spots repository. The v8 library provided by fedora-chromium repo seems to be incompatible with the libmongodb.
OK, I recompiled the sRPM and it works. @Sebastian This may be the problem. Maybe I must contact chromium packager so
Happens on Fedora 19 as well
I did remove chromium, chromium-ffmpegsumo, v8, v8-devel and then try to use 'mongo' it did work perfectly. After that I thought to try installing chromium which of course brings all the dependencies of v8, etc and then 'mongo' stopped working on my Fedora 19.
Also happens with mongodb-2.4.6 on Fedora 19
As the comment 4(In reply to Ankit Patel from comment #4) The problem is there are two v8 libraries from fedora repo (3.14.5.10-2.fc19) and from fedora-chromium (3.17.6.14-2.fc19) repo.
(In reply to Juan P. Daza P. from comment #6) > As the comment 4(In reply to Ankit Patel from comment #4) > > The problem is there are two v8 libraries from fedora repo > (3.14.5.10-2.fc19) and from fedora-chromium (3.17.6.14-2.fc19) repo. on Fedora 19 for me works after downgrade v8 to 3.14.5.10-2.fc19 and remove chromium.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Bumping to F20 as this is still a problem with F20
Is this bug still actual? (it is quite old) If yes, please reopen... I closed this bug because now it's working for me well with Spot's repo https://repos.fedorapeople.org/repos/spot/chromium-stable/ . V8 library from this repo hes been renamed (chromium-v8 package - libcv8.so library), so it doesn't conflict...