Resolution I was able to find and successfully test a resolution to this problem.
Although the SSLeay.so file was in-fact readable, it linked to a non-existant folder.
[root@mail ~]# readelf -d /opt/zimbra/zimbramon/lib/i486-linux-gnu-thread-multi/auto/Net/SSLeay/SSLeay.so
Dynamic section at offset 0x55014 contains 25 entries:
Tag Type Name/Value
0x00000001 (NEEDED) Shared library: [libssl.so.0.9.8]
0x00000001 (NEEDED) Shared library: [libcrypto.so.0.9.8]
0x00000001 (NEEDED) Shared library: [libz.so.1]
0x00000001 (NEEDED) Shared library: [libc.so.6]
0x0000000f (RPATH) Library rpath: [/opt/zimbra/openssl-0.9.8k/lib]
0x0000000c (INIT) 0x8f40
0x0000000d (FINI) 0x4d904
0x00000004 (HASH) 0xb4
0x6ffffef5 (GNU_HASH) 0x1238
0x00000005 (STRTAB) 0x4194
0x00000006 (SYMTAB) 0x1c34
0x0000000a (STRSZ) 13864 (bytes)
0x0000000b (SYMENT) 16 (bytes)
0x00000003 (PLTGOT) 0x55594
0x00000002 (PLTRELSZ) 2392 (bytes)
0x00000014 (PLTREL) REL
0x00000017 (JMPREL) 0x85e8
0x00000011 (REL) 0x7ca8
0x00000012 (RELSZ) 2368 (bytes)
0x00000013 (RELENT) 8 (bytes)
0x6ffffffe (VERNEED) 0x7c68
0x6fffffff (VERNEEDNUM) 1
0x6ffffff0 (VERSYM) 0x77bc
0x6ffffffa (RELCOUNT) 2
0x00000000 (NULL) 0x0
[root@mail ~]#
The problem was that Library rpath: [/opt/zimbra/openssl-0.9.8k/lib] didn't exist!
I added a link from /opt/zimbra/openssl-0.9.8k -> /opt/zimbra/openssl
(as seen below)
[root@mail ~]# ls -alh /opt/zimbra
total 364K
..... (section trimmed out for clarity) .....
lrwxrwxrwx 1 root root 26 Jul 8 02:11 openssl -> /opt/zimbra/openssl-0.9.8n lrwxrwxrwx 1 root root 26 Jul 8 01:43 openssl-0.9.8k -> /opt/zimbra/openssl-0.9.8n
drwxrwxr-x 6 root root 4.0K Jul 8 02:11 openssl-0.9.8n
..... (section trimmed out for clarity) .....
[root@mail ~]#
One important note: This problem existed on two servers that were otherwise identical, but they both pointed to different non-existant openssl folders in the SSLEay.so. RUN the readelf -d on SSLeay.so and verify the Library rpath before creating a link to repair it.
After creating the link, a re-install of the current version completed successfully, and resolved the unable to get globalgrant errors. |