Fail to upgrade mcs from 1.1.7 to 1.2.3

 rpm -ivh mariadb-columnstore-*1.2.3*.rpm

Preparing...                          ################################# [100%]

Updating / installing...

   1:mariadb-columnstore-common-1.2.3-################################# [ 10%]

   2:mariadb-columnstore-libs-1.2.3-1 ################################# [ 20%]

   3:mariadb-columnstore-client-1.2.3-################################# [ 30%]

   4:mariadb-columnstore-server-1.2.3-################################# [ 40%]

   5:mariadb-columnstore-shared-1.2.3-################################# [ 50%]

   6:mariadb-columnstore-platform-1.2.################################# [ 60%]

The next step is:

If installing on a pm1 node using non-distributed install

/usr/local/mariadb/columnstore/bin/postConfigure

If installing on a pm1 node using distributed install

/usr/local/mariadb/columnstore/bin/postConfigure -d

If installing on a non-pm1 using the non-distributed option:

/usr/local/mariadb/columnstore/bin/columnstore start

   7:mariadb-columnstore-gssapi-server################################# [ 70%]

   8:mariadb-columnstore-rocksdb-engin################################# [ 80%]

   9:mariadb-columnstore-tokudb-engine################################# [ 90%]

  10:mariadb-columnstore-storage-engin################################# [100%]

[root@pm1 ~]# /usr/local/mariadb/columnstore/bin/postConfigure -du

   ERROR: Invalid Argument = -du

   Usage: postConfigure [-h][-c][-u][-p][-qs][-qm][-qa][-port][-i][-n][-d][-sn][-pm-ip-addrs][-um-ip-addrs][-pm-count][-um-count][-x][-xr][-numBlocksPct][-totalUmMemory]

[root@pm1 ~]# /usr/local/mariadb/columnstore/bin/postConfigure -d -u

This is the MariaDB ColumnStore System Configuration and Installation tool.

It will Configure the MariaDB ColumnStore System and will perform a Package

Installation of all of the Servers within the System that is being configured.

IMPORTANT: This tool requires to run on the Performance Module #1

With the no-Prompting Option being specified, you will be required to have the following:

 1. Root user ssh keys setup between all nodes in the system or

    use the password command line option.

 2. A Configure File to use to retrieve configure data, default to Columnstore.xml.rpmsave

    or use the '-c' option to point to a configuration file.

The MariaDB ColumnStore Configuration Data is taken from /usr/local/mariadb/columnstore/etc/Columnstore.xml.rpmsave

Do you want to utilize the configuration data from the saved copy? [y,n]  >

NOTE: my.cnf file was upgraded based on my.cnf.rpmsave

===== Setup System Server Type Configuration =====

There are 2 options when configuring the System Server Type: single and multi

  'single'  - Single-Server install is used when there will only be 1 server configured

              on the system. It can also be used for production systems, if the plan is

              to stay single-server.

  'multi'   - Multi-Server install is used when you want to configure multiple servers now or

              in the future. With Multi-Server install, you can still configure just 1 server

              now and add on addition servers/modules in the future.

Select the type of System Server install [1=single, 2=multi] (2) >

===== Setup System Module Type Configuration =====

There are 2 options when configuring the System Module Type: separate and combined

  'separate' - User and Performance functionality on separate servers.

  'combined' - User and Performance functionality on the same server

Select the type of System Module Install [1=separate, 2=combined] (1) >

Seperate Server Installation will be performed.

NOTE: Local Query Feature allows the ability to query data from a single Performance

      Module. Check MariaDB ColumnStore Admin Guide for additional information.

Enable Local Query feature? [y,n] (n) >

NOTE: The MariaDB ColumnStore Schema Sync feature will replicate all of the

      schemas and InnoDB tables across the User Module nodes. This feature can be enabled

      or disabled, for example, if you wish to configure your own replication post installation.

MariaDB ColumnStore Schema Sync feature is Enabled, do you want to leave enabled? [y,n] (y) >

NOTE: MariaDB ColumnStore Replication Feature is enabled

Enter System Name (columnstore-1) >

===== Storage Configuration = internal =====

===== Setup Memory Configuration =====

NOTE: Using previous configuration setting for 'NumBlocksPct' = 70%

      Using previous configuration setting for 'TotalUmMemory' = 50%

===== Setup the Module Configuration =====

----- User Module Configuration -----

Enter number of User Modules [1,1024] (1) >

*** User Module #1 Configuration ***

Enter Nic Interface #1 Host Name (um1) >

Enter Nic Interface #1 IP Address or hostname of um1 (172.20.2.206) >

Enter Nic Interface #2 Host Name (unassigned) >

----- Performance Module Configuration -----

Enter number of Performance Modules [1,1024] (1) >

*** Parent OAM Module Performance Module #1 Configuration ***

Enter Nic Interface #1 Host Name (pm1.xentio.lan) >

Enter Nic Interface #1 IP Address or hostname of pm1.xentio.lan (172.20.2.205) >

Enter Nic Interface #2 Host Name (unassigned) >

Enter the list (Nx,Ny,Nz) or range (Nx-Nz) of DBRoot IDs assigned to module 'pm1' (1) >

Next step is to enter the password to access the other Servers.

This is either user password or you can default to using a ssh key

If using a user password, the password needs to be the same on all Servers.

Enter password, hit 'enter' to default to using a ssh key, or 'exit' >

===== System Installation =====

System Configuration is complete.

Performing System Installation.

Performing a MariaDB ColumnStore System install using RPM packages

located in the /root directory.

----- Performing Install on 'um1 / um1' -----

Install log file is located here: /tmp/columnstore_tmp_files/um1_rpm_install.log

MariaDB ColumnStore Package being installed, please wait ...  DONE

===== Checking MariaDB ColumnStore System Logging Functionality =====

The MariaDB ColumnStore system logging is setup and working on local server

===== MariaDB ColumnStore System Startup =====

System Configuration is complete.

Performing System Installation.

----- Starting MariaDB ColumnStore on local server -----

MariaDB ColumnStore successfully started

MariaDB ColumnStore Database Platform Starting, please wait .......................

TIMEOUT: ProcMon not responding to getSystemStatus FAILED

 IMPORTANT: There was a system startup failed, once issue has been resolved, rerun postConfigure

MariaDB ColumnStore System failed to start, check log files in /var/log/mariadb/columnstore

Enter the following command to define MariaDB ColumnStore Alias Commands

. /etc/profile.d/columnstoreAlias.sh

Enter 'mcsmysql' to access the MariaDB ColumnStore SQL console

Enter 'mcsadmin' to access the MariaDB ColumnStore Admin console

NOTE: The MariaDB ColumnStore Alias Commands are in /etc/profile.d/columnstoreAlias

Feb 22 14:45:01 um1 ProcessMonitor[31610]: 01.827897 |0|0|0| D 18 CAL0000: /usr/local/mariadb/columnstore/bin/module_installer.sh  --installdir=/usr/local/mariadb/columnstore --module=um  > /tmp/columnstore_tmp_files/module_installer.log 2>&1

Feb 22 14:45:14 um1 ProcessMonitor[31610]: 14.781415 |0|0|0| C 18 CAL0000: module_installer.sh error, exiting..., return code = 256

[root@um1 ~]# cat /tmp/columnstore_tmp_files/module_installer.log

Run Upgrade on my.cnf on Module

Run Mysql Port update on my.cnf on Module

Run post-mysqld-install

ERROR: post-mysqld-install failed: check /tmp/columnstore_tmp_files/post-mysqld-install.log

/usr/local/mariadb/columnstore/bin/post-mysqld-install

2019-02-22 14:55:17 7 [ERROR] Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 100222, now running 100311. Please use mysql_upgrade to fix this error

2019-02-22 14:55:17 7 [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','EMPTY_STRING_IS_NULL','SIMULTANEOUS_ASSIGNMENT'), found 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_VALU

ERROR: 1136  Column count doesn't match value count at row 1

2019-02-22 14:55:17 0 [ERROR] Aborting