Suppress logs flooded with login and logout messages

Products

• VMware Smart Assurance
• Network Observability

Issue/Introduction

• How do I suppress Login and Logout messages in a Smarts log file?

• Smarts Broker log flooded with login and logout messages.

• Seeing a huge growth in log files in Smarts environment.

• Logs in Smarts domains flooded with logout messages.

• Smarts application logs contain numerous LOGIN and LOGOUT messages similar to the following Broker log messages:

[December 31, 2066 9:49:48 AM GMT+00:00 +925ms] t@428 SM_ProtocolEngine-380 unknown Java
SYS_MSG-*-LOGOUT-Logout by BrokerNonsecure from root@<hostname>[##.##.##.##]:53808 session 380

[December 31, 2066 9:49:49 AM GMT+00:00 +484ms] t@18 HTTP #4
SYS_MSG-*-LOGIN-Login by BrokerNonsecure from root@<hostname>[##.##.##.##]:53809 session 381

 

Environment

All supported releases of Smart

Cause

Smarts IP by default does not automatically suppress Login and Logout messages in a log file and must be configured to do so.

Resolution

To suppress Login and Logout messages in a Smarts log file, you must add or edit the SM_NO_LOG_CLIENTS parameter and set its value to TRUE in the runcmd_env.sh file on the server where the broker resides. This disables the client logging feature subscription for broker messages. This can be done as follows:

1. Open the runcmd_env.sh file where the broker was started using the command line run sm_edit:
   
   <Basedir>/smarts/bin/sudo ./sm_edit <Basedir>/local/conf/runcmd_env.sh
   
    
2. Add or edit the following line in the runcmd_env.sh file:
   
    SM_NO_LOG_CLIENTS=TRUE
   
   

3. Save and close the runcmd_env.sh file.

4. Restart the Smarts broker service.