Access Gateway trace log not updating
search cancel

Access Gateway trace log not updating


Article ID: 129172


Updated On:


CA Single Sign On Secure Proxy Server (SiteMinder) CA Single Sign On SOA Security Manager (SiteMinder) CA Single Sign-On


We are using CA Access Gateway (Secure proxy server, aka SPS), and noticing that the web agent trace logs get created, however transactions are not written to the file.  The only thing we see in the agent trace log is the agent being initialized.
[CSmAuthenticationManager::Initialize][CSmAuthenticationManager.cpp:87][AuthenticationManager initialized.]
[Response Manager][CSmManager.cpp:67][Initialized.]
[Variable Manager][CSmManager.cpp:67][Initialized.]
[CSmAuthorizationManager::Initialize][CSmAuthorizationManager.cpp:89][AuthorizationManager initialized.]
[Initialize][CSmHighLevelAgent.cpp:189][High Level Agent Initialized.]


Applies to all Linux Web Agent and Access Gateway implementations


In this use case, there were two virtual hosts configured in the Access Gateway server.conf.  Each virtual host had its own WebAgent*.conf file, but both were using the default ServerPath (ServerPath="ServerPath_default").

This is incorrect as ServerPath should be unique per our documentation:


To resolve the issue, edit each WebAgent*.conf file and provide the proper ServerPath for each instance. Server Path should be the full path to the respective WebAgent*.conf file and restart the Agent.

For example,
Virtualhost1 = a1
-Has WebAgent-a1.conf
-Edit WebAgent-a1.conf and change ServerPath to 

Virtualhost2 = a2
-Has WebAgent-a2.conf
-Edit WebAgent-a2.conf and change ServerPath to