| Title: | DCE Product Information |
| Notice: | Kit Info - See 2.*-4.* |
| Moderator: | TUXEDO::MAZZAFERRO |
| Created: | Fri Jun 26 1992 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 2269 |
| Total number of notes: | 10003 |
Hi folks
This problem seems to be an old issue and fixed
for some platforms. (see also 1366, 1436, 1443 and QAR 374)
I have two customers having the same problem:
VMS 6.2 and DCE 1.3b ( with ECO's)
They see occasionally the follwoing problem:
acl_edit /.../gdc046_ch
returns >>> unable to bind to object /.../gdc046_ch
I tried to do a cdscp on that object:
GDC046::ERBER>cdscp
cdscp> show object /.:/gdc046_ch
SHOW
OBJECT /.../og.rzc2.ptt.com/gdc046_ch
AT 1997-02-27-15:54:34
RPC_ClassVersion = 0100
RPC_ObjectUUIDs = 33e538174ccbcf11a3b708002bb76893
CDS_CTS = 1996-06-21-10:03:08.913890100/47-44-43-30-33-39
CDS_UTS = 1997-02-27-00:56:01.695495100/47-44-43-30-33-39
CDS_Class = CDS_Clearinghouse
CDS_ClassVersion = 2.0
CDS_ObjectUUID = 1738e533-cb4c-11cf-a3b7-08002bb76893
CDS_Towers = <empty set>
CDS_CHDirectories = :
UUID of Directory = 0a12d9c4-cb4a-11cf-9424-08002bb77825
Name of Directory = /.../og.rzc2.ptt.com
CDS_CHDirectories = :
UUID of Directory = 0f797b8d-cb4a-11cf-9424-08002bb77825
Name of Directory = /.../og.rzc2.ptt.com/hosts/gdc039
CDS_CHDirectories = :
UUID of Directory = 333bd938-cb4c-11cf-bfaa-08002bb77825
Name of Directory = /.../og.rzc2.ptt.com/hosts/gdc046
CDS_CHDirectories = :
UUID of Directory = 98f91e3e-cb4e-11cf-a59d-08002bb77825
Name of Directory = /.../og.rzc2.ptt.com/hosts/gdc039/og
.
.
.
.
or
GDC046::ERBER>rpccp show entry /.:/gdc046_ch
objects:
1738e533-cb4c-11cf-a3b7-08002bb76893
>>> no matching binding information found
GDC046::ERBER>rpccp show entry -u /.:/gdc046_ch
objects:
1738e533-cb4c-11cf-a3b7-08002bb76893
>>> no matching binding information found
If the customer does a dce_setup clean and start everything
works perfectly.
I'm not sure if this problem is or was fixed on DCE for VMS.
It looks like that the QAR 374 is against the same problem
for the DUNIX platform.
Any comments on this issue ?
Thanks and regards
/Marco
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2175.1 | missing CDS_Towers on the object | TUXEDO::ZEE | There you go. | Thu Mar 06 1997 11:32 | 33 |
A few questions: - Has this clearinghouse, /.:/gdc046_ch, moved or been created recently? - If you do a "cdscp dump clerk cache", is there a CACHED CLEARINGHOUSE entry for this clearinghouse with appropriate towers? If so, can you do a "cdscp show clearinghouse /.:/gdc046_ch" and post the output? There were some timing-related problems with creation of new clearinghouses or moving of clearinghouses in previous versions of DCE in that the new address information was not necessarily updated in a quick enough fashion that people would expect. Having empty towers on the clearinghouse object is indicative of this, but not a guarantee. There's a difference between: "cdscp show clearinghouse /.:/foo_ch" - connects to specific clearinghouse, returns information stored only at that clearinghouse. and "cdscp show object /.:/foo_ch" - this is the clearinghouse object. Could connect to any server in the cell as this information is replicated. The cds clerk may do an equivalent operation to get the CDS_Towers of this clearinghouse if it is not in the cache already. Now, much of the information returned by the above two commands should be the same if they are properly synchronized, which .0 seems to indicate they are not with the empty CDS_Towers. This indicates a server problem on the /.:/gdc046_ch node in that the server is not updating the clearinghouse object for some reason. --Roger | |||||