000022559 - How to capture all log messages via RSA Authentication Manager Administration API function Sd_MonitorHistory

Document created by RSA Customer Support Employee on Jun 16, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000022559
Applies ToRSA Authentication Manager 6.0.2 Administration API
Sun Solaris 2.8
IssueHow to capture all log messages via RSA Authentication Manager Administration API function Sd_MonitorHistory
Sd_MonitorHistory() function appears to skip some activity log messages
CauseOne or more replicas in the system are running a time out of sync with the time on the primary. The Administration API call is designed to pick up all messages in the log from the last time it was called. It does this based on "logged time of last message processed by the API" rather than "last record number processed". If the time on a replica is more than 30 seconds slower than the primary and it has posted an activity record into the primary, then subsequent SD_MonitorHistory() calls may not see the "older" entries from the out-of-sync Replica.
ResolutionTo effectively use the Administration API Sd_MonitorHistory function, all RSA Authentication Manager components must be synchronized to the same time source.
Legacy Article IDa29179

Attachments

    Outcomes