Description:
When deploying the Framework agent, there can be some situations where in the logs where you may get errors or messages of the following format
HLA: Component reported fatal error: 'Low Level Agent'
HLA: Component reported fatal error: 'Session Manager'
LLA: SiteMinder Agent Api function failed - 'Sm_AgentApi_IsProtectedEx' returned '-1'
HLA: Stopping
HLA: Initialization complete
HLA: Component reported fatal error: 'Authentication Manager'
Solution:
These can be broken down in to event messages and Agent messages. Below you can find a list with their possible causes
Event Messages
List of HLA and LLAWP agent event log messages, and their possible causes
HLA Messages: Cause:
- Missing configuration path required by LLAWP: Agent cannot find the WebAgent.conf file. Make sure that WebAgent.conf file exist and is accessible.
LLAWP Messages -->Cause:
- Log worker thread exiting : Agent could not start the logging/messaging thread. Agent could not create a new message queue. Make sure that you do not have any OS and/or memory issues.
- MsgBus worker thread exiting: Agent could not start the logging/messaging thread. Agent could not create a new message queue. Make sure that you do not have any OS and/or memory issues.
- Bad log file '%s' Log worker thread exiting: Agent could not open or create the agent log file. The existing file might be corrupted, disk might be full or the user may not have access rights.
- Setsid failed, this process must already be a group leader: Agent could not create a new session. Possibly an OS issue
- Fork failed: Agent could not create a new duplicate process. Possibly an OS issue
- LLAWP unable to get configuration, exiting: Agent cannot find the WebAgent.conf file. Make sure that WebAgent.conf file exists and is accessible.
- Duplicate LLAWP process not allowed exiting: Make sure there are no other instances of LLAWP process is running.
- Could not start log worker thread, exiting: Agent could not start the logging/messaging thread. Agent could not create a new message queue. Make sure that you do not have any OS and/or memory issues.
- Could not start message bus worker thread, exiting: Agent could not start the logging/messaging thread. Agent could not create a new message queue. Make sure that you do not have any OS and/or memory issues
- LLAWP unable to create the resource cache: Make sure the value of the resource cache size configuration parameter is greater than 0
- LLAWP unable to create the authentication cache: Make sure the value of the session cache size configuration parameter is greater than 0.
- LLAWP unable to create the authorization cache: Make sure the value of the session cache size configuration parameter is greater than 0.
Agent Log Messages
HLA Messages: Cause
- Reponses Manager failed to shutdown: Authentication response manager failed to shutdown.
- Unable to process - no interfaces registered for this manager / interface name: Advance authentication initialization issues, agent could not find a plug-in.
- Analyzer failed - return code #: Advance authentication failure
- Analyzer returned unknown result code - #: Advance authentication failure, unknown error.
- Unable to process - no analyzer responded: Advance authentication analyzer did not respond.
Session manager failed to shutdown: Authentication session manager failed to shutdown.
- Failed to retrieve # Agent failed to retrieve resource or session data: Agent failed to retrieve resource or session data.
- LLA AuthenticateUser failed!: Low Level agent user authentication failed.
- GetSessionInfo failed for session ID #: Low Level agent failed to obtain the session information for session ID #
- SetSessionInfo failed for session ID # -> Low Level agent failed to set the session information for session ID #
- Session manager reported a fatal error while creating session - return code #: High Level Agent could not create a session.
- Session manager indicted processing should exit - return code #: Session manager could not process the data.
- Responses manager indicted processing should exit - return code #: Response manager could not process the data
- Variable manager failed to shutdown: Could not shutdown authorization variable manager.
- Variable Manager failed to process variables: User authorization has failed.
- Failed to initialize Administration Manager: High Level agent initialization error.
- Failed to initialize filter context: High Level agent initialization error.
- Failed to initialize Resource manager: High Level agent initialization error.
- Failed to initialize Sessionmanager: High Level agent initialization error.
- Failed to initialize Protection Manager: High Level agent initialization error.
- Failed to initialize Credential Manger: High Level agent initialization error.
- Failed to initialize Challenge Manager: High Level agent initialization error.
- Failed to initialize Authentication Manager: High Level agent initialization error.
- Failed to initialize Authorization Manager: High Level agent initialization error.
- Initialization successful : High Level agent initialization successful.
- Failed to shutdown Resource manager: High Level agent shutdown error.
- Failed to shutdown Session Manager: High Level agent shutdown error.
- Failed to shutdown Protection Manager: High Level agent shutdown error.
- Failed to shutdown Credential Manager: High Level agent shutdown error.
- Failed to shutdown Challenge manager: High Level agent shutdown error.
- Failed to shutdown Authentication Manager: High Level agent shutdown error.
- Failed to shutdown Authorization Manger: High Level agent shutdown error.
- Failed to shutdown Administration manager: High Level agent shutdown error.
- Shutdown successful: High Level agent shutdown successful.
- Administration manager reported fatal error: High Level agent request processing error.
- Resource manager unable to handle request, or Manager reported fatal error - return code #: High Level agent request processing error.
- Resource Manager indicated processing should exit - return code # : High Level agent request processing error.
- Session Manager indicated processing should exit - return code #: High Level agent session processing error.
- Session manager reported a fatal error while establishing session - return code # : High Level agent session processing error.
- Protection Manager returned - return code #: High Level agent request processing error.
- Protection manager was unable to determine if resource is protected, or reported fatal error:
- Agent could not determine if the resource is protected or not
- Challenge Manager unable to handle request, or Manager reported fatal error: Agent could not challenge the user.
- Credential manager reported fatal error - return code #: Agent could not get the user credentials.
- Credential manager indicted processing should exit - return code #: Agent could not get the user credentials.
- Challenge manager unable to handle request, or manager reported fatal error: Agent could not authenticate the user.
- Authentication manager indicated processing should exit - return code: Agent could not authenticate the user.
- Authentication Manager reported a fatal error while authenticating user: Agent could not authenticate the user.
- Authorization manager indicated processing should exit: Agent could not authorize the user.
- User authenticated and authorized: Agent was able to authenticate and authorize the user.
- Advanced Authenticated manager indicated processing should exit: Advance authentication(such as fcc) failure
LLAWP Messages: Cause:
- Log Queue initialized: Agent has been able to initialize local message buffer.
- Log Queue shutting down: Agent is shutting down the logging process.
- Message Bus received query message from client #: Agent LLAWP process has received a message and is processing it
- Message Bus received open message from client #: LLAWP process has received a request to add the client to the list