Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Won't Do
-
1.2.2
-
None
-
ubuntu 16.04
Linux 4.4.0-87-generic #110-Ubuntu SMP Tue Jul 18 12:55:35 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Description
mcsadmin> getAlarmSummary
getalarmsummary Tue Dec 11 04:50:05 2018
Active Alarm Counts: Critical = 1, Major = 0, Minor = 0, Warning = 0, Info = 0
mcsadmin> getActiveAlarms
getactivealarms Tue Dec 11 04:50:28 2018
Active Alarm List:
AlarmID = 30
Brief Description = CONN_FAILURE
Alarm Severity = CRITICAL
Time Issued = Fri Dec 7 09:03:51 2018
Reporting Module = pm1
Reporting Process = DMLProc
Reported Device = 127.0.0.1 PrimProc
2018-12-11T04:43:12.705281-07:00 labsdb162.lab.llnw.net controllernode[348652]: 12.705229 |0|0|0| E 29 CAL0000: DBRM: error: SessionManager::getSystemState() failed (network)
After SQL is run all logs (debug to crit)get spammed with PrimProc messages filling up file system.
restart of environment from debug log including start of the PrimProc messages attached
30 minutes after restart
-rwxr-xr-x 1 root root 2848 Dec 11 04:44 alarm.log
-rwxr-xr-x 1 syslog adm 203711653 Dec 11 05:00 crit.log
-rwxr-xr-x 1 syslog adm 203763710 Dec 11 05:00 debug.log
-rwxr-xr-x 1 syslog adm 203711828 Dec 11 05:00 err.log
-rwxr-xr-x 1 syslog adm 203714678 Dec 11 05:00 info.log
-rwxr-xr-x 1 root root 544 Dec 11 05:06 mcsadmin.log
-rwxr-xr-x 1 syslog adm 203712358 Dec 11 05:00 warning.log