[SOLVED] 5.0.11 -> 5.0.12 Upgrade failed (SSLeay.so)

[bards1888]

Mine shows the same....

lrwxrwxrwx 1 zimbra zimbra 26 Jan 29 22:37 openssl -> /opt/zimbra/openssl-0.9.8i
drwxrwxr-x 6 zimbra zimbra 4096 Jan 29 22:37 openssl-0.9.8i


I'm more leaning towards the fact the SSLeay has been linked against a non-existant version of openssl .... or.... maybe my previous version was using the i386 version which is OK and is linked against the newer 0.9.8i version ?

[jholder]

I don't know if this will fix it, but try moving both open ssl directories out of the way, then run
./install.sh -s

Let's see what happens.

[bards1888]

Do you want to verify message store database integrity? [Y]
Verifying integrity of message store databases. This may take a while.
Starting mysqld...done.
/opt/zimbra/mysql/bin/mysqlcheck: error while loading shared libraries: libssl.so.0.9.8: cannot open shared object file: No such file or directory
Generating report
No errors found
command failed

[jholder]

ok, that didn't help I was hoping the installer would install the open ssl libs, and relink the symlink.

Let me forward this on to one of our principal software engineers and see if he knows.

[bards1888]

Should I try removing the zimbra rpms and doing an install which would be like moving server ?

[uxbod]

No, one method would be to backup /opt/zimbra, and then install using the dummy ability. You can then copy back across /opt/zimbra. Kind of what is documented in Backing up and restoring Zimbra (Open Source Version - Zimbra :: Wiki).

[Bill Brock]

I would probably restore my backup I performed right before I did the failed upgrade. Then reinstall that version (it will ask you if you want to upgrade even though it is the same version) and see if you receive the same errors. This may actually fix some errors. I performed this same function and it fixed my admin logs, my server status issue, as well as my loggers stats issues I had had since I moved my install to a new server. Not sure why but it sure enough fixed them. I am glad it did as I now feel more comfortable upgrading to 5.0.12.

[bards1888]

Originally Posted by Bill Brock

I would probably restore my backup I performed right before I did the failed upgrade. Then reinstall that version (it will ask you if you want to upgrade even though it is the same version) and see if you receive the same errors. This may actually fix some errors. I performed this same function and it fixed my admin logs, my server status issue, as well as my loggers stats issues I had had since I moved my install to a new server. Not sure why but it sure enough fixed them. I am glad it did as I now feel more comfortable upgrading to 5.0.12.

Thanks for your advice Bill.

I rolled back to my snapshot, re-installed the same version ie 5.0.11 to 5.0.11 upgrade. No problems were encountered. Then I tried to upgrade to 5.0.12 and got the same error message;

Net::SSLeay: libssl.so.0.9.8 cannot open shared object file as per my first post.

I'm now going to roll the snapshot back again and see what libs SSLeay.so is linked against.


Update - for what it is worth, with 5.0.11 SSLeay.so is linked thusly;

[root@zimbra SSLeay]# ldd /opt/zimbra/zimbramon/lib/i486-linux-gnu-thread-multi/auto/Net/SSLeay/SSLeay.so
linux-gate.so.1 => (0x00589000)
libssl.so.0.9.8 => /opt/zimbra/openssl-0.9.8g/lib/libssl.so.0.9.8 (0x00e62000)
libcrypto.so.0.9.8 => /opt/zimbra/openssl-0.9.8g/lib/libcrypto.so.0.9.8 (0x00188000)
libz.so.1 => /usr/lib/libz.so.1 (0x005ca000)
libc.so.6 => /lib/libc.so.6 (0x00440000)
libdl.so.2 => /lib/libdl.so.2 (0x0080e000)
/lib/ld-linux.so.2 (0x00bb8000)

[root@zimbra lib]# ldd /opt/zimbra/zimbramon/lib/i386-linux-thread-multi/auto/Net/SSLeay/SSLeay.so
linux-gate.so.1 => (0x00356000)
libssl.so.0.9.8 => /opt/zimbra/openssl-0.9.8g/lib/libssl.so.0.9.8 (0x00a8a000)
libcrypto.so.0.9.8 => /opt/zimbra/openssl-0.9.8g/lib/libcrypto.so.0.9.8 (0x00110000)
libz.so.1 => /usr/lib/libz.so.1 (0x00751000)
libc.so.6 => /lib/libc.so.6 (0x00c36000)
libdl.so.2 => /lib/libdl.so.2 (0x0067a000)
/lib/ld-linux.so.2 (0x00bb8000)


It would appear that the upgrade is breaking this.

Has anyone else succesfully performed an upgrade from 5.0.11 to 5.0.12 on Centos/RHEL 32bit with FOSS Zimbra ?

[quanah]

The install log clearly shows that the 5.0.12 rpms failed to install. That needs to be corrected first. Since the 5.0.12 RPMs aren't installed, none of the correct software is installed.

[bards1888]

Originally Posted by quanah

The install log clearly shows that the 5.0.12 rpms failed to install. That needs to be corrected first. Since the 5.0.12 RPMs aren't installed, none of the correct software is installed.

But after the failed install, when I query the RPM database it shows the that all the 5.0.12 RPMS are installed.

How do you suggest I fix this, Install the RPMS manually ?