Accessing console message logs

The Global Console has two logs which are useful for troubleshooting:

• The Java console is the first tool to use for console debugging. It shows store exceptions, errors reading attributes, and stack traces.

  To collect the most information about potential console problems, specify the -Dcom.smarts.log.level=TRACE property.

  Java console information can automatically be saved to a file on your local workstation by specifying the -Dcom.smarts.java.log=<filename> property. When specifying this property, the file is written in the <SM_WRITEABLE>/logs directory.

  SM_WRITEABLE is an environment variable whose default value can be changed in the runcmd_env.sh. Use this console information to assist with debugging issues.

  Note:

  Before starting the console with the -Dcom.smarts.java.log=<filename> property, verify that the <SM_WRITEABLE>/logs directory exists under BASEDIR/smarts/local.

• The message log shows everything the Manager sends to the console while the log window is activated (opened or minimized).

  This information can automatically be saved to a file on your local workstation by specifying the -Dcom.smarts.server.logMessages=true property. When specifying this property, the file is written to the <SM_WRITEABLE>/logs directory. Use this information to assist with debugging issues when the console stops responding.

  Note:

  Before starting the console with the -Dcom.smarts.server.logMessages=true property, verify that the <SM_WRITEABLE>/logs directory exists.

  To access the log views, select View > Java Console or View > Message Log.

  In the Java console, the following warning is benign:

  Warning: Could not get the full set of system properties