MARIADB errors after update 10.1x to 10.2 downgrade to 10.1don't start mariadb

[ikkeben]

MARIADB errors after update 10.1x to 10.2 downgrade to 10.1don't start mariadb

CENTOS 7x

Latest custombuild and plugin with that i did update and downgrade.

After update 10.2 there was a problem with some php therefore the downgrade, but didn't succceed and not starting maridb now

BUT WE NEED the downgrade! HOW?
(
Nov 18 23:29:07 mysqld: InnoDB: A downgrade from MariaDB 10.2.2 or later is not supported.
Nov 18 23:29:07 mysqld: InnoDB: If this error appears when you are creating an InnoDB database,
Nov 18 23:29:07 mysqld: InnoDB: the problem may be that during an earlier attempt you managed
Nov 18 23:29:07 mysqld: InnoDB: to create the InnoDB data files, but log file creation failed.
Nov 18 23:29:07mysqld: InnoDB: If that is the case, please refer to
Nov 18 23:29:07 mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.6/en/error-creating-innodb.html

MariaDB-backup-10.1.48-1.el7.centos ######################################## Created symlink from /etc/systemd/system/mysql.service to /etc/systemd/system/mariadb.service. Created symlink from /etc/systemd/system/mysqld.service to /etc/systemd/system/mariadb.service. Created symlink from /etc/systemd/system/multi-user.target.wants/mariadb.service to /etc/systemd/system/mariadb.service. Ensuring local-infile is disabled for security reasons in MySQL configuration file... Job for mariadb.service failed because the control process exited with error code. See "systemctl status mariadb.service" and "journalctl -xe" for details. Giving mysqld a few seconds to start up... Giving mysqld a another few seconds to start up... Giving mysqld last 20 seconds to start up... Version check failed. Got the following error when calling the 'mysql' command line client ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2 "No such file or directory") FATAL ERROR: Upgrade failed /usr/bin/mysqlcheck: Got error: 2002: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2 "No such file or directory") when trying to connect cp: '/usr/lib/libmysqlclient.so' and '/usr/lib/mysql/libmysqlclient.so' are the same file cp: '/usr/lib/libmysqlclient.so.18' and '/usr/lib/mysql/libmysqlclient.so.18' are the same file Restarting MySQL. Job for mariadb.service failed because the control process exited with error code. See "systemctl status mariadb.service" and "journalctl -xe" for details. Installation completed.

 

[smtalk]

backup->reinstall mariadb->restore is the only way to downgrade. I wouldn't suggest downgrading to EOL versions though.

 

[smtalk]

After update 10.2 there was a problem with some php therefore the downgrade

Just set less restrictive sql_mode, that's it.

 

[ikkeben]

OK you mean so ?

MySQL Error "Incorrect integer value '' for column 'name' at row 1"

Posted: 2015-04-12 02:30:16


If a PHP script tries to set a string value, such as an empty string, into a MySQL integer data type or column, you will likely see this error message:


Incorrect integer value ” for column ‘name’ at row 1

In this situation, what is happening is that the script is attempting to insert or update a row with the integer entry taking on either the default value (e.g., of 0 or NULL) or the next AUTO_INCREMENT value.


But MySQL is not interpreting this action as valid due to its SQL_MODE being in STRICT mode.


In this case, to not treat this action as an error, edit my.ini, find this line –

sql_mode=NO_ENGINE_SUBSTITUTION,STRICT_TRANS_TABLES

And set to to an empty string –

sql_mode=""

Save my.ini, restart MySQL.


Afterwards, the value of '' (empty string) will just default to whatever:


A. Is specified as the default value of the column (set when the table was created).


B. Is the underlining designated default value for the integer data type.


If this does not help, then the script needs to be searched (in your editor of choice) for the column name, and the PHP code or the SQL statements on the found lines edited to set either a proper value, or the column name removed from those statements.

 

[ikkeben]

backup->reinstall mariadb->restore is the only way to downgrade. I wouldn't suggest downgrading to EOL versions though.

Yes to all not so good idea i did for now a restore from snapshot i made before updating.

Look into it later thanks