System mycolumnstore1

System and Module statuses

Component Status Last Status Change
------------ -------------------------- ------------------------
System MAN_INIT Mon Jun 26 19:22:27 2017

Module um1 MAN_DISABLED Mon Jun 26 18:50:40 2017
Module pm1 ACTIVE Mon Jun 26 19:22:43 2017
Module pm2 ACTIVE Mon Jun 26 19:22:45 2017
Module pm3 ACTIVE Mon Jun 26 19:22:50 2017

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 Jun 26 18:50:48 2017 1375
ServerMonitor um1 ACTIVE Mon Jun 26 18:50:49 2017 3677
DBRMWorkerNode um1 MAN_OFFLINE Mon Jun 26 18:55:03 2017
ExeMgr um1 MAN_OFFLINE Mon Jun 26 18:55:01 2017
DDLProc um1 MAN_OFFLINE Mon Jun 26 18:55:00 2017
DMLProc um1 MAN_OFFLINE Mon Jun 26 18:54:59 2017
mysqld um1 MAN_OFFLINE Mon Jun 26 18:50:41 2017

ProcessMonitor pm1 ACTIVE Mon Jun 26 18:48:56 2017 1290
ProcessManager pm1 ACTIVE Mon Jun 26 18:49:02 2017 1942
DBRMControllerNode pm1 ACTIVE Mon Jun 26 19:22:35 2017 8231
ServerMonitor pm1 ACTIVE Mon Jun 26 19:22:37 2017 8252
DBRMWorkerNode pm1 ACTIVE Mon Jun 26 19:22:37 2017 8338
DecomSvr pm1 ACTIVE Mon Jun 26 19:22:41 2017 8518
PrimProc pm1 ACTIVE Mon Jun 26 19:22:43 2017 8655
WriteEngineServer pm1 ACTIVE Mon Jun 26 19:22:44 2017 8716

ProcessMonitor pm2 ACTIVE Mon Jun 26 18:49:11 2017 1274
ProcessManager pm2 HOT_STANDBY Mon Jun 26 19:22:30 2017 2413
DBRMControllerNode pm2 COLD_STANDBY Mon Jun 26 19:22:35 2017
ServerMonitor pm2 ACTIVE Mon Jun 26 19:22:38 2017 2474
DBRMWorkerNode pm2 ACTIVE Mon Jun 26 19:22:40 2017 2506
DecomSvr pm2 ACTIVE Mon Jun 26 19:22:43 2017 2521
PrimProc pm2 ACTIVE Mon Jun 26 19:22:46 2017 2534
WriteEngineServer pm2 ACTIVE Mon Jun 26 19:22:47 2017 2545

ProcessMonitor pm3 ACTIVE Mon Jun 26 18:50:51 2017 1322
ProcessManager pm3 COLD_STANDBY Mon Jun 26 19:22:40 2017
DBRMControllerNode pm3 COLD_STANDBY Mon Jun 26 19:22:40 2017
ServerMonitor pm3 ACTIVE Mon Jun 26 19:22:43 2017 1979
DBRMWorkerNode pm3 ACTIVE Mon Jun 26 19:22:44 2017 2011
DecomSvr pm3 ACTIVE Mon Jun 26 19:22:48 2017 2026
PrimProc pm3 ACTIVE Mon Jun 26 19:22:50 2017 2037
WriteEngineServer pm3 ACTIVE Mon Jun 26 19:22:51 2017 2048

Above is the current status of my UM and PM. I have created this issue when I accidently rebooted UM server without taking mariaDB down. Can you help me to restore UM server?

I am getting below error in err.log when I will restart services.

Jun 26 18:51:05 ip-172-31-7-171 ProcessMonitor[1375]: 05.165519 |0|0|0| C 18 CAL0000: DBRMWorkerNode/3709 failed to init in 20 seconds, force killing it so it can restart
Jun 26 18:51:10 ip-172-31-7-171 ProcessMonitor[1375]: 10.166697 |0|0|0| C 18 CAL0000: *****Calpont Process Restarting: DBRMWorkerNode, old PID = 3709
Jun 26 18:51:10 ip-172-31-7-171 ProcessMonitor[1375]: 10.176223 |0|0|0| E 18 CAL0000: EXCEPTION ERROR on getLocalDBRMID: no DBRM for module

Please help me as soon as possible.