Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Done
-
1.0.6
-
RHEL 7.1
Description
Process Module Status Last Status Change Process ID
------------------ ------ --------------- ------------------------ ----------
ProcessMonitor pm1 ACTIVE Fri Dec 23 12:07:34 2016 8590
ProcessManager pm1 ACTIVE Fri Dec 23 12:07:40 2016 8678
DBRMControllerNode pm1 FAILED Fri Dec 23 12:32:18 2016
ServerMonitor pm1 ACTIVE Fri Dec 23 12:32:21 2016 21483
DBRMWorkerNode pm1 MAN_INIT Fri Dec 23 15:38:49 2016 24937
DecomSvr pm1 ACTIVE Fri Dec 23 12:32:25 2016 21526
PrimProc pm1 MAN_INIT Fri Dec 23 15:39:04 2016 26834
ExeMgr pm1 INITIAL
WriteEngineServer pm1 INITIAL
DDLProc pm1 INITIAL
DMLProc pm1 INITIAL
mysqld pm1 ACTIVE Fri Dec 23 15:39:09 2016
Dec 23 15:51:18 awsmltdbprd03 ProcessMonitor[8590]: 18.961526 |0|0|0| D 18 CAL0000: Process location: /usr/local/mariadb/columnstore/bin/ExeMgr
Dec 23 15:51:18 awsmltdbprd03 ProcessMonitor[8590]: 18.962403 |0|0|0| D 18 CAL0000: Dependent process of PrimProc/pm1 is 2
Dec 23 15:51:18 awsmltdbprd03 ProcessMonitor[8590]: 18.963211 |0|0|0| D 18 CAL0000: Dependent Process is not in correct state, Failed Restoral
Dec 23 15:51:18 awsmltdbprd03 ProcessMonitor[8590]: 18.963285 |0|0|0| I 18 CAL0000: STARTALL: ACK back to ProcMgr, return status = 8
Dec 23 15:51:18 awsmltdbprd03 ProcessManager[8678]: 18.963401 |0|0|0| D 17 CAL0000: pm1 module failed to start!!
Dec 23 15:51:18 awsmltdbprd03 ProcessManager[8678]: 18.963453 |0|0|0| D 17 CAL0000: ACK received from 'pm1' Process-Monitor, return status = 8
Dec 23 15:51:18 awsmltdbprd03 ProcessManager[8678]: 18.964334 |0|0|0| D 17 CAL0000: Set Module pm1 State = 2
Dec 23 15:51:18 awsmltdbprd03 ProcessMonitor[8590]: 18.964619 |0|0|0| D 18 CAL0000: statusControl: REQUEST RECEIVED: Set Module pm1 State = MAN_INIT
Dec 23 15:51:18 awsmltdbprd03 ProcessManager[8678]: 18.965026 |0|0|0| D 17 CAL0000: sendMsgProcMon: Process module pm1
Dec 23 15:51:19 awsmltdbprd03 ProcessMonitor[8590]: 19.282644 |0|0|0| C 18 CAL0000: *****Calpont Process Restarting: DBRMWorkerNode, old PID = 19299
Dec 23 15:51:19 awsmltdbprd03 ProcessMonitor[8590]: 19.282767 |0|0|0| D 18 CAL0000: StatusUpdate of Process DBRMWorkerNode State = 1 PID = 0
Dec 23 15:51:19 awsmltdbprd03 ProcessMonitor[8590]: 19.282845 |0|0|0| C 18 CAL0000: *****Process continually dying, stopped trying to restore it: DBRMWorkerNode
Dec 23 15:51:19 awsmltdbprd03 ProcessMonitor[8590]: 19.283183 |0|0|0| D 18 CAL0000: Send SET Alarm ID 13 on device DBRMWorkerNode
Dec 23 15:51:19 awsmltdbprd03 snmpmanager[8590]: 19.284337 |0|0|0| E 11 CAL0000: configAlarm error: Config::parseDoc: error parsing config file /usr/local/mariadb/columnstore/etc/AlarmConfig.xml
Attachments
Issue Links
- relates to
-
MCOL-396 AlarmConfig.xml file zero'd out when pm server restarted locally
- Closed