[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference tuxedo::dce-products

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

2125.0. "DCE 2.0A and Digital UNIX 4.0B" by PRIME8::GUILES () Tue Jan 14 1997 14:29

T.RTitleUserPersonal
Name
DateLines
2125.1Using DFS ???VIRGIN::BILLBILL is my lastname !!!Wed Jan 15 1997 07:209
2125.2log file enclosed...PRIME8::GUILESWed Jan 15 1997 10:16263
2125.3DFS 2.0A currently broken on Digital UNIX 4.0BSMURF::STRANGESteve Strange, UNIX FilesystemsWed Jan 15 1997 10:514
2125.4Is this another problem, or is it setup/install issue?RDGENG::CHAMBERLINDanger! Do not Reverse PolarityWed Feb 12 1997 04:45197
Report from a software Partner.

Any suggestions on this please?

Thanks,
	Ian Chamberlin,


		Software Partner Engineering.

================================================================================

Digital products used
---------------------

DCEADK201            installed  DCE Application Developers Kit V2.0a
DCEADKMAN201         installed  DCE Application Developers Manual Pages
V2.0a
DCECDS201            installed  DCE Cell Directory Server V2.0a
DCEMAN201            installed  DCE Command Reference Manual Pages V2.0a
DCERTS201            installed  DCE Runtime Services V2.0a
DCESEC201            installed  DCE Security Server V2.0a

Digital UNIX V4.0B (Rev. 564)



when I restart DCE, some error messages appear in the file
/opt/dcslocal/dcesetup.log (see below) :

/opt/dcelocal/dcesetup.log created on Mon Feb 10 18:33:04 MET 1997
Digital DCE V2.0a (Rev. 515) for Digital UNIX
Machine: OSF1 vsu66.sema-grenoble.fr V4.0 564 alpha
% dcecp -c registry catalog
Error in getting initial login context.
/.../vsu66_cell/subsys/dce/sec/master
% dcecp -c clearinghouse show .:/vsu66_ch
Error in getting initial login context.
{CDS_CTS 1997-02-05-07:45:33.719150100/00-00-f8-22-9c-f9}
{CDS_UTS 1997-02-05-09:54:35.877353500/00-00-f8-22-9c-f9}
{CDS_ObjectUUID cf9c6e6c-7f2b-11d0-9371-0000f8229cf9}
{CDS_AllUpTo 1997-02-06-15:37:18.384189100/00-00-f8-22-9c-f9}
{CDS_DirectoryVersion 4.0}
{CDS_CHName /.../vsu66_cell/vsu66_ch}
{CDS_CHLastAddress 
 {Tower {ncacn_ip_tcp 1.1.130.5}}
 {Tower {ncadg_ip_udp 1.1.130.5}}}
{CDS_CHState on}
{CDS_CHDirectories 
 {{Dir_UUID d03b6d3d-7f2b-11d0-9371-0000f8229cf9}
  {Dir_Name /.../vsu66_cell}}
 {{Dir_UUID dc34987a-7f2b-11d0-9371-0000f8229cf9}
  {Dir_Name /.../vsu66_cell/subsys}}
 {{Dir_UUID dc73ecf0-7f2b-11d0-9371-0000f8229cf9}
  {Dir_Name /.../vsu66_cell/subsys/dce}}
 {{Dir_UUID dcc18f82-7f2b-11d0-9371-0000f8229cf9}
  {Dir_Name /.../vsu66_cell/subsys/dce/sec}}
 {{Dir_UUID dcf0f240-7f2b-11d0-9371-0000f8229cf9}
  {Dir_Name /.../vsu66_cell/subsys/dce/dfs}}
 {{Dir_UUID dd21d270-7f2b-11d0-9371-0000f8229cf9}
  {Dir_Name /.../vsu66_cell/subsys/dce/dfs/bak}}
 {{Dir_UUID dd591afa-7f2b-11d0-9371-0000f8229cf9}
  {Dir_Name /.../vsu66_cell/hosts}}
 {{Dir_UUID dd89d50a-7f2b-11d0-9371-0000f8229cf9}
  {Dir_Name /.../vsu66_cell/hosts/vsu66}}
 {{Dir_UUID de182364-7f2b-11d0-9371-0000f8229cf9}
  {Dir_Name /.../vsu66_cell/subsys/DEC}}
 {{Dir_UUID de6bbbdc-7f2b-11d0-9371-0000f8229cf9}
  {Dir_Name /.../vsu66_cell/subsys/DEC/pc}}
 {{Dir_UUID dec1dcce-7f2b-11d0-9371-0000f8229cf9}
  {Dir_Name /.../vsu66_cell/subsys/DEC/examples}}}
{CDS_ReplicaVersion 4.0}
{CDS_NSCellname /.../vsu66_cell}
*** Clearinghouse .:/vsu66_ch not reachable. Can not verify its state.
*** No replica found or reachable on this system; please verify
configuration
% dcecp -c clearinghouse show .:/vsu66_ch
Error in getting initial login context.
{CDS_CTS 1997-02-05-07:45:33.719150100/00-00-f8-22-9c-f9}
{CDS_UTS 1997-02-05-09:54:35.877353500/00-00-f8-22-9c-f9}
{CDS_ObjectUUID cf9c6e6c-7f2b-11d0-9371-0000f8229cf9}
{CDS_AllUpTo 1997-02-06-15:37:18.384189100/00-00-f8-22-9c-f9}
{CDS_DirectoryVersion 4.0}
{CDS_CHName /.../vsu66_cell/vsu66_ch}
{CDS_CHLastAddress 
 {Tower {ncacn_ip_tcp 1.1.130.5}}
 {Tower {ncadg_ip_udp 1.1.130.5}}}
{CDS_CHState on}
{CDS_CHDirectories 
 {{Dir_UUID d03b6d3d-7f2b-11d0-9371-0000f8229cf9}
  {Dir_Name /.../vsu66_cell}}
 {{Dir_UUID dc34987a-7f2b-11d0-9371-0000f8229cf9}
  {Dir_Name /.../vsu66_cell/subsys}}
 {{Dir_UUID dc73ecf0-7f2b-11d0-9371-0000f8229cf9}
  {Dir_Name /.../vsu66_cell/subsys/dce}}
 {{Dir_UUID dcc18f82-7f2b-11d0-9371-0000f8229cf9}
  {Dir_Name /.../vsu66_cell/subsys/dce/sec}}
 {{Dir_UUID dcf0f240-7f2b-11d0-9371-0000f8229cf9}
  {Dir_Name /.../vsu66_cell/subsys/dce/dfs}}
 {{Dir_UUID dd21d270-7f2b-11d0-9371-0000f8229cf9}
  {Dir_Name /.../vsu66_cell/subsys/dce/dfs/bak}}
 {{Dir_UUID dd591afa-7f2b-11d0-9371-0000f8229cf9}
  {Dir_Name /.../vsu66_cell/hosts}}
 {{Dir_UUID dd89d50a-7f2b-11d0-9371-0000f8229cf9}
  {Dir_Name /.../vsu66_cell/hosts/vsu66}}
 {{Dir_UUID de182364-7f2b-11d0-9371-0000f8229cf9}
  {Dir_Name /.../vsu66_cell/subsys/DEC}}
 {{Dir_UUID de6bbbdc-7f2b-11d0-9371-0000f8229cf9}
  {Dir_Name /.../vsu66_cell/subsys/DEC/pc}}
 {{Dir_UUID dec1dcce-7f2b-11d0-9371-0000f8229cf9}
  {Dir_Name /.../vsu66_cell/subsys/DEC/examples}}}
{CDS_ReplicaVersion 4.0}
{CDS_NSCellname /.../vsu66_cell}
*** Clearinghouse .:/vsu66_ch not reachable. Can not verify its state.
% cdscp disable clerk
% cdscp disable server
% dcecp -c registry stop ncacn_ip_tcp:localhost
  512 ??       S <      0:03.40 /opt/dcelocal/bin/secd -bootstrap
  512 ??       S <      0:03.40 /opt/dcelocal/bin/secd -bootstrap
  512 ??       S <      0:03.40 /opt/dcelocal/bin/secd -bootstrap
  512 ??       S <      0:03.40 /opt/dcelocal/bin/secd -bootstrap
  512 ??       S <      0:03.40 /opt/dcelocal/bin/secd -bootstrap
secd did not shut down
% kill 557
% kill 527
% kill 541
% kill 512
% kill 552
% kill 499
% kill -9 527
% kill -9 541
Checking for and removing CDS shared memory segments and semaphores
*** Can not verify security configuration; check status of daemons
*** Can not verify cds configuration; check status of daemons
*** Can not verify cds directory version; check status of daemons
% /opt/dcelocal/bin/dced -c
% dcecp -c server ping {e1af8308-5d1f-11c9-91a4-08002b14a0fa ncacn_ip_tcp

1.1.130.5 135}
dcecp server ping dced was successful
% /opt/dcelocal/bin/secd -bootstrap
% dcecp -c server ping {5b8c2fa8-b60b-11c9-be0f-08001e018fa0 ncacn_ip_tcp

1.1.130.5 1242}
dcecp server ping secd was successful
% dcecp -c secval activate {ncacn_ip_tcp:1.1.130.5[135]}
% /opt/dcelocal/bin/cdsadv  

Here, the startup is blocked (I stop it using ctrl C) : cdsadv doesn't
want
to start.

****************************
Condition before the restart :
****************************

Any access to the CDS (like rpc_ns_binding_export) produces the message :

rpc_ns_binding_export : Name service unavailable (dce / rpc).

In these conditions, our application cannot read/write to/from the CDS
database.



******************
DCE configuration :
******************

The DCE configuration of the machine is the following :

        Cellname:    vsu66_cell
        Hostname:    vsu66

        DCE daemon
        CDS master server
        Global Directory Agent
        Security master
        DCE SIA disabled
        Secval activated

    DCE daemon                    (dced)              pid: 2687
    Security Server daemon        (secd)              pid: 2702
    CDS Advertiser daemon         (cdsadv)            pid: 2721
    CDS Server daemon             (cdsd)              pid: 2735
    Name Service Interface daemon (nsid)              pid: 2754
    GDA daemon                    (gdad)              pid: 2728


*********
Questions :
*********

Is there a problem caused by a bad installation of DCE or UNIX ?

Have you ever hearded of similar problems ?

2125.5different problemTUXEDO::ZEEThere you go.Wed Feb 12 1997 14:2610
If cdsadv won't start, it could be several things.  First thing is
to check if the customer has the latest patches for Digital UNIX V4.0B.
There are several threads bug fixes that would affect DCE.  Patch ID
OSF410-400131 might fix cdsadv hanging.  I can't say for sure because
we haven't seen the problem here.  I don't know what the official
mechanism is to get the latest Digital UNIX patches, but internally,
you can get them via anonymous ftp from oskits.zk3.dec.com in
patches/osf/v4.0b/.

--Roger
2125.6Which patches ????VNASWS::HAUSBIts a hard life in the mountainsThu Feb 13 1997 10:388
Can anybody describe which patches I need to run DCE 2.0A on 4.0B ??

The osf400-080.tar is still valid ????


Thanks
G.H.
2125.7Re: DCE 2.0A and Digital UNIX 4.0BQUABBI::&quot;[email protected]&quot;Thu Feb 13 1997 13:4115
In article <[email protected]>, [email protected] (Its a hard life in the mountains) writes:
|>Can anybody describe which patches I need to run DCE 2.0A on 4.0B ??
|>The osf400-080.tar is still valid ????

	No, osf400-080.tar is ONLY valid for Digital UNIX V4.0.

							- Mustie


--
Mustafizur Rahman                           E-Mail: [email protected]
Project Leader, DCE for Digital UNIX         Phone: (508) 486-5150
Digital Equipment Corporation, Littleton, MA   FAX: (508) 486-7417
[posted by Notes-News gateway]