[Dbmail] libssl.so.37 error after distribution upgrade

[Admin Beckspaced]

Hello dbmail users ;)

I just did a test on my local dev server and upgraded openSUSE from 42.1
to the latest 42.2

After the openSUSE upgrade dbmail won't start and complains:

/usr/sbin/dbmail-lmtpd: error while loading shared libraries:
libssl.so.37: cannot open shared object file: No such file or directory

ldd on the binary reports the following:

ldd /usr/sbin/dbmail-pop3d
linux-vdso.so.1 (0x00007ffd5d73b000)
libcrypt.so.1 => /lib64/libcrypt.so.1 (0x00007f365b5b3000)
libgmodule-2.0.so.0 => /usr/lib64/libgmodule-2.0.so.0
(0x00007f365b3ae000)
libgthread-2.0.so.0 => /usr/lib64/libgthread-2.0.so.0
(0x00007f365b1ac000)
libgmime-2.6.so.0 => /usr/lib64/libgmime-2.6.so.0
(0x00007f365af3c000)
libgio-2.0.so.0 => /usr/lib64/libgio-2.0.so.0 (0x00007f365abb4000)
libgobject-2.0.so.0 => /usr/lib64/libgobject-2.0.so.0
(0x00007f365a963000)
libglib-2.0.so.0 => /usr/lib64/libglib-2.0.so.0
(0x00007f365a653000)
libm.so.6 => /lib64/libm.so.6 (0x00007f365a355000)
libmhash.so.2 => /usr/lib64/libmhash.so.2 (0x00007f365a129000)
libevent_pthreads-2.0.so.5 =>
/usr/lib64/libevent_pthreads-2.0.so.5 (0x00007f3659f26000)
libevent-2.0.so.5 => /usr/lib64/libevent-2.0.so.5
(0x00007f3659cdc000)
libssl.so.43 => /usr/lib64/libssl.so.43 (0x00007f3659a82000)
libcrypto.so.41 => /usr/lib64/libcrypto.so.41 (0x00007f365967b000)
libzdb.so.11 => /usr/lib64/libzdb.so.11 (0x00007f3659465000)
libdbmail.so.0 => /usr/lib64/dbmail/libdbmail.so.0
(0x00007f36591ed000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f3658fd0000)
libc.so.6 => /lib64/libc.so.6 (0x00007f3658c2c000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f3658a28000)
libz.so.1 => /lib64/libz.so.1 (0x00007f3658812000)
libselinux.so.1 => /lib64/libselinux.so.1 (0x00007f36585eb000)
libresolv.so.2 => /lib64/libresolv.so.2 (0x00007f36583d4000)
libffi.so.4 => /usr/lib64/libffi.so.4 (0x00007f36581cb000)
libpcre.so.1 => /usr/lib64/libpcre.so.1 (0x00007f3657f5b000)
libmysqlclient.so.18 => /usr/lib64/libmysqlclient.so.18
(0x00007f36579ff000)
/lib64/ld-linux-x86-64.so.2 (0x00005622a6ac0000)
libssl.so.37 => not found
libcrypto.so.36 => not found
libssl.so.1.0.0 => /lib64/libssl.so.1.0.0 (0x00007f3657792000)
libcrypto.so.1.0.0 => /lib64/libcrypto.so.1.0.0
(0x00007f3657337000)

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 ;)

Thanks & greetings
Becki

[Reindl Harald]

Post by Admin Beckspaced
Hello dbmail users ;)
I just did a test on my local dev server and upgraded openSUSE from 42.1
to the latest 42.2
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

[Admin Beckspaced]

Post by Reindl Harald

Post by Admin Beckspaced
....
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

[Pascal Longrais]

Hello,

Since I upgraded mysql in use with DBMail 2.2.17, I now have
continuously warning messages flooding the log file.

170630 16:30:25 [Warning] Unsafe statement written to the binary log
using statement format since BINLOG_FORMAT = STATEMENT. Statements
writing to a table with an auto-increment column after selecting from
another table are unsafe because the order in which rows are retrieved
determines what (if any) rows will be written. This order cannot be
predicted and may differ on master and the slave. Statement: INSERT INTO
dbmail_messages (mailbox_idnr,physmessage_id, seen_flag, answered_flag,
deleted_flag, flagged_flag, recent_flag, draft_flag, unique_id, status)
SELECT 1, physmessage_id, seen_flag, answered_flag, deleted_flag,
flagged_flag, recent_flag, draft_flag,
'00e88ea75a58a5653ab2fb0615e2bec6', status FROM dbmail_messages WHERE
message_idnr = 1179279

How is this warning critical ?

Can I fix something ?

Thx & best regards

[Reindl Harald]

Post by Pascal Longrais
Hello,
Since I upgraded mysql in use with DBMail 2.2.17, I now have
continuously warning messages flooding the log file.
170630 16:30:25 [Warning] Unsafe statement written to the binary log
using statement format since BINLOG_FORMAT = STATEMENT. Statements
writing to a table with an auto-increment column after selecting from
another table are unsafe because the order in which rows are retrieved
determines what (if any) rows will be written. This order cannot be
predicted and may differ on master and the slave. Statement: INSERT INTO
dbmail_messages (mailbox_idnr,physmessage_id, seen_flag, answered_flag,
deleted_flag, flagged_flag, recent_flag, draft_flag, unique_id, status)
SELECT 1, physmessage_id, seen_flag, answered_flag, deleted_flag,
flagged_flag, recent_flag, draft_flag,
'00e88ea75a58a5653ab2fb0615e2bec6', status FROM dbmail_messages WHERE
message_idnr = 1179279
How is this warning critical?

no idea how should one esxplain it better than the message

Post by Pascal Longrais
Can I fix something?

binlog-format = ROW

https://dev.mysql.com/doc/refman/5.7/en/binary-log-setting.html