Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


EasyApache 4 Error
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

EasyApache 4 Error

Hi,
I'm getting following error while provisioning any EA profile. Already tried to update yum, rebuild rpms and updating cpanel. None of them resolving the issue.

Update Error:

Error: Package: ea-apache24-tools-2.4.33-5.5.1.cpanel.x86_64 (EA4)
Requires: libssl.so.1.0.0()(64bit)
Available: ea-openssl-1.0.2n-3.3.1.cpanel.x86_64 (EA4)
libssl.so.1.0.0()(64bit)
Available: ea-openssl-1.0.2o-1.1.1.cpanel.x86_64 (EA4)
libssl.so.1.0.0()(64bit)

Comments

  • ClouviderClouvider Member, Patron Provider

    Whoever sold you cPanel is responsible for supporting this.

  • Clouvider said: Whoever sold you cPanel is responsible for supporting this

    Just wanted to know if there is an easy fix before contacting cPanel.

  • ClouviderClouvider Member, Patron Provider

    cPanel partner if you bought through the partner or cPanel if you bought directly.

    It looks like a dependency issue in the repo assuming you didn't do any custom non-repo rpms that could cause grief.

  • Clouvider said: It looks like a dependency issue in the repo assuming you didn't do any custom non-repo rpms that could cause grief.

    There were some leftover rpms from cloudlinux. But unable to replace it centos one without breaking server. Had to reinstall server from backup.

  • ClouviderClouvider Member, Patron Provider

    Hence why you should have contacted the support - they have the right RPMs and know the background story behind it and as could have forced the installation of the right packages with an appropriate switch.

    I'd never accepted this resolution on a production server frankly.

  • Clouvider said: Hence why you should have contacted the support - they have the right RPMs and know the background story behind it and as could have forced the installation of the right packages with an appropriate switch.

    They were the ones who told me they are not comfortable uninstalling the cloudlinux rpms and switch to centos as it would break the server.

    It was a production server. As apache was already down and the clock was ticking. I had to act fast so deployed a new server and migrated the accounts to that. Now reinstalling old one.

  • ClouviderClouvider Member, Patron Provider
    edited April 2018

    Escalation should be requested - they have team specialising in Cloud Linux including they have Cloud Linux employed support guys working on their helpdesk for resolving CL related issues - that's why support should have been requested by the license provider - it would skip straight to the high tier partner queue. Them being not comfortable is not really an excuse that should fly ;-).

    Again, Apache being down on production, on the partner support qualifies as emergency support with a skilled engineer attending the ticket immediately with an option for a phone call.

Sign In or Register to comment.