Friday, August 14, 2015

If you are doing rsync and you encountered this error like rsync out of memory, you may want to take a look.a this article (Rsync out of memory? Try this...). Need to add an additional parameter (--no-inc-recursive) to the rsync commands.

According to the article, the the out of memory failure occured when rsync attempts to load all the filenames and info in to RAM at startup. For example,

If you do encountered an issue such as this. Apparently, there is a
incompatibility between llibXi-1.7.2-2.,/pre>2.el6.i686 != libXi-1.6.1-3.el6.x86_64

# yum install libXrender
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 libXrender which is missing some
dependency that another package requires. Yum is trying to
solve this by installing an older version of libXrender 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 libXrender.otherarch ... this should give you an error
message showing the root cause of the problem.
2. You have multiple architectures of libXrender 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 libXrender 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: libXrender-0.9.8-2.1.el6.i686 != libXrender-0.9.7-2.el6.x86_64
You could try using --skip-broken to work around the problem

To resolve the issue, you have to install libXrender-0.9.8-2.1.el6.x86_64

If you do encountered an issue such as this. Apparently, there is a
incompatibility between llibXi-1.7.2-2.,/pre>2.el6.i686 != libXi-1.6.1-3.el6.x86_64

# yum install libXi
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 libXi which is missing some
dependency that another package requires. Yum is trying to
solve this by installing an older version of libXi 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 libXi.otherarch ... this should give you an error
message showing the root cause of the problem.
2. You have multiple architectures of libXi 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 libXi 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: libXi-1.7.2-2.2.el6.i686 != libXi-1.6.1-3.el6.x86_64
You could try using --skip-broken to work around the problem

To resolve the issue, we have to do a

# yum install libXi-1.7.2-2.2.el6.x86_64

and you will see quite a list of updates to some core libraries. Finally, you can do a

If you do encountered an issue such as this. Apparently, there is a incompatibility between libstdc++-4.4.7-16.el6.i686 != libstdc++-4.4.7-11.el6.x86_64.

# yum install libstdc++.so.6
Resolving Dependencies
--> Running transaction check
---> Package libstdc++.i686 0:4.4.7-16.el6 will be installed
--> 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 libstdc++ which is missing some
dependency that another package requires. Yum is trying to
solve this by installing an older version of libstdc++ 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 libstdc++.otherarch ... this should give you an error
message showing the root cause of the problem.
2. You have multiple architectures of libstdc++ 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 libstdc++ 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: libstdc++-4.4.7-16.el6.i686 != libstdc++-4.4.7-11.el6.x86_64
You could try using --skip-broken to work around the problem
** Found 1 pre-existing rpmdb problem(s), 'yum check' output follows:
1:emacs-23.1-25.el6.x86_64 has missing requires of libotf.so.0()(64bit)

To resolve the issues, do a

# yum install libstdc++-4.4.7-16.el6.x86_64

and you will see quite a list of updates to some core libraries. Finally, you can do a