problem after update

Submitted by mmoxnes on Sat, 02/22/2014 - 03:50 Pro Licensee

after I did the last update I get: Failed to query Postfix config command to get the current value of parameter recipient_bcc_maps:

also when I try to run yum I get an error related to
/usr/lib/libsasl2.so.2:

invalid ELF header.

it also states that my current version of python dont match

I tried to reinstall the Glibc, that didnt help,

installed glibc: 2.12.-1.132.el6.i686 Python: 2.6.6 (r266:84292 jan 22) GCC 4.7.7 20120313

Status: 
Active

Comments

Submitted by andreychek on Sat, 02/22/2014 - 09:22

Do you happen to have the output that was generated during the last update?

Also, what is the output of this command:

ls /etc/yum.repos.d

And lastly, what is the output of this command:

postconf | grep recipient_bcc_maps

Submitted by mmoxnes on Sat, 02/22/2014 - 16:04 Pro Licensee

ls /etc/yum.repos.d: CentOS-Base.repo CentOS-Vault.repo virtualmin.repo CentOS-Debuginfo.repo epel.repo virtualmin.repo.rpmnew CentOS-Media.repo epel-testing.repo

postconf | grep recipient_bcc_maps postconf: error while loading shared libraries: /usr/lib/libsasl2.so.2: invalid ELF header

Submitted by andreychek on Sat, 02/22/2014 - 16:14

Hmm, what is the output of these three commands:

uname -a
file /bin/ls
rpm -qa | grep sasl

Submitted by mmoxnes on Sat, 02/22/2014 - 16:19 Pro Licensee

uname -a Linux magica.mcmox.no 2.6.32-431.5.1.el6.i686 #1 SMP Tue Feb 11 21:56:33 UTC 2014 i686 i686 i386 GNU/Linux

file /bin/ls /bin/ls: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.18, stripped

rpm -qa | grep sasl cyrus-sasl-2.1.23-13.el6_3.1.i686 cyrus-sasl-plain-2.1.23-13.el6_3.1.i686 cyrus-sasl-md5-2.1.23-13.el6_3.1.i686 cyrus-sasl-gssapi-2.1.23-13.el6_3.1.i686 cyrus-sasl-lib-2.1.23-13.el6_3.1.i686

Submitted by mmoxnes on Sat, 02/22/2014 - 16:24 Pro Licensee

trying better formatting rpm -qa | grep sasl

cyrus-sasl-2.1.23-13.el6_3.1.i686

cyrus-sasl-plain-2.1.23-13.el6_3.1.i686

cyrus-sasl-md5-2.1.23-13.el6_3.1.i686

cyrus-sasl-gssapi-2.1.23-13.el6_3.1.i686

cyrus-sasl-lib-2.1.23-13.el6_3.1.i686

Submitted by mmoxnes on Sun, 02/23/2014 - 08:06 Pro Licensee

I reinstalled the server, only took a few hours including restoring the websites.

but it would be nice to know what caused this error... and how to avoid it in the future

Submitted by andreychek on Sun, 02/23/2014 - 08:42

I'm actually somewhat puzzled as to what might have caused that. I've never run into an error like that before.

Doing some Googling, it doesn't seem like a common problem, but the few posts I found on a similar issue indicated that it could be caused by a server having a mixture of 32 bit and 64 bit packages on it.

However, reviewing your system, it's running a 32 bit kernel, with 32 bit packages -- and we verified that the library in question is 32 bit.

My only other thoughts are that it could be due to a package from a third party repository, or possibly some sort of file corruption.

In the case of the former -- we'd suggest not enabling any third party repositories, and only installing packages from a non-standard repository when necessary. It appeared that the package in question was a standard CentOS package though.

So unfortunately, I'm not sure what to tell you to do differently next time.

Submitted by mmoxnes on Sun, 02/23/2014 - 08:59 Pro Licensee

I think I found a possible cause to the error, not sure yet, I had a different machine stored on the same iScsi device and it suddenly hade a lot of harddisk errors, so I did a ckfs on my old linux server and It had a lot of errors on my sdb1 (/home) device (didnt tell any on sba1 (/boot) or sda2 (/ ) but that migth have happened during reboot after upgrading kernel....

Submitted by andreychek on Sun, 02/23/2014 - 12:23

Yeah, if you're seeing some disk errors on the drive that hosted the OS for that server, that could definitely explain the issue you saw.