09-24-2014 10:00 PM - edited 03-10-2019 10:03 PM
Hi All,
Recently detected ACS 5.4 having missing log messages and couldn't figure out what cause it. Would like to get some comment from whose ever that face this issue before.
Cisco Secure ACS - Alarm Notification |
Severity: Critical |
Alarm Name | ACS - System Errors | ||||||||||
Cause/Trigger | Alarm caused by ACS - System Errors threshold | ||||||||||
Alarm Details |
| ||||||||||
Report Links | |||||||||||
Generated On | 2014-09-25 06:02:00.0 |
10-20-2014 06:37 PM
Hi,
have you tried generate some log on 2014-09-25 06:02:00.0 ?
in my case, i already seen a log TACACS Accounting, which is missing the username value,
05-04-2016 07:32 AM
same issue here Version : 5.7.0.15.1 i've tried reboot both appliances, with no success
05-27-2016 01:41 AM
This missing log message alarm will come if logging recovery is enabled.
This logging recovery feature will be helpful in case log collector is down and ACS will try to recover those logs missed during that down time.
ACS can recover only if such messages to stored in local storage system. For example "TACACS Accounting" messages should be configured to store in local store as well. Then only Logging Recovery can recover from that ACS node.
If such messages are not available in the local store, then ACS sends alarm as "Missing log messages" and you can ignore them.
Do you think really your log collector is down for some time when you get this alarm?
05-27-2016 09:45 AM
Hi, no, the log collector were not down when i get this alarms.
I have checked in "Logging Categories->Global->TACACS Accounting", the box for "Log to Local Target". But NOT checked "Local Target is Critical"
ACS instances are all configured for "GLOBAL", none per-instance
Is this OK?
02-15-2017 01:44 PM
Hello.
I have the same issue with 5.8.1. Primary instance is log collector also.
Any idea?
Thanks.
Andrea
02-16-2017 02:18 AM
Hi.
Please, what messages should be configured to store locally?
Thanks.
Andrea
02-06-2015 02:55 PM
I have the same problem on my 5.5 platform:
CISCO SECURE ACS - ALARM NOTIFICATION
Alarm Name: ACS - System Errors
Severity: Critical
Cause/Trigger: Alarm caused by ACS - System Errors threshold
Generated on: 2015-01-29 00:22:00.0
Details
-------
(ACS Instance = acsdue, Time = Thu Jan 29 00:20:00 CET 2015, Category = CSCOacs_Internal_Operations_Diagnostics, Severity = ERROR, Message Text = Missing log messages)
and also the problem described in CSCuq03553. I suspect that there are some relationship between these 2 problems, maybe some log file are purged before been processed.
Any news from your site ?
09-10-2015 01:12 AM
I have had the same problem on 5.6 and now on 5.7.
Has anyone an idea how to tell the system to further ignore those missing log messages ?
12-01-2015 10:32 PM
I have the exactly same problem in ACS v.5.6. I installed the latest patch 5-6-0-22-4 which I hoped could solve the problem but it didn't.
05-10-2016 06:32 AM
Hello.
Same problem with a two servers deployment using software version 5.5.
Because this message is repeated every ten minutes, I stopped the log recovery message function and message is stopped. This is a workaround.
Any idea?
Thanks.
Andrea
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide