Summary:
How to change tracing level in IME version 5.0/5.0.5 on Solaris platform. This option can be set while IME is running or as a start-up option.

Symptom:
The default tracing option for IME is INFO. With this mode, only INFO and ERROR messages are logged in trace files. For troubleshooting, it’s more helpful, if the tracing level is changed to DEBUG.

Detailed Information:
There are two levels of tracing in IME for all customer deployments: INFO and DEBUG. The amount of debugging information available in the IME trace files is maximized with the DEBUG trace level. The recommended tracing level for all deployments is INFO. In case of troubleshooting, it is recommended that the tracing level be changed to DEBUG.

The trace files are default located in <IME_INSTALL>/logs directory. There is a separate trace file for each component in IME. For example, for Account Manager, its IMEAccount_3482.trc, where 3482 defined the process ID for Account Manager process. Every time IME is restarted, processes get assigned a new process ID and hence new trace file gets generated for each restarted component.

Resolution:
There are two options to change the tracing level.

1. As a startup option
2. As a run-time option

Startup option: This option is recommended for development setups and on the systems where tracing level change requirement is ongoing. To set this option:

· Login to the IME system as root
· Go to <IME_INSTALL>
· Open IME “start” script
· After “#!/bin/csh”, in the next line, paste following environment variable setting:

setenv TW_TRACE_LEVEL ALL=debug

· The other permitted option for tracing is “info”.
· Restart IME Server to enable desired tracing.

Note that setting this environment variable will enable debug tracing only for locally running IME processes.

Run-time option: This option is helpful especially on production environment where restart of IME system is not a practical/easy option. To set this option:

· Login to the IME system as root
· Execute following command on console:

<IME_INSTALL>/scripts/run_exec <IME_INSTALL>/bin/IMEStart -corba_trace_level ALL=debug

· The other permitted option for tracing is “info”.
· This command will generate a process ID and the tracing level will be enabled as specified.
· To verify the tracing action, go to <IME_INSTALL>/logs
· Open the latest IMEAccount_<process id>.trc file.
· Look for a similar statement in last few lines as given below:

Wed Nov 27 15:07:27 2002 microsec: 729050, TID 26, DEBUG: IMEAccount, module=CORE: Setting level for module: ALL to: debug; in file: Compiler/ccTrace.cpp; at line: 496

· The option provided above set the tracing level for all IME components on the given system. This is the recommended option as well. In case debugging level for only particular components needs to be changed, use following command:

<IME_INSTALL>/scripts/run_exec <IME_INSTALL>/bin/IMEStart -corba_trace_level <IP Address> <Name of component> ALL=debug

· Name of the component would be e.g. AccountManager, PackageManager, etc. To get complete list of all components and other options, use following command:

<IME_INSTALL>/scripts/run_exec <IME_INSTALL>/bin/IMEStart

NOTE: These commands or environment settings can be used to bring back the tracing level to info after troubleshooting process has completed.

Also, please note that the run-time tracing change is temporary. After restart of IME server, the tracing level will revert back to default “info”. To have continued tracing in desired mode, refer to start-up option of tracing above.

IMPORTANT: In some deployments, it has been reported that this command reports ERROR as given below. Please ignore the error, as it’s a known issue and being worked upon. The tracing level would be set despite this ERROR statement:

Wed Nov 27 16:36:11 2002 microsec: 779329, TID 1, ERROR: IMEStart, module=APPLICATION: Failed to set trace level for component 20; in file: PostaStart.cpp; at line: 1206

Original Author: VMITTAL
Original Submitter: IBURTON
Keywords: trace, debug, info, error, log, tracing, ime IME ID#28934