Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
1.1.2
-
None
-
amazon 2um 3pm ebs system
-
2018-03
Description
customer reporting errors with Alarm Config file on UM1. Main concern is all alarms should be handled on the Parent Oam module, which is PM1. Need to investigate further.
Also what appears to be a communication error is the pretty much the same as the previous day:
Jan 29 06:21:18 mcs1-um1 alarmmanager[95751]: 18.213563 |0|0|0| E 11 CAL0000: configAlarm error: Oam::setAlarmConfig: error opening file /usr/local/mariadb/columnstore/etc/AlarmConfig.xml: Permission denied
Jan 29 06:43:03 mcs1-um1 alarmmanager[106915]: 03.066877 |0|0|0| E 11 CAL0000: configAlarm error: Oam::setAlarmConfig: error opening file /usr/local/mariadb/columnstore/etc/AlarmConfig.xml: Permission denied
Jan 30 01:33:59 mcs1-um1 alarmmanager[110546]: 59.117619 |0|0|0| E 11 CAL0000: configAlarm error: Oam::setAlarmConfig: error opening file /usr/local/mariadb/columnstore/etc/AlarmConfig.xml: Permission denied
Jan 30 05:34:52 mcs1-um1 alarmmanager[7498]: 52.529761 |0|0|0| E 11 CAL0000: configAlarm error: Oam::setAlarmConfig: error opening file /usr/local/mariadb/columnstore/etc/AlarmConfig.xml: Permission denied