Obtaining the target log files
About this task
You can create debug log files on the target system for debugging a problem by
configuring target properties. To enable the debug log, complete the steps that are relevant to your
operating system. You must have admin authority.
- Windows® systems
-
- Edit the target registry and go to HKEY_LOCAL_MACHINE\SOFTWARE\IBM\Tivoli\Remote
Control\TargetNote: On a 64-bit system, all the 32-bit registry keys are under the WOW6432Node key. For example: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\IBM\Tivoli\Remote Control\Target
- Right-click LogLevel and select Modify
- Set the value to 4 and click OK.
- Restart the target service.
- Start a session with the target and run the steps that are required for creating the problem.
- End the session.
- Edit the target registry and go to HKEY_LOCAL_MACHINE\SOFTWARE\IBM\Tivoli\Remote
Control\Target
- Linux® systems
-
- Edit the /etc/ibmtrct.conf file
- Set the value of LogLevel to 4 and save the file.
- Restart the target service.
- Start a session with the target and run the steps that are required for creating the problem.
- End the session.
- macOS systems
- Click .
- Enter sudo defaults write /Library/Preferences/com.ibm.bigfix.remotecontrol.target.plist LogLevel 4.
- Enter your password if prompted.
- Restart the target.
- Click .
- Open the Remote Control Target.app.
- Start a session with the target and run the steps that are required for creating the problem.
- End the session.
The log files are created with names in the following format:
On Windows® and Linux® systems:
trc_[comp]_[SUFFIX].log where [SUFFIX] is determined by the LogRollOver and LogRotation settings and [comp] is base, dsp, or gui.
For example, trc_base_Mon.log, trc_gui_Thu.log
On macOS systems:
trc_target_[SUFFIX].log where [SUFFIX] is determined by the LogRollOver and LogRotation settings.
For example, trc_target_Mon.log.
Note: When you finish gathering log files, set the value of LogLevel back to 2.
Restart the target service.
For more information about the logging properties, see Properties for configuring logging activity