Symantec Access Management

  • Private Community
Back to discussions
Expand all | Collapse all

CSm and SmPlugin messages missing in webagent logs on startup

  • 1.  CSm and SmPlugin messages missing in webagent logs on startup

    Posted Oct 21, 2018 02:14 PM

    Hello,

    We have a case where webagent logs stops logging after LLAWP: Message bus is successfully initialized. Below is the log snippet. The CSm and SmPlugin messages are missing after startup.

     

    [LLAWPLogQ.cpp:661][INFO][sm-AgentFramework-00590] LLAWP: Logging initialized.
    [36612/1300707136][Mon Oct 15 2018 17:09:55][LLAWorkerProcess.cpp:1552][INFO][sm-AgentFramework-00680] LLAWP: Initialization complete.
    [36612/1118795520][Mon Oct 15 2018 17:09:55][LLAWPMsgBus.cpp:419][INFO][sm-AgentFramework-00660] LLAWP: Message bus initialized.

     

     

    In Normal cases we see the following logs:

     

    [114109/4216878848][Thu Sep 06 2018 17:28:18][LLAWPLogQ.cpp:661][INFO][sm-AgentFramework-00590] LLAWP: Logging initialized.
    [114109/15742784][Thu Sep 06 2018 17:28:18][LLAWorkerProcess.cpp:1552][INFO][sm-AgentFramework-00680] LLAWP: Initialization complete.
    [114109/4197365504][Thu Sep 06 2018 17:28:18][LLAWPMsgBus.cpp:419][INFO][sm-AgentFramework-00660] LLAWP: Message bus initialized.
    [111661/2191488768][Thu Sep 06 2018 17:28:22][CSmLowLevelAgent.cpp:5221][INFO][sm-AgentFramework-00510] LLA: Logging initialized.
    [111661/2191488768][Thu Sep 06 2018 17:28:22][SmPlugin.cpp:66][INFO][sm-AgentFramework-00170] Agent Framework plug-in 'SM_WAF_HTTP_PLUGIN' initialized. Description 'SiteMinder Agent HTTP Plug-in'.
    [111661/2191488768][Thu Sep 06 2018 17:28:22][CSmAdminManager.cpp:853][INFO][sm-AgentFramework-00320] ADMIN: Received key update attribute 'KEY_UPDATE_PERSISTENT'.
    [111661/2191488768][Thu Sep 06 2018 17:28:22][CSmAdminManager.cpp:871][INFO][sm-AgentFramework-00310] ADMIN: Successfully processed key update attribute 'PERSISTENT'.
    [111661/2191488768][Thu Sep 06 2018 17:28:22][CSmAdminManager.cpp:804][INFO][sm-AgentFramework-00320] ADMIN: Received key update attribute 'KEY_UPDATE_LAST'.
    [111661/2191488768][Thu Sep 06 2018 17:28:22][CSmAdminManager.cpp:820][INFO][sm-AgentFramework-00310] ADMIN: Successfully processed key update attribute 'LAST'.
    [111661/2191488768][Thu Sep 06 2018 17:28:22][CSmAdminManager.cpp:828][INFO][sm-AgentFramework-00320] ADMIN: Received key update attribute 'KEY_UPDATE_CURRENT'.
    [111661/2191488768][Thu Sep 06 2018 17:28:22][CSmAdminManager.cpp:845][INFO][sm-AgentFramework-00310] ADMIN: Successfully processed key update attribute 'CURRENT'.
    [111661/2191488768][Thu Sep 06 2018 17:28:22][CSmAdminManager.cpp:778][INFO][sm-AgentFramework-00320] ADMIN: Received key update attribute 'KEY_UPDATE_NEXT'.
    [111661/2191488768][Thu Sep 06 2018 17:28:22][CSmAdminManager.cpp:795][INFO][sm-AgentFramework-00310] ADMIN: Successfully processed key update attribute 'NEXT'.
    [111661/2191488768][Thu Sep 06 2018 17:28:22][CSmAdminManager.cpp:261][INFO][sm-AgentFramework-00280] ADMIN: Administration Manager initialized.
    [111661/2191488768][Thu Sep 06 2018 17:28:22][CSmHighLevelAgent.cpp:191][INFO][sm-AgentFramework-00380] HLA: Initialization complete.
    [111660/2199881472][Thu Sep 06 2018 17:29:12][CSmLowLevelAgent.cpp:5221][INFO][sm-AgentFramework-00510] LLA: Logging initialized.
    [111660/2199881472][Thu Sep 06 2018 17:29:12][SmPlugin.cpp:66][INFO][sm-AgentFramework-00170] Agent Framework plug-in 'SM_WAF_HTTP_PLUGIN' initialized. Description 'SiteMinder Agent HTTP Plug-in'.

     

     

    Do you see in issue here? If yes, how can we fix it? What is the reason for missing CSm and SmPlugin messages ?

     

    Best Regards,

    Murali



  • 2.  Re: CSm and SmPlugin messages missing in webagent logs on startup

    Posted Oct 23, 2018 10:57 AM

    What is version of Web Server / Web Agent on the non working one VS the working one ?

     

    Couple of things that I'd check

     

    • Look at the configuration of WebAgentTrace.conf (compare with the working one).
    • Check disk space.
    • Check if LLAWP is still running.