[MCOL-1185] configAlarm error: Oam::setAlarmConfig: error opening file /usr/local/mariadb/columnstore/etc/AlarmConfig.xml: Permission denied Created: 2018-01-30  Updated: 2023-10-26  Resolved: 2018-02-07

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

Type: Bug Priority: Major
Reporter: David Hill (Inactive) Assignee: Daniel Lee (Inactive)
Resolution: Fixed Votes: 1
Labels: None
Environment:

amazon 2um 3pm ebs system

Sprint: 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

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

with the change to send all alarm request to procmgr, also change to make it a single threaded process. the mulit-threaded processing was still causing the alarm config file to be corrupted...

system looks like it can keep up with it being single threaded stop/start system is the time where the most alarms are generated... doing a soak test now

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

fixed with pull request

fixed with this pull request

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

test, i hada scripted that would continuuall do a restartsystem and monitored error logs to make sure the error opening error msg wasnt issued.

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

fix

1 all alarm set/clear request sent to procmgr
2 procmgr now has a dedicated port to receive and serially process alarm request. this will prevent the file corruption issue

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

Build verified: Github source

1.1.3-1
[root@localhost ~]# cat mariadb-columnstore-1.1.3-1-centos7.x86_64.bin.tar.gz.txt
/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 ffcc4e94ccd07b6bbdfc47531c4c2f065f3fab47
Merge: 05431bf 3fb5dde
Author: benthompson15 <ben.thompson@mariadb.com>
Date: Mon Feb 5 22:37:05 2018 -0600
Merge pull request #398 from mariadb-corporation/statuscontrol-fix
add ProcStatusControl to postConfigure setup

Verified mentioned file has write permission. Also performed system restarted few times.

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