#50778 closed defect (fixed)
mongodb @3.2.3_0 start error _SSLv2_client_method
Reported by: | whurley@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.3.4 |
Keywords: | Cc: | ryandesign (Ryan Carsten Schmidt) | |
Port: | mongodb |
Description
After updating to mongodb @3.2.3 and openssl @1.0.2g_0 the following error occurs when attempting to run mongod:
dyld: Symbol not found: _SSLv2_client_method Referenced from: /opt/local/bin/mongod Expected in: /opt/local/lib/libssl.1.0.0.dylib in /opt/local/bin/mongod Trace/BPT trap: 5
Change History (8)
comment:1 Changed 9 years ago by wlipa (Bill Lipa)
comment:2 Changed 9 years ago by ShaharHD (Shahar Hadas)
mongodb is built requiring SSLv2.
is it possible to fix it on the port level? or this needs to be addressed with MongoDB code?
comment:3 follow-up: 4 Changed 9 years ago by dbevans (David B. Evans)
Rebuilding mongodb should fix the problem. Try
sudo port -n upgrade --force mongodb
to confirm.
comment:4 Changed 9 years ago by ShaharHD (Shahar Hadas)
Rebuilding was the 1st thing I tried. When it didn't work, I uninstalled mongodb and reinstalled - and that didn't help either.
comment:5 Changed 9 years ago by dbevans (David B. Evans)
I think you're just getting the prebuilt binary from our server rather than actually rebuilding. I'm doing a local rebuild now and will commit a fix as soon as I confirm the results.
comment:6 Changed 9 years ago by dbevans (David B. Evans)
If you want to rebuild from source in the meantime, the corrent command would be (-s
for source):
sudo port -ns upgrade --force mongodb
comment:7 Changed 9 years ago by dbevans (David B. Evans)
Cc: | ryandesign@… added |
---|---|
Keywords: | mongodb openssl removed |
Resolution: | → fixed |
Status: | new → closed |
Fix committed in r146273, revision incremented to rebuild mongodb with openssl 1.0.2g. The buildbots are backed up right now so it may take a few hours before a new binary image is available.
comment:8 Changed 9 years ago by whurley@…
Also want to confirm that building from source resolved the issue.
The ruby2.2 port has a similar problem.