Skip to main content

Apache Service Won't Start after EA3 to EA4 Migration

pschlenker
After running the EA3 to EA4 migration script, the Apache service won't start. When I run the command "service httpd start", the operation fails because the script is looking for the Apache binaries in /usr/local/apache, but that directory no longer exists. After running the migration script, the only apache directories I see in /usr/local/ is: /usr/local/apache.backup /usr/local/apache.backup_archive/ /usr/local/apache.backup.ea3/ According to the installation instructions, when EasyApache is migrated, the /usr/local/apache directory is supposed to be moved to the /usr/local/apache.3 directory, but there is no apache.3 directory in /usr/local/ after the migration completes. I received several warnings during the migration, but it's hard to tell if those warning mean that the migration was erroring out, or if they were just normal warnings. Unfortunately, I can't remember exactly what the warnings were. I don't want to run the migration again to make note of the warnings because it will bring our website down. I ran the command to revert EasyApache to EA3, and the script ran without issue. After reverting back to EA3, the Apache service started without issue, and I see the "apache" directory in /usr/local/ once again. Here is my system information: /etc/redhat-release:CentOS release 6.6 (Final) /usr/local/cpanel/version:11.60.0.34 /var/cpanel/envtype:virtuozzo CPANEL=release Server version: Apache/2.4.25 (Unix) Server built: Jan 14 2017 11:06:39 Cpanel::Easy::Apache v3.34.10 rev9999 PHP 5.6.29 (cli) (built: Jan 14 2017 14:12:31) Copyright (c) 1997-2016 The PHP Group Zend Engine v2.6.0, Copyright (c) 1998-2016 Zend Technologies mysql Ver 14.14 Distrib 5.5.52, for Linux (x86_64) using readline 5.1

Comments

6 comments

Date Votes
  • cPanelMichael
    Hello, Could you open a support ticket using the link in my signature so we can take a closer look and see what happened? You can post the ticket number here so we can update this thread with the outcome. Thank you.
    0
  • gfornes
    Good Morning!!. I got the the same problem when I was Migrating form EA3 to EA4. When I run system Update I get this error: --> Finished Dependency Resolution Error: Package: 32:bind-chroot-9.8.2-0.30.rc1.el6_6.2.x86_64 (@updates) Requires: bind = 32:9.8.2-0.30.rc1.el6_6.2 Removing: 32:bind-9.8.2-0.30.rc1.el6_6.2.x86_64 (@updates) bind = 32:9.8.2-0.30.rc1.el6_6.2 Updated By: 32:bind-9.8.2-0.47.rc1.el6_8.4.x86_64 (updates) bind = 32:9.8.2-0.47.rc1.el6_8.4 Available: 32:bind-9.8.2-0.47.rc1.el6.x86_64 (base) bind = 32:9.8.2-0.47.rc1.el6 Available: 32:bind-9.8.2-0.47.rc1.el6_8.1.x86_64 (updates) bind = 32:9.8.2-0.47.rc1.el6_8.1 Available: 32:bind-9.8.2-0.47.rc1.el6_8.2.x86_64 (updates) bind = 32:9.8.2-0.47.rc1.el6_8.2 Available: 32:bind-9.8.2-0.47.rc1.el6_8.3.x86_64 (updates) bind = 32:9.8.2-0.47.rc1.el6_8.3 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest -- error(11928) -- yum exited 256 -- /error(11928) --
    My Ticket ID is: 8158587 I'd aprecciate if you could help my.
    0
  • cPanelMichael
    My Ticket ID is: 8158587

    Hello, To update, it looks like this was the result of unsupported bind-chroot packages installed on the system. Removing those packages allowed YUM to update successfully, which then allowed for a successful EasyApache 4 conversion. Thank you.
    0
  • golden_eyes
    Hi, I have the same problem in my 3 servers, below is the log of one of them:
    [root@nava ~]# yum update Loaded plugins: fastestmirror, tsflags, universal-hooks Setting up Update Process Loading mirror speeds from cached hostfile * EA4: 85.13.201.2 * cpanel-addons-production-feed: 85.13.201.2 * base: centos.mirrors.ovh.net * extras: centos.mirrors.ovh.net * updates: centos.mirrors.ovh.net Resolving Dependencies --> Running transaction check ---> Package bind.x86_64 32:9.8.2-0.47.rc1.el6_8.2 will be updated --> Processing Dependency: bind = 32:9.8.2-0.47.rc1.el6_8.2 for package: 32:bind-chroot-9.8.2-0.47.rc1.el6_8.2.x86_64 ---> Package bind.x86_64 32:9.8.2-0.62.rc1.el6_9.4 will be an update --> Processing Dependency: portreserve for package: 32:bind-9.8.2-0.62.rc1.el6_9.4.x86_64 ---> Package bind-devel.x86_64 32:9.8.2-0.47.rc1.el6_8.2 will be updated ---> Package bind-devel.x86_64 32:9.8.2-0.62.rc1.el6_9.4 will be an update ---> Package bind-libs.x86_64 32:9.8.2-0.47.rc1.el6_8.2 will be updated ---> Package bind-libs.x86_64 32:9.8.2-0.62.rc1.el6_9.4 will be an update ---> Package bind-utils.x86_64 32:9.8.2-0.47.rc1.el6_8.2 will be updated ---> Package bind-utils.x86_64 32:9.8.2-0.62.rc1.el6_9.4 will be an update --> Running transaction check ---> Package bind.x86_64 32:9.8.2-0.47.rc1.el6_8.2 will be updated --> Processing Dependency: bind = 32:9.8.2-0.47.rc1.el6_8.2 for package: 32:bind-chroot-9.8.2-0.47.rc1.el6_8.2.x86_64 ---> Package portreserve.x86_64 0:0.0.4-11.el6 will be installed --> Finished Dependency Resolution Error: Package: 32:bind-chroot-9.8.2-0.47.rc1.el6_8.2.x86_64 (@updates) Requires: bind = 32:9.8.2-0.47.rc1.el6_8.2 Removing: 32:bind-9.8.2-0.47.rc1.el6_8.2.x86_64 (@updates) bind = 32:9.8.2-0.47.rc1.el6_8.2 Updated By: 32:bind-9.8.2-0.62.rc1.el6_9.4.x86_64 (updates) bind = 32:9.8.2-0.62.rc1.el6_9.4 Available: 32:bind-9.8.2-0.62.rc1.el6.x86_64 (base) bind = 32:9.8.2-0.62.rc1.el6 Available: 32:bind-9.8.2-0.62.rc1.el6_9.1.x86_64 (updates) bind = 32:9.8.2-0.62.rc1.el6_9.1 Available: 32:bind-9.8.2-0.62.rc1.el6_9.2.x86_64 (updates) bind = 32:9.8.2-0.62.rc1.el6_9.2 You could try using --skip-broken to work around the problem ** Found 1 pre-existing rpmdb problem(s), 'yum check' output follows: 32:bind-9.8.2-0.47.rc1.el6_8.2.x86_64 has missing requires of portreserve [root@nava ~]# rpm -e --justdb --nodeps 32:bind-chroot-9.8.2-0.47.rc1.el6_8.2.x86_64 error: package 32:bind-chroot-9.8.2-0.47.rc1.el6_8.2.x86_64 is not installed
    How do I solve it? Best Regards
    0
  • sysdop
    @golden_eyes The bind-chroot is leaving you as it is not necessary. You can remove it by running the command yum remove bind-chroot -y and without any problem and this automatically solves your problem, then you run yum clean all and again yum upgrade.
    0
  • cPanelMichael
    Hello, Here's a post with an example of how to remove the bind-chroot RPM: Updating Kernel Version Thank you.
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post