One of my client upgraded to 8.5 SU3 and getting following every night when Backup is initiated.
At Sat Sep 08 01:01:02 ADT 2012 on node memsuccx01, the following SyslogSeverityMatchFound events generated:
SeverityMatch : Alert
MatchedEvent : Sep 8 01:00:48 memsuccx01 local7 1 : 97: memsuccx01.voice.root.local: Sep 08 2012 04:00:48.721 UTC : %UC_GENERIC-1-ProcessStop: %[UNKNOWN_PARAMTYPE:Process Identifier=20591][ModuleName=Cisco Desktop LDAP Monitor Service][AppID=Cisco Unified CCX Cluster View Daemon][ClusterID=][NodeID=memsuccx01]: Process Stopped AppID : Cisco Syslog Agent ClusterID :
NodeID : memsuccx01
TimeStamp : Sat Sep 08 01:00:48 ADT 2012
I checked the follwoing bug:
CSCtn93085 - UCCX: sev 2 alarms generated in SysLog during normal backup
It says the bug is fixed in 8.5 SU3 but my customer just upgraded to SU3 and still getting these alerts. It happens only during the backup and everything comes up working fine next morning.
Still happening on 10.6... *sigh*.
This issue is caused by Cisco bug CSCtn93085 which is affecting the version you are on, though it is only cosmetic. Here are the details of the bug:
|UCCX: sev 2 alarms generated in SysLog during normal backups|
During a backup of UCCX, the LDAP Monitor Service is temporarily stopped. This is normal behavior,
but a severity 2 alarm is being generated in the SysLog. The alarm makes it appear that the service
stopped unexpectedly or crashed.
Ignore alarms regarding the LDAP Monitor Service that appear during the timeframe of a UCCX backup.
This is by design on version 9.0 as well. Please check the following for version 9.0
During a backup of Unified CCX, a Severity 2 alarm is generated in the Syslog that indicates that the LDAP Monitor service stopped unexpectedly or crashed.
The LDAP Monitor service is temporarily stopped during a Unified CCX backup. This is normal behavior. You can ignore these alarms when they appear during a backup.
The bug id is intended to inform the customers that this alert is expected during backup and it can be ignored. Infact the customers are recieving alerts even when they are running the versions listed in the 'Fixed-in' section of bug link. That's why i referred this as working as per design for this specific case only as there is no real 'fix' that is being worked upon.
Thank you, but I respectfully disagree. Working by design is different from informative defect. Working by design indicates that the product team/developers decided a feature works based on how it was designed and coded per system requirements. Defect means something is mis-behaving for whatever reason i.e. software code error or unexpected behavior. This to me sounds like the later.
No disrespect here either, but I'm going to have to go with Chris on this one +5
I find it funny how this goes from a Severity Level 2 bug originally
to a Level 4 - "Fixed" when there have been at least 80 TAC cases
It sounds like they just gave up trying to fix this and decided it's now
"working as designed".
Cisco Unified Contact Center Express