[MCOL-1204] postConfigure install fails - System Catalog Create Failure Created: 2018-02-06  Updated: 2018-02-16  Resolved: 2018-02-06

Status: Closed
Project: MariaDB ColumnStore
Component/s: installation
Affects Version/s: 1.1.3
Fix Version/s: Icebox

Type: Bug Priority: Critical
Reporter: David Hill (Inactive) Assignee: David Hill (Inactive)
Resolution: Not a Bug Votes: 0
Labels: None
Environment:

google 2pm combo system centos 7 feb 6 build


Sprint: 2018-03

 Description   

performing a new install on a 2pm combco system and postConfigure errors out with System Catalog Create Failure.

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

MariaDB ColumnStore successfully started

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

System Catalog Create Failure
Check latest log file in /tmp/dbbuilder.log.*
IMPORTANT: Once issue has been resolved, rerun postConfigure

[root@centos-7-yum-pm1 bin]# ./dbrmctl status
DBRM is currently Read Only!

[root@centos-7-yum-pm1 tmp]# cat dbbuilder.status
FAILED: buildOption=7
[root@centos-7-yum-pm1 tmp]# cat dbbuilder.log
Creating System Catalog...

Creating SYSTABLE
---------------------------------------
Creating TableName column OID: 1001
Build system catalog was not successful. Creating TableName column OID: 1001 a BRM Allocate extent error. [BRM error status: DBRM is in READ-ONLY mode]
[root@centos-7-yum-pm1 tmp]#

[root@centos-7-yum-pm1 dbrm]# ll
total 2060
rw-rw-rw 1 root root 5 Feb 6 15:31 BRM_saves_journal
rw-rw-rw 1 root root 2099202 Feb 6 15:31 oidbitmap
rw-rw-r- 1 root root 12 Feb 6 15:31 SMTxnID

root@centos-7-yum-pm1 bin]# ma getsystemi
getsysteminfo Tue Feb 6 15:49:38 2018

System columnstore-1

System and Module statuses

Component Status Last Status Change
------------ -------------------------- ------------------------
System ACTIVE Tue Feb 6 15:31:50 2018

Module pm1 ACTIVE Tue Feb 6 15:31:41 2018
Module pm2 ACTIVE Tue Feb 6 15:31:32 2018

Active Parent OAM Performance Module is 'pm1'
Primary Front-End MariaDB ColumnStore Module is 'pm1'
MariaDB ColumnStore Replication Feature is enabled

MariaDB ColumnStore Process statuses

Process Module Status Last Status Change Process ID
------------------ ------ --------------- ------------------------ ----------
ProcessMonitor pm1 ACTIVE Tue Feb 6 15:30:02 2018 3273
ProcessManager pm1 ACTIVE Tue Feb 6 15:30:08 2018 3367
DBRMControllerNode pm1 ACTIVE Tue Feb 6 15:31:08 2018 4619
ServerMonitor pm1 ACTIVE Tue Feb 6 15:31:08 2018 4639
DBRMWorkerNode pm1 ACTIVE Tue Feb 6 15:31:11 2018 4678
DecomSvr pm1 ACTIVE Tue Feb 6 15:31:12 2018 4745
PrimProc pm1 ACTIVE Tue Feb 6 15:31:16 2018 4819
ExeMgr pm1 ACTIVE Tue Feb 6 15:31:29 2018 7004
WriteEngineServer pm1 ACTIVE Tue Feb 6 15:31:34 2018 7108
DDLProc pm1 ACTIVE Tue Feb 6 15:31:40 2018 7502
DMLProc pm1 ACTIVE Tue Feb 6 15:31:50 2018 8139
mysqld pm1 ACTIVE Tue Feb 6 15:31:43 2018 4543

ProcessMonitor pm2 ACTIVE Tue Feb 6 15:30:56 2018 1946
ProcessManager pm2 HOT_STANDBY Tue Feb 6 15:31:02 2018 2042
DBRMControllerNode pm2 COLD_STANDBY Tue Feb 6 15:31:24 2018
ServerMonitor pm2 ACTIVE Tue Feb 6 15:31:12 2018 2347
DBRMWorkerNode pm2 ACTIVE Tue Feb 6 15:31:18 2018 2372
DecomSvr pm2 ACTIVE Tue Feb 6 15:31:19 2018 2407
PrimProc pm2 ACTIVE Tue Feb 6 15:31:23 2018 2419
ExeMgr pm2 ACTIVE Tue Feb 6 15:31:28 2018 2651
WriteEngineServer pm2 ACTIVE Tue Feb 6 15:31:32 2018 2693
DDLProc pm2 COLD_STANDBY Tue Feb 6 15:31:32 2018
DMLProc pm2 COLD_STANDBY Tue Feb 6 15:31:32 2018
mysqld pm2 ACTIVE Tue Feb 6 15:31:26 2018 2291

Active Alarm Counts: Critical = 1, Major = 0, Minor = 0, Warning = 0, Info = 0



 Comments   
Comment by David Hill (Inactive) [ 2018-02-06 ]

discovered the problem was related to the system not being correctly cleaned up before a new install was done. pm2 still had a set of rpm packages installed and had some process running.
I was doing a binary package install from pm1...

on the second install, I installed the rpm packaged from pm2 and delete the /usr/local/mariadb on both directories, then successfully reinstalled from scratch...

Generated at Thu Feb 08 02:26:59 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.