Chapter 5. Troubleshooting techniques 167
5.3.3 Case 3: Wrong Proxy configuration
In this case we assume that the Target Proxy is not configured properly and the
communication between remote control proxies does not work, while the
gateway and Endpoint Proxy communication works fine. Based on this scenario
we provide troubleshooting examples to discover and solve this issue.
As soon as we start the session, we get the error message in Figure 5-6.
Figure 5-6 Error message at session startup: Proxy configuration problem
We assume that Target and Controller Endpoint are alive and everything works
from Framework point of view. We assume also that the Remote Control Proxies
services are up and running. So we skip these checks in this example.
We directly analyze the Remote Control Proxy Target and Controller log files,
and since our environment uses a Relay, we also analyze the relay.log:
First we analyze the Target Proxy log file as in Example 5-15.
Example 5-15 The remote control Target Proxy log file
03/02/12 16:09:15 3 1920 logInit - Message logging initialized (level=3,
logmax=1MB).
03/02/12 16:09:16 1 1920 sendCommandLineRequest: cannot connect to
127.0.0.1:3333
03/02/12 16:09:16 0 1920 Proxy label: none (node is root)
03/02/12 16:09:16 0 1920 Proxy type: target
03/02/12 16:09:16 2 1920 No listen interface specified, defaulting to
INADDY_ANY
03/02/12 16:09:16 0 1920 Proxy listen port: 5020
03/02/12 16:09:16 0 1920 TFST Endpoint Proxy directory: C:\Tivoli\Tivoli
Systems\Tivoli Endpoint Proxy
03/02/12 16:09:16 2 1920 No timeout specified, using default
03/02/12 16:09:16 0 1920 Communication timeout: 240
03/02/12 16:09:16 0 1920 Max sessions: 10
03/02/12 16:09:16 0 1920 Reply to RSM data: no
03/02/12 16:09:16 3 1920 initRoutedSessionsManager: no network card specified
for children-local-host, using random interface