000023001 - Why isn't an 'Autodetection Error' logged in the RSA ACE/Agent event log?

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

Article Content

Article Number000023001
Applies ToRSA ACE/Agent 5.x
RSA ACE/Server
IssueWhy isn't an "Autodetection Error" logged in the RSA ACE/Agent event log?
RSA ACE/Agent debugging logs "set_load_balance_event() autodetect FAILED". Event log does not always log "Event ID 1002 ACE/Server is not responding" when this event occurs.

When an RSA ACE/Agent has difficulty communicating with the ACE/Server, the following log entry appears in the agent's debugging log:

    [1568] 13:32:30.830 File:loadbal.c Line:1412 # set_load_balance_event() autodetect FAILED on 2

Usually, the Microsoft Windows event viewer would log the same event at the same time:

    Source ACECLIENT
    Category ACE/Agent
    Event ID 1002
    ACE/Server is not responding.
    Run SDTEST on Windows or sdinfo on UNIX to verify port and IP address of ACE/Server.
    Make Sure ACE/Server process is running.

It was noticed that a log event does not always appear in Windows' event viewer, while a communication failure appears in the RSA ACE/Agent's debugging log. The reason for this behavior is a suppression logic that, under some circumstances, prevents this message from being logged in Windows event viewer.

The above error appears on a server even if the Agent is not installed and client code is built into the server.

Legacy Article IDa29136