SMTP error after mariaDB upgrade

[fearworks]

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

I should add that changing the version of MariaDB to a later version (10+ I think) looks like it will introduce a number of other issues. For example, the daemon does not appear to run correctly, due to issues with the datetime format being changed in MariaDB. I am seeing an error message when the daemon runs:

Code:

SQL Error: Incorrect datetime value: '1549233750' for column `sentora_core`.`x_logs`.`lg_when_ts` at row 1

Looking here:

https://stackoverflow.com/questions/2280...umber-1292

it is probable that this is because there are null entries or invalid timedate entries within the Sentora database entries, which would need sorting out.

So, I would say that upgrading MariaDB is not a wise move, and is also going to be a pain to undo. You are probably looking at a full reinstall

Keith

After some more poking around, this error was actually a bug in the Sentora code. This file:

Code:

/etc/sentora/panel/dryden/debug/logger.class.php

has a line that tries to write a timestamp to a field in the database that is autofilled with a timestamp. MariaDB 5.5 must just ignore this and say "oh well", while the newer versions (10+) don't like it and actually throw it up as an error. So the line:

Code:

$statement = "INSERT INTO x_logs (lg_user_fk, lg_code_vc, lg_module_vc, lg_detail_tx, lg_stack_tx, lg_when_ts) VALUES (0, '" . $this->logcode . "', 'NA', '" . $this->detail . "', '" . $this->mextra . "','" . time() . "')";

needs changing to:

Code:

$statement = "INSERT INTO x_logs (lg_user_fk, lg_code_vc, lg_module_vc, lg_detail_tx, lg_stack_tx) VALUES (0, '" . $this->logcode . "', 'NA', '" . $this->detail . "', '" . $this->mextra . "')";

There's a similar line a few lines above it, which is correct, so make sure you correct the right section.

In theory, if you combine my suggestion to set up the repo and THEN install Sentora, and also make this change as soon as Sentora is installed, you should have some success.

I ran a few benchmark tests and, being completely honest, version 10.3 seemed slower than version 5.5, but I might play about with it some more.

Keith