Well, that's interesting! The server with a problem (which I'll call P1) doesn't even have the symlinks for libssl.so and libcrypto.so, nor the files that they would normally point to!
$ ldd /usr/pxp12/pxplus
linux-vdso.so.1 => (0x00007ffeedffa000)
libdl.so.2 => /lib64/libdl.so.2 (0x00000034cc000000)
libm.so.6 => /lib64/libm.so.6 (0x00000034cc800000)
libnsl.so.1 => /lib64/libnsl.so.1 (0x00000034ce400000)
libc.so.6 => /lib64/libc.so.6 (0x00000034cb800000)
$ ls -l /lib64/libssl.so
ls: cannot access /lib64/libssl.so: No such file or directory
$ ls -l /lib64/libcrypto.so
ls: cannot access /lib64/libcrypto.so: No such file or directory
$ ll libssl*
ls: cannot access libssl*: No such file or directory
$ ll libcrypto*
ls: cannot access libcrypto*: No such file or directory
Now, we do have 3 other servers of various ages (which I'll call S1, S2, & S3, with S3 being the newest), which also run the same PXPlus version 12 (tcb(29)=1250000). My test program fails on S1 & S2, but works on S3. So, I checked the files on all 3 servers. The symlinks are exactly the same on all three, but the target files are newer and larger on S3 (the working server)
Logs from S1/S2 (where the test program fails) are below:
lrwxrwxrwx. 1 root root 16 Sep 21 2016 /lib64/libssl.so -> libssl.so.1.0.1e
lrwxrwxrwx. 1 root root 19 Sep 21 2016 /lib64/libcrypto.so -> libcrypto.so.1.0.1e
-rwxr-xr-x. 1 root root 449880 May 9 2016 /lib64/libssl.so.1.0.1e
-rwxr-xr-x. 1 root root 2017168 May 9 2016 /lib64/libcrypto.so.1.0.1e
Logs from S3 (where the test program works) are below. Note that the target files are larger/newer:
lrwxrwxrwx. 1 root root 16 Jun 19 2017 /lib64/libssl.so -> libssl.so.1.0.1e
lrwxrwxrwx. 1 root root 19 Jun 19 2017 /lib64/libcrypto.so -> libcrypto.so.1.0.1e
-rwxr-xr-x. 1 root root 454008 Feb 20 2017 /lib64/libssl.so.1.0.1e
-rwxr-xr-x. 1 root root 2025760 Feb 20 2017 /lib64/libcrypto.so.1.0.1e
The fact that the problem server P1 doesn't even have the libssl.so and libcrypto.so links or targets makes me wonder if those files are even used any more since the program did work fine up until last week! Mike or Allen, can you confirm whether those links are still needed in PXPlus 12?
I'm tempted to update the target files (libssl.so.1.0.1e and libcrypto.so.1.0.1e) on the S1 & S2 servers so that they match S3, but I have no idea how to update them. Any suggestions on how or whether those files can be updated?
Again, I appreciate any feedback - it may seem minor or irrelevant, but it may trigger something I haven't looked at, and I'm really curious now to figure out what is causing this!