000012388 - What does 'Server Test Succeeded' in aserver.log mean?

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 Number000012388
Applies ToAccess Manager authorization server
ClearTrust authorization server
IssueWhat does "Server Test Succeeded" in AServer log mean?

AServer logs report the following:

sequence_number=170266,2008-10-08 02:30:48:767 EDT,messageID=3001,client_ip_address=,client_port=3410,result_code=30,result_action=Server Test,result_reason=Server Test Succeeded
sequence_number=170267,2008-10-08 02:51:01:400 EDT,messageID=3001,client_ip_address=,client_port=1369,result_code=30,result_action=Server Test,result_reason=Server Test Succeeded
sequence_number=170268,2008-10-08 02:56:32:281 EDT,messageID=3001,client_ip_address=,client_port=4730,result_code=30,result_action=Server Test,result_reason=Server Test Succeeded
sequence_number=170272,2008-10-08 02:56:41:828 EDT,messageID=3001,client_ip_address=,client_port=1453,result_code=30,result_action=Server Test,result_reason=Server Test Succeeded


These are pings/no-ops sent by clients and other aserver(s)  to the aserver to validate the connection. The clients could be API Runtime Clients or RSA agents for web/appservers.  The agents perform this function during a pool refresh.  Aservers maintain a few connections to each other for user bad password count and user lockout updates. 

The API for generating a test of a server may be used for custom tests and programmers should review the following item


testServer(Map options)
          "Ping" the server which implements this interface.


Legacy Article IDa42458