# proxysql-1.4.5-1.1.el7.x86\_64 requires openssl-1.0.2

**URL:** <https://forums.percona.com/t/proxysql-1-4-5-1-1-el7-x86-64-requires-openssl-1-0-2/6205>\
**Category:** Other Tools\
**Created:** [February 20, 2018, 5:09pm UTC](https://forums.percona.com/t/proxysql-1-4-5-1-1-el7-x86-64-requires-openssl-1-0-2/6205 "2018-02-20T17:09:29Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![jakem](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/jakem/32/1215_2.png) [@jakem](https://forums.percona.com/u/jakem)\
**Post date:** [February 20, 2018, 5:09pm UTC](https://forums.percona.com/t/proxysql-1-4-5-1-1-el7-x86-64-requires-openssl-1-0-2/6205/1 "2018-02-20T17:09:29Z")

</div>

proxysql-1.4.5-1.1.el7.x86\_64 won’t install from the percona repo on RHEL7 systems. It seems to require openssl-1.0.2, but RHEL7 has only openssl-1.0.1.

proxysql-1.4.3-1.1.el7.x86\_64 installs fine on the same system, so this is a regression.

# yum install proxysql-1.4.5

Loaded plugins: priorities, product-id, search-disabled-repos  
4 packages excluded due to repository priority protections  
Resolving Dependencies  
 → Running transaction check  
—\> Package proxysql.x86\_64 0:1.4.5-1.1.el7 will be installed  
 → Processing Dependency: libcrypto.so.10(OPENSSL\_1.0.2)(64bit) for package: proxysql-1.4.5-1.1.el7.x86\_64  
 → Finished Dependency Resolution  
Error: Package: proxysql-1.4.5-1.1.el7.x86\_64 (percona)  
Requires: libcrypto.so.10(OPENSSL\_1.0.2)(64bit)  
You could try using --skip-broken to work around the problem  
You could try running: rpm -Va --nofiles --nodigest

---

<div class="post-metadata">

**Author:** ![jakem](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/jakem/32/1215_2.png) [@jakem](https://forums.percona.com/u/jakem)\
**Post date:** [February 21, 2018, 10:37am UTC](https://forums.percona.com/t/proxysql-1-4-5-1-1-el7-x86-64-requires-openssl-1-0-2/6205/2 "2018-02-21T10:37:36Z")

</div>

… although maybe since 1.4.6 is out now, don’t bother fixing 1.4.5 and just instead roll the fix out with a 1.4.6 package? 🙂

---

<div class="post-metadata">

**Author:** ![lorraine.pocklington](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/lorraine.pocklington/32/37_2.png) [@lorraine.pocklington](https://forums.percona.com/u/lorraine.pocklington)\
**Post date:** [February 21, 2018, 10:58am UTC](https://forums.percona.com/t/proxysql-1-4-5-1-1-el7-x86-64-requires-openssl-1-0-2/6205/3 "2018-02-21T10:58:15Z")

</div>

Hi there jakem  
I’ve asked the team about this one, they think you should be able to update OPENSSL on RHEL7 to 1.0.2, and then the install should work for you.

---

<div class="post-metadata">

**Author:** ![jakem](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/jakem/32/1215_2.png) [@jakem](https://forums.percona.com/u/jakem)\
**Post date:** [February 21, 2018, 3:59pm UTC](https://forums.percona.com/t/proxysql-1-4-5-1-1-el7-x86-64-requires-openssl-1-0-2/6205/4 "2018-02-21T15:59:01Z")

</div>

The newest openssl from Red Hat for RHEL7 is 1.0.1e-60.el7.

Can you advise what 1.0.2 packages the team is building off of? And where they got them from?

---

<div class="post-metadata">

**Author:** ![jakem](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/jakem/32/1215_2.png) [@jakem](https://forums.percona.com/u/jakem)\
**Post date:** [February 26, 2018, 12:02pm UTC](https://forums.percona.com/t/proxysql-1-4-5-1-1-el7-x86-64-requires-openssl-1-0-2/6205/5 "2018-02-26T12:02:34Z")

</div>

Sorry, I’m wrong. My repo mirror was busted. There are indeed newer openssl’s available for RHEL7. ☹

---

<div class="post-metadata">

**Author:** ![lorraine.pocklington](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/lorraine.pocklington/32/37_2.png) [@lorraine.pocklington](https://forums.percona.com/u/lorraine.pocklington)\
**Post date:** [February 26, 2018, 12:11pm UTC](https://forums.percona.com/t/proxysql-1-4-5-1-1-el7-x86-64-requires-openssl-1-0-2/6205/6 "2018-02-26T12:11:03Z")

</div>

Hey Jakem, thanks for updating me. I was going to chase down our release engineer today to check, so I appreciate that you let us know.  
No problem at all, either, it’s best to check these things.  
If you have any problems going forward don’t hesitate to ask.
