Operational Defect Database
BugZero updated this defect 33 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
VMware | 323853
Smarts: Logs flooded with login and logout messages; How can I suppress them?
Last update date:
4/16/2024
Affected products:
Smart Assurance - SMARTS
Affected releases:
No affected releases provided.
Fixed releases:
No fixed releases provided.
Description:
Symptoms
How do I suppress Login and Logout messages in a Smarts log file?Smarts Broker log flooded with login and logout messagesSeeing a huge growth in log files in Smarts environmentLogs in Smarts OI flooded with logout messagesLogs in Smarts SAM flooded with logout messagesLogs in Smarts AM or Smarts AM PM 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 JavaSYS_MSG-*-LOGOUT-Logout by BrokerNonsecure from root@domain.emc.com.fake[10.0.0.1]:53808 session 380 [December 31, 2066 9:49:49 AM GMT+00:00 +484ms] t@18 HTTP #4SYS_MSG-*-LOGIN-Login by BrokerNonsecure from root@domain.emc.com.fake[10.0.0.1]:53809 session 381 [December 31, 2066 9:49:49 AM GMT+00:00 +492ms] t@16 HTTP #2SYS_MSG-*-LOGIN-Login by BrokerNonsecure from root@domain.emc.com.fake[10.0.0.1]:53810 session 382 [December 31, 2066 9:49:49 AM GMT+00:00 +499ms] t@429 SM_ProtocolEngine-381 unknown JavaSYS_MSG-*-LOGOUT-Logout by BrokerNonsecure from root@domain.emc.com.fake[10.0.0.1]:53809 session 381 [December 31, 2066 9:49:49 AM GMT+00:00 +506ms] t@430 SM_ProtocolEngine-382 unknown JavaSYS_MSG-*-LOGOUT-Logout by BrokerNonsecure from root@domain.emc.com.fake[10.0.0.1]:53810 session 382 [December 31, 2066 9:49:51 AM GMT+00:00 +469ms] t@16 HTTP #2SYS_MSG-*-LOGIN-Login by BrokerNonsecure from root@domain.emc.com.fake[10.0.0.1]:53811 session 383 [December 31, 2066 9:49:51 AM GMT+00:00 +747ms] t@16 HTTP #2SYS_MSG-*-LOGIN-Login by BrokerNonsecure from root@domain.emc.com.fake[10.0.0.1]:53812 session 384 [December 31, 2066 9:49:51 AM GMT+00:00 +759ms] t@432 SM_ProtocolEngine-384 unknown JavaSYS_MSG-*-LOGOUT-Logout by BrokerNonsecure from root@domain.emc.com.fake[10.0.0.1]:53812 session 384 [December 31, 2066 9:49:51 AM GMT+00:00 +816ms] t@16 HTTP #2SYS_MSG-*-LOGIN-Login by BrokerNonsecure from root@Localhost[127.0.0.1]:49743 session 385 [December 31, 2066 9:49:51 AM GMT+00:00 +834ms] t@433 SM_ProtocolEngine-385 13155 ISIN-ESM-9SYS_MSG-*-LOGOUT-Logout by BrokerNonsecure from root@Localhost[127.0.0.1]:49743 session 385 [December 31, 2066 9:49:52 AM GMT+00:00 +707ms] t@16 HTTP #2SYS_MSG-*-LOGIN-Login by BrokerNonsecure from root@domain.emc.com.fake[10.0.0.1]:53813 session 386
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: 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 Add or edit the following line in the runcmd_env.sh file: SM_NO_LOG_CLIENTS=TRUE Save and close the runcmd_env.sh file.Restart the Smarts broker service.
