limit=1918 (4703B06C.0000-4:kdcc1sr.c,562,"rpc__sar") Endpoint
unresponsive: "ip.pipe:#9.42.22.26:1918", 1C010001:1DE0000F, 210, 5(2),
FFFF/1, 1.1.1.9, d7273a (4703B06F.0000-
4:kdcl0cl.c,129,"KDCL0_ClientLookup") status=1c020006, "location server
unavailable", ncs/KDC1_STC_SERVER_UNAVAILABLE (4703B08F.0000-
4:kdcc1sr.c,562,"rpc__sar") Endpoint unresponsive: "ip:#9.42.22.26:1918",
1C010001:1DE0000F, 32, 5(2), FFFF/2, 1.1.1.9, d7273a (4703B092.0000-
4:kdcl0cl.c,129,"KDCL0_ClientLookup") status=1c020006, "location server
unavailable", ncs/KDC1_STC_SERVER_UNAVAILABLEYou can find out what is using
that port, stop the process, and then configure your system to use another port.
You can also reboot the system to clean up any stale Tivoli Monitoring processes
that might be bound to this port.
Remote monitoring server lost connection to the hub and all
agents display offline
Check the log for error messages in the RAS1 trace log that indicate timestamp
problems such as Ignoring invalid lastTimeStamp. This error occurs because you
synchronized the time on the hub and remote Tivoli Enterprise Monitoring Servers
with another time server. Restart the monitoring server experiencing the errors
because timers and POSIX (timed waits, for example) depend on reliable system
time.
After the set timeout, the Tivoli Enterprise Monitoring Server
is still pending
When you attempt to stop or start the Tivoli Enterprise Monitoring Server service,
after the set timeout, the Tivoli Enterprise Monitoring Server is still pending the
start or stop. You will receive the following error:
TEMS service is still pending start/stop. Check ITM documentation for more details.
The default time for starting and stopping a Tivoli Enterprise Monitoring Server
service is ten minutes. In the following two situations, this time can be ten times as
long:
1. If you have a large or complicated infrastructure connected to the Tivoli
Enterprise Monitoring Server.
2. If you have a remote Tivoli Enterprise Monitoring Server, but the hub Tivoli
Enterprise Monitoring Server is offline.
In any other situation, call IBM Software Support.
Providing the wrong path to configuration files during LDAP
configuration causes the Tivoli Enterprise Portal login window
to hang
During Security and LDAP configuration at Tivoli Enterprise Monitoring Server, if
you provide an incorrect path to the key.kdb and key.sth files, the Tivoli
Enterprise Portal login window goes into an indefinite loop. This occurs after
restarting the Tivoli Enterprise Monitoring Server and launching the Tivoli
Enterprise Portal client. Ensure that the provided paths are correct during
configuration. The installer does not check if the file exists under the user-provided
path.
Chapter 9. Monitoring server troubleshooting 161
To Next Page
Loading...
Need help?
General
