SMTP error after mariaDB upgrade

[fearworks]

Hi,


I updated my server from mysql 5.5 mariadb to mariaDB 10.2 following these steps.
https://www.tecmint.com/upgrade-mariadb-...an-ubuntu/

Soon after I finished the installation and rebooted my server I tried logging in roundcube but I got
I checked the logs and I figured that dovecot needs the mysql module
so I did

Code:

yum install dovecot-mysql

Now I can login to roundcube to view old mails, but when I try to send  I get
.
I can't receive neither. Also the issue happens on my phone too, when sending I get "connecting to outgoing server failed" and I can't receive.

tail /var/log/dovecot.log gives the following:



Does anyone know what the issue is? I don't want to try random solutions from the internet since this is a production server.

After playing around on some test server VMs for a few hours, the only seemingly reliable way to use MariaDB version 10 with Sentora is to apply it to your repo settings BEFORE you even install Sentora. I cannot find an "easy" upgrade path once Sentora is installed, without lots and lots of messing around to reconfigure pretty much everything. Following any upgrade guides online (and they're all pretty similar) yields an upset Sentora, where webmail won't log in, the server logo in the panel information is missing, and probably lots of other issues. So what seems to work is this:

Starting with a brand new CentOS server, set up the repo settings first:

Code:

vi /etc/yum.repos.d/MariaDB.repo

Add into this file:

Code:

# MariaDB 10.3 CentOS repository list - created 2019-02-03 19:26 UTC
# http://downloads.mariadb.org/mariadb/repositories/
[mariadb]
name = MariaDB
baseurl = http://yum.mariadb.org/10.3/centos7-amd64
gpgkey=https://yum.mariadb.org/RPM-GPG-KEY-MariaDB
gpgcheck=1

and save. You don't have to use version 10.3, and you can find the appropriate text for different versions here: https://downloads.mariadb.org/mariadb/re...r=exascale

Now, run the Sentora installer in the usual way.

This is not an upgrade... this is a new install. BTW, note that it's completely untested by me and should not be attempted for a production server!

I'm sure it's possible to rescue your installation... if it is it would require a lot of time and attention.

Keith