Re: libssl.so.37 error after distribution upgrade

Admin Beckspaced <[email protected]> Thu, 8 Jun 2017 13:01:44 +0200
Newsgroups gmane.mail.imap.dbmail
Organization Beckspaced
Message-ID <[email protected]>
>> ....
>>
>> /usr/sbin/dbmail-lmtpd: error while loading shared libraries:
>> libssl.so.37: cannot open shared object file: No such file or directory
>>
>> I already tried a fresh new compile on the new openSUSE 42.2 and the
>> compile went fine without any errors but dbmail still won't start up and
>> complains about libssl.so.37
>>
>> Any hints would be awesome
> i guess you don't build rpm packages and now have a mess of old and new
> stuff - that combined with install to /usr in case of a "make install"
> is terrible, try to remove everything dbmail related and build again
>
> whatout that your openssl packages are all in the same version
> rpm -qa | grep openssl
>
> however, openssl will become a problem in general in context of dbmail,
> for Fedora users with F26 which ships openssl-1.1 and so we *really*
> need a --without-openssl fpr dbmail 3.1.x and 3.2.x ASAP to avoid it at
> all, most users don't expose dbmail because of instability with TLS
> directly to the net and have a proxy doing also TLS offloading in front
>

Hello Harald & list users,
thanks a lot for your reply. Good to see that the list is still active

After a bit of more digging in the notes during compile of dbmail I 
found the error.

warning: libssl.so.37, needed by /usr/lib64/libzdb.so, not found (try 
using -rpath or -rpath-link)
warning: libcrypto.so.36, needed by /usr/lib64/libzdb.so, not found (try 
using -rpath or -rpath-link)

so the culprit here was libzdb with the old openssl libs from openSUSE 42.1

after removing all the old garbage of dbmail & requirements and doing a 
fresh compile of dbmail and zdb all is working fine again

thanks a lot for your help and I might want to look into creating rpm's 
in the future, like you suggested.

Greetings & best wishes
Becki