• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Resolved Plesk Onyx & CentOS 7.4 compatible?

thank you for your reply
yes i reinstalled it and now i have failure stating apache and thereafter PHP services!

Code:
systemctl status httpd.service
● httpd.service - The Apache HTTP Server
   Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor preset: disabled)
  Drop-In: /usr/lib/systemd/system/httpd.service.d
           └─limit_nofile.conf
   Active: failed (Result: exit-code) since Wed 2017-09-20 19:47:53 +0430; 3min 15s ago
     Docs: man:httpd(8)
           man:apachectl(8)
  Process: 31888 ExecStop=/bin/kill -WINCH ${MAINPID} (code=exited, status=1/FAILURE)
  Process: 31886 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=exited, status=1/FAILURE)
 Main PID: 31886 (code=exited, status=1/FAILURE)

Sep 20 19:47:53 srv38715.screweb.com httpd[31886]: (13)Permission denied: AH00072: make_sock: could not bind to address [::]:7080
Sep 20 19:47:53 srv38715.screweb.com httpd[31886]: (13)Permission denied: AH00072: make_sock: could not bind to address 0.0.0.0:7080
Sep 20 19:47:53 srv38715.screweb.com httpd[31886]: no listening sockets available, shutting down
Sep 20 19:47:53 srv38715.screweb.com httpd[31886]: AH00015: Unable to open logs
Sep 20 19:47:53 srv38715.screweb.com systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE
Sep 20 19:47:53 srv38715.screweb.com systemd[1]: httpd.service: control process exited, code=exited status=1
Sep 20 19:47:53 srv38715.screweb.com kill[31888]: kill: cannot find process ""
Sep 20 19:47:53 srv38715.screweb.com systemd[1]: Failed to start The Apache HTTP Server.
Sep 20 19:47:53 srv38715.screweb.com systemd[1]: Unit httpd.service entered failed state.
Sep 20 19:47:53 srv38715.screweb.com systemd[1]: httpd.service failed.

Please help me because all of my websites are down now!Yum does not work and all my websites error:
502 Bad Gateway
nginx

Looks to me like the there is something blocking it, have you tried the following?

# plesk repair web
and/or
# plesk repair installation

Plesk Repair Utility: Installation
 
Usually, we do not experience any significant issue with Centos updates, however, I would recommend to wait until we will pass all integration tests on CentOS 7.4 and announce it officially. I expect this on September 25

I updated one of the servers which had 'yum update' issues to Onyx 17.5.3#23, but the update issues didn't change much!
Code:
[root@*** ***.***.eu]# yum update
Loaded plugins: fastestmirror, langpacks
PLESK_17_5_3-extras                                                                                                                  | 2.9 kB  00:00:00
PLESK_17_PHP52                                                                                                                       | 2.9 kB  00:00:00
PLESK_17_PHP53                                                                                                                       | 2.9 kB  00:00:00
PLESK_17_PHP54                                                                                                                       | 2.9 kB  00:00:00
PLESK_17_PHP55                                                                                                                       | 2.9 kB  00:00:00
PLESK_17_PHP56                                                                                                                       | 2.9 kB  00:00:00
PLESK_17_PHP70                                                                                                                       | 2.9 kB  00:00:00
PLESK_17_PHP71                                                                                                                       | 2.9 kB  00:00:00
base                                                                                                                                 | 3.6 kB  00:00:00
extras                                                                                                                               | 3.4 kB  00:00:00
plesk-migrator                                                                                                                       | 2.9 kB  00:00:00
plesk-migrator-tp                                                                                                                    | 2.9 kB  00:00:00
updates                                                                                                                              | 3.4 kB  00:00:00
++++++++++++++++++++++++++++++++++++++++++++ CUT ++++++++++++++++++++++++++++++++++++++++++++
Determining fastest mirrors
 * base: centos.mirror.transip.nl
 * extras: centos.mirror.transip.nl
 * updates: centos.mirror.transip.nl
Resolving Dependencies
++++++++++++++++++++++++++++++++++++++++++++ CUT ++++++++++++++++++++++++++++++++++++++++++++
--> Finished Dependency Resolution
Error: Package: abrt-addon-pstoreoops-2.1.11-45.el7.centos.x86_64 (@base)
           Requires: abrt = 2.1.11-45.el7.centos
           Removing: abrt-2.1.11-45.el7.centos.x86_64 (@base)
               abrt = 2.1.11-45.el7.centos
           Updated By: abrt-2.1.11-48.el7.centos.x86_64 (base)
               abrt = 2.1.11-48.el7.centos
Error: Package: abrt-addon-vmcore-2.1.11-45.el7.centos.x86_64 (@base)
           Requires: abrt = 2.1.11-45.el7.centos
           Removing: abrt-2.1.11-45.el7.centos.x86_64 (@base)
               abrt = 2.1.11-45.el7.centos
           Updated By: abrt-2.1.11-48.el7.centos.x86_64 (base)
               abrt = 2.1.11-48.el7.centos
Error: kernel conflicts with kexec-tools-2.0.7-50.el7.x86_64
Error: Package: abrt-addon-ccpp-2.1.11-45.el7.centos.x86_64 (@base)
           Requires: abrt = 2.1.11-45.el7.centos
           Removing: abrt-2.1.11-45.el7.centos.x86_64 (@base)
               abrt = 2.1.11-45.el7.centos
           Updated By: abrt-2.1.11-48.el7.centos.x86_64 (base)
               abrt = 2.1.11-48.el7.centos
Error: Package: 1:NetworkManager-1.4.0-20.el7_3.x86_64 (@updates)
           Requires: NetworkManager-libnm(x86-64) = 1:1.4.0-20.el7_3
           Installed: 1:NetworkManager-libnm-1.8.0-9.el7.x86_64 (@base)
               NetworkManager-libnm(x86-64) = 1:1.8.0-9.el7
Error: Package: glibc-devel-2.17-157.el7_3.4.x86_64 (@updates)
           Requires: glibc-headers = 2.17-157.el7_3.4
           Removing: glibc-headers-2.17-157.el7_3.4.x86_64 (@updates)
               glibc-headers = 2.17-157.el7_3.4
           Updated By: glibc-headers-2.17-196.el7.x86_64 (base)
               glibc-headers = 2.17-196.el7
Error: Package: abrt-addon-xorg-2.1.11-45.el7.centos.x86_64 (@base)
           Requires: abrt = 2.1.11-45.el7.centos
           Removing: abrt-2.1.11-45.el7.centos.x86_64 (@base)
               abrt = 2.1.11-45.el7.centos
           Updated By: abrt-2.1.11-48.el7.centos.x86_64 (base)
               abrt = 2.1.11-48.el7.centos
Error: Package: abrt-addon-kerneloops-2.1.11-45.el7.centos.x86_64 (@base)
           Requires: abrt = 2.1.11-45.el7.centos
           Removing: abrt-2.1.11-45.el7.centos.x86_64 (@base)
               abrt = 2.1.11-45.el7.centos
           Updated By: abrt-2.1.11-48.el7.centos.x86_64 (base)
               abrt = 2.1.11-48.el7.centos
 You could try using --skip-broken to work around the problem
** Found 91 pre-existing rpmdb problem(s), 'yum check' output follows:
++++++++++++++++++++++++++++++++++++++++++++ CUT ++++++++++++++++++++++++++++++++++++++++++++

What could be causing it and how to solve?
 
I updated one of the servers which had 'yum update' issues to Onyx 17.5.3#23, but the update issues didn't change much!

What could be causing it and how to solve?

I did a full reinstall of CentOS but then the new version and reinstalled plesk. Didnt find a way to fix it, sorry
 
Ok, I have solved the updating issues. (for my specific case, but this might be useful for someone else).

package-cleanup --cleandupes bumped into an issue with NetworkManager. Apparently, 2 versions were installed, which was probably caused by the premature update to CentOS 7.4 before Plesk was ready.

The older 1.4.0 version didn’t have any dependent applications, so I removed it manually.

Ran package-cleanup --cleandupes again which solved a lot of duplicates.

This cleared a lot of dependency-issues. That leaves the grub2-tools issue.

Code:
Removing grub2-tools.x86_64 1:2.02-0.44.el7.centos - od due to obsoletes from installed 1:grub2-tools-extra-2.02-0.64.el7.centos.x86_64
--> Restarting Dependency Resolution with new changes.
--> Running transaction check
---> Package grub2-tools.x86_64 1:2.02-0.44.el7.centos will be obsoleted
--> Finished Dependency Resolution
Error:  Multilib version problems found. This often means that the root
       cause is something else and multilib version checking is just
       pointing out that there is a problem. Eg.:
   
         1. You have an upgrade for grub2-tools which is missing some
            dependency that another package requires. Yum is trying to
            solve this by installing an older version of grub2-tools of the
            different architecture. If you exclude the bad architecture
            yum will tell you what the root cause is (which package
            requires what). You can try redoing the upgrade with
            --exclude grub2-tools.otherarch ... this should give you an error
            message showing the root cause of the problem.
   
         2. You have multiple architectures of grub2-tools installed, but
            yum can only see an upgrade for one of those architectures.
            If you don't want/need both architectures anymore then you
            can remove the one with the missing update and everything
            will work.
   
         3. You have duplicate versions of grub2-tools installed already.
            You can use "yum check" to get yum show these errors.
   
       ...you can also use --setopt=protected_multilib=false to remove
       this checking, however this is almost never the correct thing to
       do as something else is very likely to go wrong (often causing
       much more problems).
   
       Protected multilib versions: 1:grub2-tools-2.02-0.64.el7.centos.x86_64 != 1:grub2-tools-2.02-0.44.el7.centos.x86_64

The way I solved the grub2-tools issue might not have been the recommended/cleanest way, but it worked.

grub2-tools-2.02-0.44.el7.centos.x86_64 was a dependency for 3 other packages, which were dependencies of others. The ‘grub2’-packages were all the new version (2.02-0.64.el7), only grub2-tools was older.

So after backing up the server to be prepared for a quick reinstall, I removed the package by executing
Code:
sudo rpm -e —nodeps grub2-tools-2.02-0.44.el7.centos.x86_64
followed by
Code:
sudo yum -y install grub2-tools

After this all dependency-issues which showed up during yum update were gone and all packages were updated the way the should.

Next time I'll wait for Plesk to be ready for the next OS update and hope it doesn't install conflicting system updates by itself.
 
Last edited:
Next time I'll wait for Plesk to be ready for the next OS update and hope it doesn't install conflicting system updates by itself.

Automatic updates shouldn't really be enabled at all on a productive environment. You never know what's going on. Do it manually and be safe with knowing all related aspects.
 
A word of caution to any users Plesk users upgrading to Centos 7.4 on DIgitalocean. Your droplet will lose network connectivity after the upgrade to 7.4 if its networking is using their new cloud-init scripts. It seems that their cloud-init scripts don't work properly with Centos 7.4 which causes the default gateway not to be set properly after reboot. I had to fix this for a few people now.

I'd really appreciate your assistance.
Can you tell me how you restored the default route? I've lost network connectivity on one droplet after upgrading to 7.4 then rebooting. And on another, although it is working and has network connectivity and has been rebooted, there doesn't appear to be a default route set :-(

Thanks,

Faris.

EDIT:
This seems to have done the trick:
# ip route add default via $gateway-ip
But was that the correct thing to do?

EDIT2: But I don't know how to make cloud-init, which is the real problem, add the correct default route persistently. Your advice would be appreciated.
 
Last edited:
> add the correct default route persistently.

Just add the gateway parameter to /etc/sysconfig/network

Code:
GATEWAY=<yourgatewayipaddres>
That should make it persistent for your devices
 
> add the correct default route persistently.

Just add the gateway parameter to /etc/sysconfig/network

Code:
GATEWAY=<yourgatewayipaddres>
That should make it persistent for your devices

That's really cool. Thanks Danami.

DO suggested adding the ip route add (etc) to rc.local. This does work (as long as you chmod +x), but as it runs AFTER pretty much everything else on boot, certain things are not happy - e.g. ntpd cannot get the correct time and the hardware clock is one hour off, so you end up with oddities in the log until ntpd checks again a little later on.

Without your hint (and without Google helping me find it) I would have been totally lost on this. It just didn't occur to me to look for a missing default gateway. I just could not figure out what was wrong. You saved me a great deal of hassle and hair loss! Thank you again.
 
> Without your hint (and without Google helping me find it) I would have been totally lost on this. It just didn't occur to me to look for a missing default gateway. I just could not figure out what was wrong. You saved me a great deal of hassle and hair loss! Thank you again.

Don't worry it took me a bit to figure out also. I'm not that familiar with DO's cloudinit scripts but I wish they would fix them. When I asked DO support they told me not to run dist updates. The tech didn't understand that new OS point versions get pushed via "yum update" only on Centos :(

I can confirm that I haven't had any issues on OVH VMs and they use the same cloud-init scripts (with openstack though) so the Centos 7.4 problems seems isolated to some VMs on Digitalocean only.
 
Back
Top