[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

2170.0. "DCE on ALPHAbook1 failing on setup" by MUFFIT::gerry (Gerry Reilly) Wed Feb 26 1997 03:59

I am trying to setup the DCE on a Tadpole ALPHAbook1 running Digital UNIX
V4.0b.  No matter how I approach the setup - either as a client, or even
just starting the dced manually with appropriate flags - the startup
fails with the same error-

        Initializing dced (dced)...
1997-02-26-08:27:33.832+00:00I429.497 dced FATAL rpc general dgclive.c 374 0x3ffc0183508
(rpc__dg_maintain_init) Can't create UUID
*** Error in initializing dced (exiting)

Any thoughts or suggestions appreciated.

-gerry


T.RTitleUserPersonal
Name
DateLines
2170.1The SolutionMUFFIT::gerryGerry ReillyWed Feb 26 1997 09:5920
As this was quite urgent I decided to debug this one myself.

The problem is caused by the fact that the routine right at the bottom
of the stack when doing a uuid_create, dce_get_802_addr, only checks
the first four network interfaces.  If dce_get_802_addr doesn't find
an interface amongst these four that is configured and has the right set of 
IFF flags (up, running, and broadcast) then it returns an error code.
This then causes uuid_create to fail and the dced not to initialise.

Unfortunately, the Tadpole shows more than four interfaces, and the fifth
one in the list was the ethernet i/f.

The workaround for me was to disable slip and therefore remove one
interface from the system, and therefore the physical address could
be obtained by the call to dce_get_802_addr.  The fix looks to me
to be to check all interfaces (rather than the first four) to see
if there is an interface that can return a default hardware address
that can be used to generate the uuid.

-gerry