[SERVER-20259] Support for OpenSuSE tumbleweed Created: 02/Sep/15 Updated: 08/Nov/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Admin |
| Affects Version/s: | 3.0.5, 3.0.6 |
| Fix Version/s: | features we're not sure of |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Cesar Izurieta Hidalgo | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | platform-request | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Build
|
||||||||
| Operating System: | ALL | ||||||||
| Steps To Reproduce: |
|
||||||||
| Participants: | |||||||||
| Description |
|
After upgrading from 3.0.4 to 3.0.5 or 3.0.6 from the mongodb repositories mongod fails with the following message:
Seems to be related to openssl. These packages are present on my system:
|
| Comments |
| Comment by Cesar Izurieta Hidalgo [ 04/Sep/15 ] | |||||
|
Actually running like this works:
The same thing for the mongo executable. It seems now that the problem is on how openssl and libcrypto are packaged for openSuSE as that libcrypto.so is provided by libopenssl-devel-1.0.2d-1.1.x86_64. Finally the solution was to do the following. I do not recommend it but it might work for some people:
After that mongod and mongo load correctly. | |||||
| Comment by Cesar Izurieta Hidalgo [ 04/Sep/15 ] | |||||
|
Maybe it would be good to limit the versions on the rpm spec file so that >= 3.0.5 requires openssl < 1. That way it wont auto-update on openSuSE systems (or any other system that updates their openssl version). Right now the dependency seems to be declared as "openssl" without version constraints (see https://github.com/mongodb/mongo/blob/master/rpm/mongodb-org.spec#L38). | |||||
| Comment by Ernie Hershey [ 04/Sep/15 ] | |||||
|
Hi cesarizu - I'm sorry you're having this problem. I believe as a result of 1) Upgrade/downgrade OpenSSL to match a SLES environment. Here are the SSL packages in place in our build environment:
2) Use our legacy binaries, which don't support SSL (available here) |