Chapter 23 |
Troubleshooting |
This section includes information on troubleshooting. Items covered include information on:
During the Sun Management Center module development process, when you encounter problems with module loading and its additional functionalities, refer to one of the three areas where Sun Management Center software provides you with trouble shooting information.
/opt/SUNWsymon/sbin/es-run ctail -f /var/opt/SUNWsymon/log/agent.log |
/opt/SUNWsymon/es-start -ai |
The following sections provide some examples for each one of the above categories. |
The Sun Management Center console is based on a configuration file infrastructure. This infrastructure provides a scripting language that is interpreted at run time to create Java consoles. Because of this late binding, most of the errors are shown at run time.
Errors are displayed in two places:
Note - All configuration files (those with extension .x) are installed on the Sun Management Center server, hence any action on these files will go through that server.
For example, if you are using a [load myConsole-j.x ] construct in your application, then in the Sun Management Center server log you should see this file being read by the console.
The Sun Management Center server log is a circular text file. To look at it in a 'tail' mode run following command:
/opt/SUNWsymon/sbin/es-run ctail -f /var/opt/SUNWsymon/log/server.log
No console log is created by the Sun Management Center console. All console debug messages are displayed in the Sun Management Center Console Messages dialog. When the Sun Management Center console comes up, it redirects all stdout messages to this dialog. Thus, if your Java code has System.out.println statements, the output of those will be displayed in this dialog.