156 IBM Tivoli Remote Control Across Firewalls
By default, the rcproxy.log file has debug level 3, the one we recommend, since it
will display comprehensible information. But this parameter can have values
between 0-11. Since values higher than 3 contain debugging information used by
developers also, we recommend that you set them only if requested by the
Customer Support Engineers, since this will notably affect the performance of the
Remote Control Proxy service, and because the error messages may not be
easily understood.
When the Remote Control Proxy service starts, it loads all the information stored
in the rcproxy.cfg. The Proxy service startup and the connection between proxies
information are then stored in the rcproxy.log file
Example 5-2 shows the rcproxy.log file contents.
Example 5-2 The Target Proxy log file
03/02/06 15:59:00 3 2104 logInit - Message logging initialized (level=3,
logmax=1MB).
03/02/06 15:59:01 1 2104 sendCommandLineRequest: cannot connect to
127.0.0.1:3333
03/02/06 15:59:01 0 2104 Proxy label: none (node is root)
03/02/06 15:59:01 0 2104 Proxy type: target
03/02/06 15:59:01 2 2104 No listen interface specified, defaulting to
INADDY_ANY
03/02/06 15:59:01 0 2104 Proxy listen port: 5020
03/02/06 15:59:01 0 2104 TFST Endpoint Proxy directory: C:\Tivoli\Tivoli
Systems\Tivoli Endpoint Proxy
03/02/06 15:59:01 2 2104 No timeout specified, using default
03/02/06 15:59:01 0 2104 Communication timeout: 240
03/02/06 15:59:01 0 2104 Max sessions: 10
03/02/06 15:59:01 0 2104 Reply to RSM data: no
03/02/06 15:59:01 3 2104 initRoutedSessionsManager: no network card specified
for children-local-host, using random interface
03/02/06 15:59:01 2 2104 initRoutedSessionsManager: children-remote-file
parameter not specified
03/02/06 15:59:02 3 1344 routingManager: WHO reply command received
[l=tic01005-gw]
03/02/06 16:00:55 3 1344 routingManager: TELL command received
[l=tic01005-gw]
The structure of the messages is explained as follows:
<date> <time> <debug-level> <thread> <message>
For example:
03/02/06 15:59:01 0 2104 Proxy listen port: 5020, where: