Hi,
I just did the upgrade of OMV from latest 3.x to 4. And it worked quite well, I didn't find any errors during the upgrade - no surprise since I am only using a very limited featureset (mainly a RAID5 published via SMB, plus mySQL - both used for KODI on several client boxes).
The directories and the SQL DB are accessible after the upgrade, so at a first glance it looks like everything is ok. Also the http mySQL admin UI can be used. The normally used services are up and running.
But then I realized that in the OMV GUI the service "MySQL" has a red light in the service overview in column "running".
A research in the logs showed the following two topics - the mentioned two tables mysql.events and mysql.proc are shown at more places in the logs. Sounds to me like mySQL is internally linked to MariaDB, and that something minor went wrong on the migration of DBMS.
Is this a known issue - even better, maybe with a known solution? I don't find it here in the forum.
Cheers,
Kane
Code
2018-05-13T13:25:54+0200 MediaNAS1 mysqld[1062]: 2018-05-13 13:25:54 140052994717440 [Note] InnoDB: Dumping buffer pool(s) not yet started
2018-05-13T13:25:54+0200 MediaNAS1 mysqld[1062]: 2018-05-13 13:25:54 140053658866240 [Note] Server socket created on IP: '0.0.0.0'.
2018-05-13T13:25:55+0200 MediaNAS1 mysqld[1062]: 2018-05-13 13:25:55 140053658866240 [ERROR] Incorrect definition of table mysql.event: expected column 'sql_mode' at position 14 to have type set('REAL_AS_FLOAT','PIPES_AS_CONCAT','ANSI_QUOTES','IGNORE_SPACE','IGNORE_BAD_TABLE_OPTIONS','ONLY_FULL_GROUP_BY','NO_UNSIGNED_SUBTRACTION','NO_DIR_IN_CREATE','POSTGRESQL','ORACLE','MSSQL','DB2','MAXDB','NO_KEY_OPTIONS','NO_TABLE_OPTIONS','NO_FIELD_OPTIONS','MYSQL323','MYSQL40','ANSI','NO_AUTO_VALUE_ON_ZERO','NO_BACKSLASH_ESCAPES','STRICT_TRANS_TABLES','STRICT_ALL_TABLES','NO_ZERO_IN_DATE','NO_ZERO_DATE','INVALID_DATES','ERROR_FOR_DIVISION_BY_ZERO','TRADITIONAL','NO_AUTO_CREATE_USER','HIGH_NOT_PRECEDENCE','NO_ENGINE_SUBSTITUTION','PAD_CHAR_TO_FULL_LENGTH'), found type set('REAL_AS_FLOAT','PIPES_AS_CONCAT','ANSI_QUOTES','IGNORE_SPACE','NOT_USED','ONLY_FULL_GROUP_BY','NO_UNSIGNED_SUBTRACTION','NO_DIR_IN_CREATE','POSTGRESQL','ORACLE','MSSQL','DB2','MAXDB','NO_KEY_OPTIONS','NO_TABLE_OPTIONS','NO_FIELD_OPTIONS','MYSQL323','MYSQL40','ANSI','NO_AUTO_VALUE_ON_ZERO','NO_BACKSLASH_ESCAPES','STRICT_TRANS_TABLES','STRICT_A
2018-05-13T13:25:55+0200 MediaNAS1 mysqld[1062]: 2018-05-13 13:25:55 140053658866240 [ERROR] mysqld: Event Scheduler: An error occurred when initializing system tables. Disabling the Event Scheduler.
2018-05-13T13:25:55+0200 MediaNAS1 mysqld[1062]: 2018-05-13 13:25:55 140053658866240 [Note] /usr/sbin/mysqld: ready for connections.
2018-05-13T13:25:55+0200 MediaNAS1 mysqld[1062]: Version: '10.1.26-MariaDB-0+deb9u1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 Debian 9.1
2018-05-13T13:25:55+0200 MediaNAS1 systemd[1]: Started MariaDB database server.Code
May 13 13:12:29 MediaNAS1 mysqld_safe[14112]: 2018-05-13 13:12:29 140562172942080 [ERROR] Incorrect definition of table mysql.proc: expected column 'sql_mode' at position 14 to have type set('REAL_AS_FLOAT','PIPES_AS_CONCAT','ANSI_QUOTES','IGNORE_SPACE','IGNORE_BAD_TABLE_OPTIONS','ONLY_FULL_GROUP_BY','NO_UNSIGNED_SUBTRACTION','NO_DIR_IN_CREATE','POSTGRESQL','ORACLE','MSSQL','DB2','MAXDB','NO_KEY_OPTIONS','NO_TABLE_OPTIONS','NO_FIELD_OPTIONS','MYSQL323','MYSQL40','ANSI','NO_AUTO_VALUE_ON_ZERO','NO_BACKSLASH_ESCAPES','STRICT_TRANS_TABLES','STRICT_ALL_TABLES','NO_ZERO_IN_DATE','NO_ZERO_DATE','INVA
May 13 13:12:29 MediaNAS1 mysqld_safe[14112]: 2018-05-13 13:12:29 140562172942080 [ERROR] Incorrect definition of table mysql.event: expected column 'sql_mode' at position 14 to have type set('REAL_AS_FLOAT','PIPES_AS_CONCAT','ANSI_QUOTES','IGNORE_SPACE','IGNORE_BAD_TABLE_OPTIONS','ONLY_FULL_GROUP_BY','NO_UNSIGNED_SUBTRACTION','NO_DIR_IN_CREATE','POSTGRESQL','ORACLE','MSSQL','DB2','MAXDB','NO_KEY_OPTIONS','NO_TABLE_OPTIONS','NO_FIELD_OPTIONS','MYSQL323','MYSQL40','ANSI','NO_AUTO_VALUE_ON_ZERO','NO_BACKSLASH_ESCAPES','STRICT_TRANS_TABLES','STRICT_ALL_TABLES','NO_ZERO_IN_DATE','NO_ZERO_DATE','INVALID_DATES','ERROR_FOR_DIVISION_BY_ZERO','TRADITIONAL','NO_AUTO_CREATE_USER','HIGH_NOT_PRECEDENCE','NO_ENGINE_SUBSTITUTION','PAD_CHAR_TO_FULL_LENGTH'), found type set('REAL_AS_FLOAT','PIPES_AS_CONCAT','ANSI_QUOTES','IGNORE_SPACE','NOT_USED','ONLY_FULL_GROUP_BY','NO_UNSIGNED_SUBTRACTION','NO_DIR_IN_CREATE','POSTGRESQL','ORACLE','MSSQL','DB2','MAXDB','NO_KEY_OPTIONS','NO_TABLE_OPTIONS','NO_FIELD_OPTIONS','MYSQL323','MYSQL40','A
May 13 13:12:29 MediaNAS1 mysqld_safe[14112]: NSI','NO_AUTO_VALUE_ON_ZERO','NO_BACKSLASH_ESCAPES','STRICT_TRANS_TABLES','STRICT_A
May 13 13:12:29 MediaNAS1 mysqld_safe[14112]: ERROR: 1136 Column count doesn't match value count at row 1
May 13 13:12:29 MediaNAS1 mysqld_safe[14112]: 2018-05-13 13:12:29 140562173366848 [ERROR] Aborting
May 13 13:12:29 MediaNAS1 mysqld_safe[14112]:
May 13 13:12:32 MediaNAS1 mysqld_safe[14112]:
May 13 13:12:32 MediaNAS1 mysqld_safe[14112]: Installation of system tables failed! Examine the logs in
May 13 13:12:32 MediaNAS1 mysqld_safe[14112]: /media/de8655aa-134d-46d5-ace3-25f29c9897fa/mysql_data for more information.
May 13 13:12:32 MediaNAS1 mysqld_safe[14112]:
May 13 13:12:32 MediaNAS1 mysqld_safe[14112]: The problem could be conflicting information in an external
May 13 13:12:32 MediaNAS1 mysqld_safe[14112]: my.cnf files. You can ignore these by doing:
May 13 13:12:32 MediaNAS1 mysqld_safe[14112]:
May 13 13:12:32 MediaNAS1 mysqld_safe[14112]: shell> /usr/scripts/scripts/mysql_install_db --defaults-file=~/.my.cnf
May 13 13:12:32 MediaNAS1 mysqld_safe[14112]:
May 13 13:12:32 MediaNAS1 mysqld_safe[14112]: You can also try to start the mysqld daemon with:
May 13 13:12:32 MediaNAS1 mysqld_safe[14112]:
May 13 13:12:32 MediaNAS1 mysqld_safe[14112]: shell> /usr/sbin/mysqld --skip-grant --general-log &
May 13 13:12:32 MediaNAS1 mysqld_safe[14112]:
May 13 13:12:32 MediaNAS1 mysqld_safe[14112]: and use the command line tool /usr/bin/mysql
May 13 13:12:32 MediaNAS1 mysqld_safe[14112]: to connect to the mysql database and look at the grant tables:
May 13 13:12:32 MediaNAS1 mysqld_safe[14112]:
May 13 13:12:32 MediaNAS1 mysqld_safe[14112]: shell> /usr/bin/mysql -u root mysql
May 13 13:12:32 MediaNAS1 mysqld_safe[14112]: mysql> show tables;
May 13 13:12:32 MediaNAS1 mysqld_safe[14112]:
May 13 13:12:32 MediaNAS1 mysqld_safe[14112]: Try 'mysqld --help' if you have problems with paths. Using
May 13 13:12:32 MediaNAS1 mysqld_safe[14112]: --general-log gives you a log in /media/de8655aa-134d-46d5-ace3-25f29c9897fa/mysql_data that may be helpful.