[MCOL-1190] Process ID of mysqld is missed in the output of mcsadmin getSystemInfo Created: 2018-02-01  Updated: 2023-10-26  Resolved: 2018-02-13

Status: Closed
Project: MariaDB ColumnStore
Component/s: None
Affects Version/s: 1.1.2
Fix Version/s: 1.1.3

Type: Bug Priority: Minor
Reporter: Zdravelina Sokolovska (Inactive) Assignee: Daniel Lee (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Environment:

MCS run on VMs, Multi Server ColumnStore System UM1-PM1 ;guest OS RHEL 7.4


Issue Links:
Relates
relates to MCOL-1193 Last Status Change of mysqld is not ... Closed
Sprint: 2018-04

 Description   

Process ID of mysqld is missed in the output of mcsadmin getSystemInfo

[root@um1 ~]#  mcsadmin getSystemInfo
 
 
 
WARNING: running on non Parent OAM Module, can't make configuration changes in this session.
 
         Access Console from 'pm1' if you need to make changes.
 
 
 
getsysteminfo   Thu Feb  1 17:11:31 2018
 
 
 
System cs-1.1.0
 
 
 
System and Module statuses
 
 
 
Component     Status                       Last Status Change
 
------------  --------------------------   ------------------------
 
System        ACTIVE                       Mon Jan 29 01:38:21 2018
 
 
 
Module um1    ACTIVE                       Mon Jan 29 01:38:19 2018
 
Module pm1    ACTIVE                       Mon Jan 29 01:38:09 2018
 
 
 
Active Parent OAM Performance Module is 'pm1'
 
MariaDB ColumnStore Replication Feature is enabled
 
 
 
 
 
MariaDB ColumnStore Process statuses
 
 
 
Process             Module    Status            Last Status Change        Process ID
 
------------------  ------    ---------------   ------------------------  ----------
 
ProcessMonitor      um1       ACTIVE            Mon Jan 29 01:37:54 2018        1020
 
ServerMonitor       um1       ACTIVE            Mon Jan 29 01:38:06 2018        1334
 
DBRMWorkerNode      um1       ACTIVE            Mon Jan 29 01:38:07 2018        1359
 
ExeMgr              um1       ACTIVE            Mon Jan 29 01:38:12 2018        1563
 
DDLProc             um1       ACTIVE            Mon Jan 29 01:38:16 2018        1574
 
DMLProc             um1       ACTIVE            Mon Jan 29 01:38:20 2018        1583
 
mysqld              um1       ACTIVE            Mon Jan 29 01:38:10 2018
 
 
 
ProcessMonitor      pm1       ACTIVE            Mon Jan 29 01:37:43 2018        1014
 
ProcessManager      pm1       ACTIVE            Mon Jan 29 01:37:49 2018        1128
 
DBRMControllerNode  pm1       ACTIVE            Mon Jan 29 01:38:01 2018        1384
 
ServerMonitor       pm1       ACTIVE            Mon Jan 29 01:38:03 2018        1400
 
DBRMWorkerNode      pm1       ACTIVE            Mon Jan 29 01:38:03 2018        1435
 
DecomSvr            pm1       ACTIVE            Mon Jan 29 01:38:07 2018        1549
 
PrimProc            pm1       ACTIVE            Mon Jan 29 01:38:09 2018        1602
 
WriteEngineServer   pm1       ACTIVE            Mon Jan 29 01:38:10 2018        1638
 
 
 
Active Alarm Counts: Critical = 0, Major = 0, Minor = 0, Warning = 0, Info = 0
 



[root@pm1 ~]#  mcsadmin getSystemInfo
 
getsysteminfo   Thu Feb  1 17:16:16 2018
 
 
 
System cs-1.1.0
 
 
 
System and Module statuses
 
 
 
Component     Status                       Last Status Change
 
------------  --------------------------   ------------------------
 
System        ACTIVE                       Mon Jan 29 01:38:21 2018
 
 
 
Module um1    ACTIVE                       Mon Jan 29 01:38:19 2018
 
Module pm1    ACTIVE                       Mon Jan 29 01:38:09 2018
 
 
 
Active Parent OAM Performance Module is 'pm1'
 
MariaDB ColumnStore Replication Feature is enabled
 
 
 
 
 
MariaDB ColumnStore Process statuses
 
 
 
Process             Module    Status            Last Status Change        Process ID
 
------------------  ------    ---------------   ------------------------  ----------
 
ProcessMonitor      um1       ACTIVE            Mon Jan 29 01:37:54 2018        1020
 
ServerMonitor       um1       ACTIVE            Mon Jan 29 01:38:06 2018        1334
 
DBRMWorkerNode      um1       ACTIVE            Mon Jan 29 01:38:07 2018        1359
 
ExeMgr              um1       ACTIVE            Mon Jan 29 01:38:12 2018        1563
 
DDLProc             um1       ACTIVE            Mon Jan 29 01:38:16 2018        1574
 
DMLProc             um1       ACTIVE            Mon Jan 29 01:38:20 2018        1583
 
mysqld              um1       ACTIVE            Mon Jan 29 01:38:10 2018
 
 
 
ProcessMonitor      pm1       ACTIVE            Mon Jan 29 01:37:43 2018        1014
 
ProcessManager      pm1       ACTIVE            Mon Jan 29 01:37:49 2018        1128
 
DBRMControllerNode  pm1       ACTIVE            Mon Jan 29 01:38:01 2018        1384
 
ServerMonitor       pm1       ACTIVE            Mon Jan 29 01:38:03 2018        1400
 
DBRMWorkerNode      pm1       ACTIVE            Mon Jan 29 01:38:03 2018        1435
 
DecomSvr            pm1       ACTIVE            Mon Jan 29 01:38:07 2018        1549
 
PrimProc            pm1       ACTIVE            Mon Jan 29 01:38:09 2018        1602
 
WriteEngineServer   pm1       ACTIVE            Mon Jan 29 01:38:10 2018        1638
 
 
 
Active Alarm Counts: Critical = 0, Major = 0, Minor = 0, Warning = 0, Info = 0
 
[root@pm1 ~]#



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

the mysqld pid is taken from the pid file. please check if this file exist.

..mariadb/columnstore/mysql/db/'hostname'.pid

also can you check the status and post the output please..

..mariadb/columnstore/mysql/mysql-Columnstore status

Comment by Zdravelina Sokolovska (Inactive) [ 2018-02-01 ]

mysqld pid is available from both pid file and mysql-Columnstore status

[root@um1 ~]# cat  /usr/local/mariadb/columnstore/mysql/db/um1.xentio.lan.pid
 
13970


[root@um1 ~]# /usr/local/mariadb/columnstore/mysql/mysql-Columnstore status
 
 SUCCESS! MySQL running (13970)

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

have issue reproduced on in house system, checking on a fix..

mcsadmin> getsystemi
getsysteminfo Mon Feb 12 15:56:19 2018

System 1.1.3

System and Module statuses

Component Status Last Status Change
------------ -------------------------- ------------------------
System ACTIVE Mon Feb 12 15:55:59 2018

Module um1 ACTIVE Mon Feb 12 15:55:56 2018
Module pm1 ACTIVE Mon Feb 12 15:55:39 2018
Module pm2 ACTIVE Mon Feb 12 15:55:46 2018

Active Parent OAM Performance Module is 'pm1'
MariaDB ColumnStore Replication Feature is enabled

MariaDB ColumnStore Process statuses

Process Module Status Last Status Change Process ID
------------------ ------ --------------- ------------------------ ----------
ProcessMonitor um1 ACTIVE Mon Feb 12 15:55:16 2018 959
ServerMonitor um1 ACTIVE Mon Feb 12 15:55:36 2018 3086
DBRMWorkerNode um1 ACTIVE Mon Feb 12 15:55:36 2018 3112
ExeMgr um1 ACTIVE Mon Feb 12 15:55:49 2018 4684
DDLProc um1 ACTIVE Mon Feb 12 15:55:53 2018 4697
DMLProc um1 ACTIVE Mon Feb 12 15:55:57 2018 4707
mysqld um1 ACTIVE Mon Feb 12 15:55:47 2018

ProcessMonitor pm1 ACTIVE Mon Feb 12 15:54:55 2018 828
ProcessManager pm1 ACTIVE Mon Feb 12 15:55:01 2018 1358
DBRMControllerNode pm1 ACTIVE Mon Feb 12 15:55:31 2018 2073
ServerMonitor pm1 ACTIVE Mon Feb 12 15:55:33 2018 2089
DBRMWorkerNode pm1 ACTIVE Mon Feb 12 15:55:33 2018 2120
DecomSvr pm1 ACTIVE Mon Feb 12 15:55:37 2018 2267
PrimProc pm1 ACTIVE Mon Feb 12 15:55:39 2018 2371
WriteEngineServer pm1 ACTIVE Mon Feb 12 15:55:40 2018 2430

ProcessMonitor pm2 ACTIVE Mon Feb 12 15:55:25 2018 1219
ProcessManager pm2 HOT_STANDBY Mon Feb 12 15:55:26 2018 3777
DBRMControllerNode pm2 COLD_STANDBY Mon Feb 12 15:55:37 2018
ServerMonitor pm2 ACTIVE Mon Feb 12 15:55:40 2018 3807
DBRMWorkerNode pm2 ACTIVE Mon Feb 12 15:55:40 2018 3835
DecomSvr pm2 ACTIVE Mon Feb 12 15:55:44 2018 3847
PrimProc pm2 ACTIVE Mon Feb 12 15:55:46 2018 3857
WriteEngineServer pm2 ACTIVE Mon Feb 12 15:55:47 2018 3865

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

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

discovered a code bug... looks like issue is only happening on um /pm separate systems...
testing fix out now..

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

test on separate system.. make sure a mysqld pid shows up after install, restsrtsyetm, reboot, and mysqld restart:

./mysql-Columnstore restart
Shutting down MySQL.. SUCCESS!
Starting MySQL.. SUCCESS!
[root@ip-172-30-0-59 mysql]# pwd
/usr/local/mariadb/columnstore/mysql

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

https://github.com/mariadb-corporation/mariadb-columnstore-engine/pull/40

Comment by Daniel Lee (Inactive) [ 2018-02-13 ]

Build verified: Github source 1.1.3-1

/root/columnstore/mariadb-columnstore-server
commit e5499e513d88a3dfefbe9a356e20a1bceb1bde38
Merge: 99cdb0a 4840a43
Author: david hill <david.hill@mariadb.com>
Date: Wed Jan 31 16:53:52 2018 -0600

Merge pull request #92 from mariadb-corporation/MCOL-1152

MCOL-1152: Change the debian package names.

/root/columnstore/mariadb-columnstore-server/mariadb-columnstore-engine
commit d45dc5f33e9d14c845aab0c586eb7280a537d3d5
Merge: d0ceeaa 9cb9934
Author: benthompson15 <ben.thompson@mariadb.com>
Date: Mon Feb 12 14:04:38 2018 -0600

Merge pull request #403 from mariadb-corporation/MCOL-1190

MCOL-1190 - code fix, mysql not being monitored on seperate um/pm sys…

mcsadmin> getprocessstatus
getprocessstatus Tue Feb 13 16:19:39 2018

MariaDB ColumnStore Process statuses

Process Module Status Last Status Change Process ID
------------------ ------ --------------- ------------------------ ----------
ProcessMonitor um1 ACTIVE Tue Feb 13 15:30:35 2018 15652
ServerMonitor um1 ACTIVE Tue Feb 13 15:30:50 2018 15997
DBRMWorkerNode um1 ACTIVE Tue Feb 13 15:30:50 2018 16010
ExeMgr um1 ACTIVE Tue Feb 13 15:31:02 2018 17384
DDLProc um1 ACTIVE Tue Feb 13 15:31:06 2018 17397
DMLProc um1 ACTIVE Tue Feb 13 15:31:11 2018 17431
mysqld um1 ACTIVE Tue Feb 13 15:31:06 2018 15956

ProcessMonitor pm1 ACTIVE Tue Feb 13 15:29:53 2018 15294
ProcessManager pm1 ACTIVE Tue Feb 13 15:29:59 2018 15363
DBRMControllerNode pm1 ACTIVE Tue Feb 13 15:30:42 2018 16196
ServerMonitor pm1 ACTIVE Tue Feb 13 15:30:44 2018 16212
DBRMWorkerNode pm1 ACTIVE Tue Feb 13 15:30:44 2018 16236
DecomSvr pm1 ACTIVE Tue Feb 13 15:30:48 2018 16376
PrimProc pm1 ACTIVE Tue Feb 13 15:30:50 2018 16453
WriteEngineServer pm1 ACTIVE Tue Feb 13 15:30:51 2018 16518

ProcessMonitor pm2 ACTIVE Tue Feb 13 15:30:34 2018 15197
ProcessManager pm2 HOT_STANDBY Tue Feb 13 15:30:35 2018 15239
DBRMControllerNode pm2 COLD_STANDBY Tue Feb 13 15:30:50 2018
ServerMonitor pm2 ACTIVE Tue Feb 13 15:30:53 2018 15271
DBRMWorkerNode pm2 ACTIVE Tue Feb 13 15:30:53 2018 15284
DecomSvr pm2 ACTIVE Tue Feb 13 15:30:57 2018 15298
PrimProc pm2 ACTIVE Tue Feb 13 15:30:59 2018 15306
WriteEngineServer pm2 ACTIVE Tue Feb 13 15:31:00 2018 15314

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