themew
Regular Pleskian
Check that your IP is whitelisted in Fail2ban (if you're using it) and check this site Loading site please wait...
to fix your 502 error.
to fix your 502 error.
Check that your IP is whitelisted in Fail2ban (if you're using it) and check this site Loading site please wait...
to fix your 502 error.
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
Yes,nothing happened!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
Yes,nothing happened!
YesIs SELinux enabled?
thank you very much,i'll do the same and put results here!45.2.7. Enable or Disable SELinux
Disable it and reboot, set it to disabled
After I ran into the Cento 7.4 update issue, because I didn't wait, I had a lot of issues to solve and the only remaining one is due to SELinux. So try disabling it and rebooting. Maybe that'll do the trick. I'll be around.
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
[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 ++++++++++++++++++++++++++++++++++++++++++++
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?
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
sudo rpm -e —nodeps grub2-tools-2.02-0.44.el7.centos.x86_64
sudo yum -y install grub2-tools
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.
The older 1.4.0 version didn’t have any dependent applications, so I removed it manually.
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.
> add the correct default route persistently.
Just add the gateway parameter to /etc/sysconfig/network
That should make it persistent for your devicesCode:GATEWAY=<yourgatewayipaddres>