CA7I3- IDASH not in Sync with live Data

book

Article ID: 222008

calendar_today

Updated On:

Products

CA Workload Automation iDash for CA 7

Issue/Introduction

Not seeing current information in iDash from the CA7 instance. No records are being received since 15:30 yesterday.

According to the Message guide no action is required for CAL2M117I below. But, after receiving this message yesterday no more events have been recorded for this CA7. Also concerned regarding the CAL2M149W messages.

CAL2M114I iDash denata3utcai01.cloud.tiaa-cref.org CA73 retrying notification, 1 of 20                              
CAL2M117I iDash denata3utcai01.cloud.tiaa-cref.org CA73 starting recovery, EVTL: 1464                               
CAL2M117I Reason: Exception reading notification response, -46 EDC8114I Address family not supported, EVTL: 1464    
CAL2M144I (CA73) Catchup listener initializing, EVTL: 1464                                                          
CAL2M188I (CA73) Catchup listener initialized,  EVTL: 1464, Token: 10FA9AB80                                        
CAL2M149W (CA73) CA7LOG event not recorded by ENF                                                                   
CAL2M123I (CA73) TERM requested for catchup: ............., EVTL: 1464                                              
CAL2M330I (CA73) TERM complete for catchup:  ............., EVTL: 1464, RC: 00000000 00000000 00D2F000              
CAL2M187I (CA73) Event recovery processing completed                                                                
CAL2M114I iDash denata3utcai01.cloud.tiaa-cref.org CA73 retrying notification, 2 of 20                              
CAL2M117I iDash denata3utcai01.cloud.tiaa-cref.org CA73 starting recovery, EVTL: 1484                               

Environment

Release : 12.0

Component : CA WORKLOAD AUTOMATION iDASH FOR CA 7

Resolution

The problem was with ENF not recording events and the recovery was getting an error. Had the customer restarted ENF and CA7IDASH and things started to work. The client will follow up with ENF support to see what happened to ENF.