My suggests to look for:
1. Are your other servers setups installed from "Entware for QNAP"
too?
2. Do your other servers have libz.so* located under /opt/lib/ too?
3. Did you compare owner and permissions of every libz.so* file between
servers too?
4. Are other servers running Dovecot with same user account?
El 20/3/23 a les 4:01, Horst Simon ha escrit:> I try to logon to map using dovecot with SSL required. I get following
> entries in the log:Mar 20 13:49:30 auth: Debug: Loading modules from
> directory: /opt/lib/dovecot/modules/auth
> Mar 20 13:49:30 auth: Debug: Module loaded:
> /opt/lib/dovecot/modules/auth/lib20_auth_var_expand_crypt.so
> Mar 20 13:49:30 auth: Debug: Read auth token secret from
> /opt/var/run/dovecot/auth-token-secret.dat
> Mar 20 13:49:30 auth: Debug: passwd-file /opt/etc/dovecot/userdb:Read 1
> users in 0 secs
> Mar 20 13:49:30 auth: Debug: auth client connected (pid=26120)
> Mar 20 13:49:30 imap-login: Error: Failed to initialize SSL server
> context: Can't load SSL certificate (ssl_cert setting):
> error:12800067:DSO support routines::could not load the shared library:
> filename(libz.so): libz.so: cannot open shared object file: No such file
> or directory, error:12800067:DSO support routines::could not load the
> shared library: user=<>, rip=192.168.117.5, lip=192.168.117.2,
> session=<eX3e+Uv3k8DAqHUF>
> Mar 20 13:49:30 imap-login: Info: Disconnected: TLS initialization
> failed. (no auth attempts in 0 secs): user=<>, rip=192.168.117.5,
> lip=192.168.117.2, session=<eX3e+Uv3k8DAqHUF
>
> The library files exist in the include directory
> [/opt] # find . -name libz* -print
>
> ./lib/opkg/info/libzstd.control
>
> ./lib/opkg/info/libzstd.list
>
> ./lib/libz.so
>
> ./lib/libz.so.1
>
> ./lib/libz.so.1.2.13
>
> ./lib/libzstd.so
>
> ./lib/libzstd.so.1
>
> ./lib/libzstd.so.1.5.2
>
> ./lib/libz.a
>
>
> Have the dovecot settings the same on other servers and it works,
> Dovecot is v2.3.18, installed from Entware for QNAP. Any help?appreciated.
>
> Horst
>
>
>
--
Narcis Garcia
__________
I'm using this dedicated address because personal addresses aren't
masked enough at this mail public archive. Public archive administrator
should fix this against automated addresses collectors.