pw debug
This command is used to dynamically turn debugging on or off for various processes and monitors running on the BMC TrueSight Infrastructure Management Server and Integration Services. Changing the debug level does not disturb data collection or any process or subsystem operations.
The following options can be specified:
-p process_name
— Proactive process as it is listed by thepw system status
. Infrastructure Management process runs on the server.Note
pw debug
does not support the Publishing Server process. Instead, see Configuring tracing for event management CLI commands.-a IntegrationServiceHost
— Host name of the Integration Service as it appears in the third column of output from thepw remote list
command.-s subsystem
— Distinct task performed by a proactive process. The name of the subsystem running in a process list. For example, the subsystems under pronet_agent (the Integration Service process) will correspond to the various monitors being run by that Integration Service.
To get a list of currently active subsystems, run the pw debug list
command. If you run pw debug list
by itself, it lists the debug status for all processes and subsystems running on BMC TrueSight Infrastructure Management Server, except for the Infrastructure Management Self-monitoring Service and any hidden subsystems.
If you run pw debug list-a ProactiveNet_Server_hostName_or_IPaddress
, it lists the status of all visible subsystems being run by the Infrastructure Management Self-monitoring Service on the BMC TrueSight Infrastructure Management Server. This information can then be used for setting debug levels on individual processes and visible subsystems on the BMC TrueSight Infrastructure Management Server or any Integration Service.
The following pw debug
commands are available:
pw debug file
pw debug list
pw debug on|off
Note
BMC recommends that the name and IP address of all hosts be configured on the DNS server. If no DNS entry corresponding to a particular host exists, some or all of the Infrastructure Management actions might fail.
pw debug file -a IntegrationServiceName [-x]
}Running pw debug file -a
IntegrationServiceName
pulls the log files from the specified Integration Service and stores them as a compressed .jar file on BMC TrueSight Infrastructure Management Server in the /pw/pronto/agentlogs/IntegrationServiceName directory. A .jar file is also known as a Java archive; it is analogous to a tar or zip and can be decompressed by the Windows utility WinZip. If you do not want the .jar format, specify the -x
option, and the logs will be brought over and stored under /pw/pronto/agentlogs/IntegrationServiceName/logs in their original uncompressed form. This command takes effect only on the currently active subsystems.
The log files downloaded include the Integration Service installation log file and all other log (and debug) files under the installationDirectory/pw/pronto/logs directory. The Integration Service logs for Solaris are stored under pproxy/PNS/Solaris28-sun4/log, for Windows under pproxy/PNS/log, and for Linux under pproxy/PNS/Linux-2-4-x86-nptl/log.
For example, to retrieve the Integration Service installation log file including log/debug files of the PATROL Integration Service, run the pw debug file -a
IntegrationServiceName
-x
command.
Debug must be turned on before the monitor log file is displayed in the /pw/pronto/logs/debug directory.
pw debug list
Use the following to list the debug status of all processes:
pw debug list -a
IntegrationServiceName
For example,
- To list the debug status of all processes on the BMC TrueSight Infrastructure Management Server, run the
pw debug list
command. - To list the debug status of the JServer process only, run the
pw debug list -p jserver
command. - To list the debug status for the Integration Service, run the
pw debug list -a
IntegrationServiceName
command.
Note
BMC recommends that the name and IP address of all hosts be configured on the DNS server. In case there is no DNS entry corresponding to a particular host, some or all of the Infrastructure Management actions might fail.
pw debug on|off
pw debug on | off | list -p
process_name
| -a
IntegrationServiceName
[-s
subsystem
]
pw debug on
turns on debugging on for all specified processes, Integration Services, and subsystems.
pw debug off
turns debugging off for all specified processes, Integration Services, and subsystems.
-p
process_name
— Infrastructure Management process listed by the pw system status
command. Infrastructure Management process runs on the BMC TrueSight Infrastructure Management Server. Use pw debug
to completely turn off debugging for a given process. This command will turn off debugging for all subprocesses that might not be visible.
-a
IntegrationServiceName
— Host name of the Integration Service as it appears in the third column of output from the pw remote list
command.
-s
subsystem
— Distinct task performed by a proactive process. The name of the subsystem running in a process list. -s
subsystem
does not turn debugging on or off for hidden subsystems. To turn debugging on or off for all subsystems, including hidden subsystems, use pw debug on
or pw debug off
.
For example, to turn on debugging for JServer, run the pw debug on -p jserver
command and to turn off debuging for the WebSphereMon subsystem for a specified Integration Service, run the pw debug off -a
IntegrationServiceName
-s WebSphereMon
command.
Activate debug for dbsrv
The following are the steps to enable debug services.
One can set or retrieve the logging level by using the \pw\pronto\bin\sqli command-line interface or through the dbisqlc interface.
Options available:
ALL, SQL - Turns on logging of SQL statements sent to the database
NONE - Turns off logging of SQL statements sent to the database
If you select SQL, the following types of requests are recorded in /usr/pw/asatmp/storm_<hostname>db.log:
¨ START DATABASE
¨ STOP ENGINE
¨ STOP DATABASE
¨ Statement preparation
¨ Statement execution
¨ EXECUTE IMMEDIATE statements
¨ Option settings
¨ COMMIT statements
¨ ROLLBACK statements
¨ PREPARE TO COMMIT operations.
¨ Connections
¨ Disconnections
¨ Beginnings of transactions
¨ DROP STATEMENT statement.
¨ Cursor explanations
¨ Cursor closings
¨ Cursor resume
¨ Errors
To turn on SQL logging level through sqli:
sqli "call sa_server_option('request_level_logging', 'SQL')"
sqli "select property('RequestLogging')"
sqli "call sa_server_option('request_level_logging', 'NONE')"
To determine the current logging level through sqli:
csh# source /usr/pw/pronto/bin/.tmcsh
csh# /usr/pw/pronto/bin/sqli <<EOF
>select property('RequestLogging');
>EOF
To turn off logging through sqli:
csh# source /usr/pw/pronto/bin/.tmcsh
csh# /usr/pw/pronto/bin/sqli <<EOF
>call sa_server_option('request_level_logging', 'NONE');
>EOF
If you want to set or retrieve the logging level through dbisqlc, connect to the database with DBA user. Run the following statements to set/retrieve the logging level.
- Setting: call sa_server_option('request_level_logging', 'SQL');
- Retrieving : SELECT PROPERTY( 'RequestLogging' );
Activate debug for services
Perform the following steps to enable debugging for services:
- In a text editor, open the /pw/jboss/server/minimal_jms/conf/log4j.xml file.
Uncomment the JMS Detailed logging section:
<!-- JMS Detailed logging --> <!-- <category name="org.jboss.mq"> <priority value="TRACE" class="org.jboss.logging.XLevel"/> </category> --> should become: <!-- JMS Detailed logging --> <category name="org.jboss.mq"> <priority value="TRACE" class="org.jboss.logging.XLevel"/> </category>
- Restart the BMC TrueSight Infrastructure Management Server by using the
pw system start
command.
All debug logs related to JMS will be redirected to the /pw/pronto/logs/ProactiveNet.log file
Note
Warnings displayed by the ProactiveNet.log file indicating that the data points from adapter type monitors are not latest these can be ignored.
Activate debug for httpd
Although there is no debug option exists for httpd, you can enable access_log for the httpd process to see the list of requests made by following these steps:
- Open the httpd.conf file from the /pw/apache/conf directory.
- Uncomment line number 564 (
#CustomLog /pw/apache/logs/access_log common
) by removing the first "#" mark. - Restart httpd process by using the
pw process restart httpd
command. (All the users logged in to the Operations Console will be logged out.)
The access_log file is located in the /pw/apache/logs directory.
Activate debug for mcell
Run the following command to turn on debugging for the cell:
pw debug on -p mcell
Run the following command to turn off debugging for the cell.
pw debug off -p mcell
-p
process_name
: Infrastructure Management process listed by the pw system status
command. The Infrastructure Management process runs on the server.
Note
You will not be able to see the debug status (on/off) of the mcell when you run the pw debug list
command.
Comments
Log in or register to comment.