Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mysql2 segfault, when using mariadb_user #194

Closed
sinfomicien opened this issue Apr 19, 2018 · 2 comments
Closed

mysql2 segfault, when using mariadb_user #194

sinfomicien opened this issue Apr 19, 2018 · 2 comments
Assignees
Milestone

Comments

@sinfomicien
Copy link
Contributor

A very interesting bug i found yesterday...

If you wanna use mariadb_user, then you need to have the mysql2 gem. We install the gem in the omnibus chef packages... But, we linked it against the system libmariadb.

And here come the magic thing ! Embedded chef use libssl.1.0, libmariadb from my system which use my system ssl lib (libssl1.1).

So each time someone want to install a gem compiled against system library, itself linked to system libssl... He creates a wonderful conflict. If someone has a magic idea to propose here... I will be more than happy to hear :-)

My System is a Debian 9 one. But you can reproduce it in every system which has libssl.1.1 as the base one.

@sinfomicien
Copy link
Contributor Author

I'm not particularly proud of what i will PR, but at least it works !

sinfomicien referenced this issue in sinfomicien/mariadb Apr 20, 2018
Try to install mysql2 and dependencies only in omnibus installation.
sinfomicien referenced this issue in sinfomicien/mariadb Apr 20, 2018
Try to install mysql2 and dependencies only in omnibus installation.
damacus added a commit to sinfomicien/mariadb that referenced this issue May 15, 2018
@sinfomicien sinfomicien self-assigned this May 22, 2018
sinfomicien added a commit to sinfomicien/mariadb that referenced this issue May 22, 2018
@sinfomicien sinfomicien modified the milestones: 1.6.0, 1.5.4 May 22, 2018
@lock
Copy link

lock bot commented May 24, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators May 24, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant