IBM E027SLL-H - Tivoli Monitoring - PC Troubleshooting Manual page 120

location broker (LLB) and the global location broker (GLB). There is one local
location broker for every RPC server (The Tivoli Enterprise Monitoring Server has
it's own LLB. The monitoring agent, the Warehouse Proxy agent, and the Tivoli
Enterprise Portal Server all have their own instance of a LLB.) RPC servers, by
definition, publish the service offered and address of this service in their local
location broker.
Confirming the Local Location Broker service initialized:
The bind messages in the RKLVLOG indicate the success or failure of the LLB
service initialization. One of two message IDs prefix the LLB status messages,
depending on how the LLB service was started. KDSNC007 is the message prefix
issued on successful LLB process initialization when the LLB is started internally
by the Tivoli Enterprise Monitoring Server.
(USCACO01.VWCTHLB.CANCTDCS.SNASOCKETS).135.
Repairing errors in Local Location Broker service initialization:
Bind failures due to insufficient authorization are reported with Errno. 2
(EACCESS). Bind to the Local Location Broker (as the name LOCAL implies) is
done with a local socket address. The bind fails for the following reasons:
v Insufficient authorization
v The address is unavailable
Status 1DE00000=KDE1_STC_CANTBIND.
<0x176A97D4,0x10> BSD bind details:
Family 2, Socket 0, Status 1DE00000, Errno 2.
"cant bind socket",
Bind failures due to address-in-use:
ENDPOINTINUSE
socket", ncs/KDC1_STC_CANT_BIND
Bind failure due to address-in-use but not fatal:
socket", ncs/KDC1_STC_CANT_BIND
If the bind failure is due to EADDRINUSE but the Broker service is started, the
error might not be fatal. Determine whether or not the bind of this IBM Tivoli
Monitoring address space was to the LLB in that address space. In some instances,
an address space can bind to the LLB of another address space. This can only
occur in the same system image. If the bind failure is fatal, then another process on
this system image has the 'well-known' port. Bind failures due to insufficient
authorization are fixed by granting RACF permission for the OMVS segment to the
Omegamon Platform started task name.
102
IBM Tivoli Monitoring: Troubleshooting Guide
KDSNC004 Bind of local location broker complete= ip.pipe:#9.42.46.26.21343.
KDSNC004 Bind of local location broker complete= ip:#9.42.46.26.21343.
KDSNC004 Bind of local location broker complete= sna:
KDSNC007 Local Location Broker is active
(32645848-E8E45647:kdebnws.c,64,"KDEB_NewSocket")
(3265B3F0-E8E45647:kdebnws.c,84,"KDEB_NewSocket")
00000000 00022EE1 00000000 00000000 00000000
(326B1EA8-E8E45647:kdcsuse.c,98,"KDCS_UseFamily") status=1c010005,
ncs/KDC1_STC_CANT_BIND
2001.252 04:42:41 KDC00008 Unable to create location server, status 1C010005
(3ACDB600-DEB3B73F:kdebnws.c,62,"KDEB_NewSocket") Status 1DE00030=KDE1_STC_
(3ACF5028-DEB3B73F:kdcsuse.c,99,"KDCS_UseFamily") status=1c010005, "cant bind
(1CF7B1F8-E6D9D743:kdcsuse.c,99,"KDCS_UseFamily") status=1c010005, "cant bind
KDSNC007 Local Location Broker is active
.................