Amazon AMi multi-node system didnt successfully restart after a stop/start

during the fixing of MCOL-422, discovered this problem where the system doesn't come back ACTIVE after a stop/start of the instances on a multi-node system

Component Status Last Status Change
------------ -------------------------- ------------------------
System FAILED Sun Dec 4 23:43:37 2016

Module um1 MAN_OFFLINE Sun Dec 4 23:43:36 2016
Module pm1 ACTIVE Sun Dec 4 23:43:41 2016
Module pm2 FAILED Sun Dec 4 23:43:35 2016

Active Parent OAM Performance Module is 'pm1'

MariaDB Columnstore Process statuses

Process Module Status Last Status Change Process ID
------------------ ------ --------------- ------------------------ ----------
ProcessMonitor um1 ACTIVE Sun Dec 4 23:43:16 2016 1306
ServerMonitor um1 ACTIVE Sun Dec 4 23:43:32 2016 8207
DBRMWorkerNode um1 ACTIVE Sun Dec 4 23:43:36 2016 8769
ExeMgr um1 INITIAL
DDLProc um1 INITIAL
DMLProc um1 INITIAL
mysqld um1 ACTIVE Sun Dec 4 23:43:28 2016

ProcessMonitor pm1 ACTIVE Sun Dec 4 23:43:05 2016 1437
ProcessManager pm1 ACTIVE Sun Dec 4 23:43:10 2016 4093
DBRMControllerNode pm1 ACTIVE Sun Dec 4 23:43:33 2016 9262
ServerMonitor pm1 ACTIVE Sun Dec 4 23:43:35 2016 9431
DBRMWorkerNode pm1 ACTIVE Sun Dec 4 23:43:35 2016 10128
DecomSvr pm1 ACTIVE Sun Dec 4 23:43:39 2016 14411
PrimProc pm1 ACTIVE Sun Dec 4 23:43:41 2016 14528
WriteEngineServer pm1 ACTIVE Sun Dec 4 23:43:42 2016 14608

ProcessMonitor pm2 ACTIVE Sun Dec 4 23:45:15 2016 11675
ProcessManager pm2 HOT_STANDBY Sun Dec 4 23:44:56 2016 11389
DBRMControllerNode pm2 AUTO_OFFLINE Sun Dec 4 23:46:00 2016
ServerMonitor pm2 INITIAL
DBRMWorkerNode pm2 INITIAL
DecomSvr pm2 INITIAL
PrimProc pm2 INITIAL
WriteEngineServer pm2 INITIAL