Skip to main content

psdebug

Use the psdebug program on an application server to configure logging output from various Bravura Security Fabric software components. It is helpful when troubleshooting installation or functionality problems.

Usage
psdebug -prog <program> -level <0-5|99> -maxwait <seconds>
psdebug -prog <program> -submodule <submodule> -level <0-5|99>
psdebug -remove
psdebug -remove <program>
psdebug -prog <program> -extlevel <level names>

Argument

Description

-prog <program>

Identify the program to change the logging level for.

-submodule <submodule>

For programs or scripts that use IDMLib, identify the submodule to change the logging level for.

-level <N>

Set the logging level for programs or scripts, or turn debugging on or off.

See "Logging levels" below.

-extlevel <level names>

Set extended performance logging levels.

See "Extended performance logging levels" below.

-remove

Remove custom debug settings. Individual programs/submodules can be specified.

-maxwait <seconds>

Set the maxwait parameter to ignore all Perf log events that are slower than the specified duration. If the maxwait argument is not specified explicitly, then the default value is set to 15 seconds.

Logging levels

To determine the type of information to include in the specified program’s log file, use the command:

psdebug -prog <program> -level <0-5|99>

where logging levels can be:

  • 0 No log file generated

  • 1 Log errors only

  • 2 Log errors and warnings

  • 3 Log errors, warnings, and notices

  • 4 Log errors, warnings, notices, and information messages (default)

  • 5 Log all the above and debugging information for the program

  • 99 Log all the above and verbose debugging information

Note:

  • A change in the logging level will take effect the next time the program starts or script is run.

    Services keep running and restarting them can interrupt their work and cause errors; in order for the logging service to be aware of logging configuration changes added by psdebug or direct-to-registry for any service, run:

    services\idmlogsvc -trace-restart

  • You may need to test a debug level to obtain the information you require. For example; the idpm service needs to be set to 5 to display the IP address of the Domain Controller that sends a Password Change notification.

  • It is a good idea to keep a list of which binaries and scripts have been set to specific logging levels.

  • Do not include the program or script’s extension (.exe, .py).

  • PSLang scripts are generally run in-process; so if the workflow service (idwfm) runs a PSLang script, then the script’s logs will show up as being generated by idwfm and they should inherit idwfm’s log level.

Extended performance logging levels

To determine the type of performance information to be included in the specified program’s log file, use the command:

psdebug -prog <program> -extlevel <level names>

where extended logging levels can be one or both of the following:

  • perf Runtime performance messages – All binary and script performance are recorded

  • perf_sproc Stored procedure runtime performance messages – The performance of stored procedures, called by binaries, is recorded.

    This option has to be added only to the ajax service ( -prog ajaxsvc).

  • perf_replication Database replication messages – The name and duration of replicated stored procedures is recorded, as well as the send queue in which they are running.

  • perf_lws Local workstation runtime performance messages – The name and duration of local workstation stored procedures is recorded.

  • perf_ajax Ajax runtime performance messages – All Ajax requests, including the function name, transid, duration, and user are recorded.

Examples

  1. To log errors and warnings only for the idwfm service, type:

    psdebug -prog idwfm -level 2

  2. To track events and stored procedures that are part of replication:

    psdebug.exe -prog iddb -level 5 -extlevel perf_replication

  3. Since Database Service (iddb) is a long running service, you can manually inform the logging system that a change was made by running the following command:

    idmlogsvc.exe -trace-restart

  4. To remove custom logging level settings for all modules, type:

    psdebug -remove

  5. To log only error level messages for a script called test with a submodule called test_submodule, type:

    psdebug -prog test -submodule test_submodule -level 1

  6. To log program and stored procedure performance for the Transaction Monitor Service (idtm) service, type:

    psdebug -prog idtm -extlevel perf perf_sproc

  7. To log program and stored procedure performance that takes more than 5 seconds for the iddiscover program, type:

    psdebug.exe -prog iddiscover -level 4 -maxwait 5

See also

Determine the level of product customization

In this section: