Coba lakukan:
rm -f /var/lib/rpm/__db*
rpm --rebuilddb
yum clean all
yum update -y
[root@d=serverkusworoo ~]# rm -f /var/lib/rpm/__db*
[root@d=serverkusworoo ~]# rpm --rebuilddb
[root@d=serverkusworoo ~]#
[root@d=serverkusworoo ~]# yum clean all
Loaded plugins: fastestmirror, priorities, protectbase, replace
Cleaning repos: base epel extras mratwork-epel mratwork-google-mod-pagespeed
: mratwork-ius-archive mratwork-ius-stable mratwork-mariadb-32
: mratwork-mariadb-64 mratwork-nginx mratwork-nginx-stable
: mratwork-release-neutral-noarch mratwork-release-version-arch
: mratwork-varnish-3.0 mratwork-webtatic updates
Cleaning up Everything
Cleaning up list of fastest mirrors
[root@d=serverkusworoo ~]# yum update -y
Loaded plugins: fastestmirror, priorities, protectbase, replace
Setting up Update Process
Determining fastest mirrors
epel/metalink | 9.6 kB 00:00
mratwork-epel/metalink | 9.6 kB 00:00
* base: mirror.scalabledns.com
* epel: mirror.sfo12.us.leaseweb.net
* extras: mirror.scalabledns.com
* mratwork-epel: mirror.sfo12.us.leaseweb.net
* mratwork-ius-stable: mirror.team-cymru.org
* mratwork-webtatic: us-east.repo.webtatic.com
* updates: mirror.scalabledns.com
base | 3.7 kB 00:00
base/primary_db | 4.7 MB 00:00
epel | 4.3 kB 00:00
epel/primary_db | 5.8 MB 00:00
extras | 3.4 kB 00:00
extras/primary_db | 37 kB 00:00
mratwork-epel | 4.3 kB 00:00
mratwork-epel/primary_db | 5.8 MB 00:00
mratwork-google-mod-pagespeed | 951 B 00:00
mratwork-google-mod-pagespeed/primary | 3.5 kB 00:00
mratwork-google-mod-pagespeed 22/22
mratwork-ius-archive | 2.3 kB 00:00
mratwork-ius-archive/primary_db | 3.7 MB 00:02
mratwork-ius-stable | 2.2 kB 00:00
mratwork-ius-stable/primary_db | 210 kB 00:00
mratwork-mariadb-32 | 2.9 kB 00:00
mratwork-mariadb-32/primary_db | 21 kB 00:00
mratwork-mariadb-64 | 2.9 kB 00:00
mratwork-mariadb-64/primary_db | 22 kB 00:00
mratwork-nginx | 2.9 kB 00:00
mratwork-nginx/primary_db | 36 kB 00:00
mratwork-nginx-stable | 2.9 kB 00:00
mratwork-nginx-stable/primary_db | 15 kB 00:00
mratwork-release-neutral-noarch | 951 B 00:00
mratwork-release-neutral-noarch/primary | 1.2 kB 00:00
mratwork-release-neutral-noarch 5/5
mratwork-release-version-arch | 951 B 00:00
mratwork-release-version-arch/primary | 201 B 00:00
mratwork-varnish-3.0 | 951 B 00:00
mratwork-varnish-3.0/primary | 9.4 kB 00:00
mratwork-varnish-3.0 40/40
mratwork-webtatic | 3.6 kB 00:00
mratwork-webtatic/primary_db | 118 kB 00:00
updates | 3.4 kB 00:00
updates/primary_db | 1.4 MB 00:00
0 packages excluded due to repository protections
Resolving Dependencies
--> Running transaction check
skip......
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 libxml2 which is missing some
dependency that another package requires. Yum is trying to
solve this by installing an older version of libxml2 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 libxml2.otherarch ... this should give you an error
message showing the root cause of the problem.
2. You have multiple architectures of libxml2 installed, but
yum can only see an upgrade for one of those arcitectures.
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 libxml2 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: libxml2-2.7.6-21.el6_8.1.i686 != libxml2-2.9.1-1.mr.el6.x86_64
Topic: website gk bisa di akses, error nginx dan httpd (Read 13302 times)
