ITEM: FK7653L
DCE: Cannot start /opt/dcelocal/bin/dtsd
Response:
ENV:AIX 4.1.5, DCE 2.1, Model Unknown
PROBLEM:Customer is unable to configure a dtsd client.
ERROR message
cannot start /opt/dcelocl/bin/dtsd
Looked at the namespace
Listing the namespace produced many error messages
A directory for /.:/hosts/\ does not exist.
*ACTION TAKEN:Customer conferred with Customer.
Customer believes this is a problem with the cds cache for
this particular machine.
Customer is getting error messages about a missing object in
cds and this seems to be from the cds cache.
Stopped cds and sec on the master and cleaned the cache.
Ran cdscp dir list /.:/hosts/\ says dir does
not exist, but cdsli -rd shows this directory in the output.
Ran cdscp del child /.:/hosts/\
This solved the problem, cdsli and cdscp show the same info.
Customer proceeded to delete the principals in the registry
for this client machine.
Reconfigured the dce clients, a new principal/account was
created for this machine but there is no entry in cds
under /.:/hosts for this machine, this is despite the
information returned to stdout when the client is
configuring
----------------------------------------------------------------------
Waiting (up to 2 minutes) for cdsadv to find a CDS server.
Found a CDS server.
Modifying acls on hosts/\
Modifying acls on hosts/\/self
Modifying acls on hosts/\/cds-clerk
Modifying acls on hosts/\/profile
Modifying acls on /.:/lan-profile
CDS Clerk (cds_cl) configured successfully
Configuring DTS Clerk (dts_cl)...
Cannot start /opt/dcelocal/bin/dtsd
Current state of DCE configuration:
-----------------------------------------------------------------------
This configuration was done using an inhouse configuration script.
Customer is going to try to configure this client from the smit panels.
Successfully configured A dce client from smitty, Customer was able to
dce_login as cell_admin.
dcecp> dir list /.:/hosts Does NOT show a directory for the client
(\) that was just configured in SMIT
dcecp -c dir list /.:/hosts
/.../\/hosts/\ /.../\/hosts/\
/.../\/hosts/\ /.../\/hosts/\
/.../\/hosts/\
root@\ $ cdsli -rd
/.:/hosts
/.:/hosts/\
/.:/hosts/\
/.:/hosts/\
/.:/hosts/\
/.:/hosts/\
/.:/subsys
/.:/subsys/dce
/.:/subsys/dce/dfs
/.:/subsys/dce/sec
This is brand new machine (F40) which has never been configured into
this cell before and has one interface.
root@\ $ cdsli -rd !pg
(get_dirs): Error enumerating directories under /.:/hosts/\
Requested entry does not exist (dce / cds)
(get_dirs): Error enumerating directories under /.:/hosts/\
Requested entry does not exist (dce / cds)
/.:/hosts
/.:/hosts/\
/.:/hosts/\
/.:/hosts/\
/.:/hosts/\
/.:/hosts/\
/.:/subsys
/.:/subsys/dce
/.:/subsys/dce/dfs
/.:/subsys/dce/sec
root@\ $ dcecp
dcecp> dir show /.:/hosts/\
Error: Requested entry does not exist
dcecp> dir show /.:/hosts/\
Error: Requested entry does not exist
dcecp> dir list /.:/hosts/\
Error: Requested entry does not exist
dcecp> dir list /.:/hosts/\
/.../\/hosts/\/cds-clerk
/.../\/hosts/\/config
/.../\/hosts/\/dts-entity
/.../\/hosts/\/profile
/.../\/hosts/\/self
dcecp> dir list /.:/hosts
/.../\/hosts/\
/.../\/hosts/\
/.../\/hosts/\
/.../\/hosts/\
/.../\/hosts/\
Customer has been given permission to unconfigure \
and \ in order to clean up the namespace
Telnetted to the \ machine
It is configures as follows
Current state of DCE configuration:
cds_cl COMPLETE CDS Clerk
dts_cl PARTIAL DTS Clerk
rpc COMPLETE RPC Endpoint Mapper
sec_cl COMPLETE Security Client
root@\ $ lsdfs
Current state of DFS configuration:
dfs_cl COMPLETE DFS Client Machine
dfs_srv COMPLETE DFS File Server Machine
Next action: Customer has cleaned up the namespace on \ and
unconfigured \ and \.
He tried to reconfigure \ using smitty full config
and received the error above about dts.
\ shows the following
Current state of DCE configuration:
cds_cl COMPLETE CDS Clerk
rpc COMPLETE RPC Endpoint Mapper
sec_cl COMPLETE Security Client
dts_cl PARTIAL Dts Clerk
cdsli -rd on the server \ does NOT show a directory
called /.:/hosts/\.
Customer then went to the server and manually created a
directory and object under /.:/hosts.O.K.
Tried to do an admin only configuration for \ on the
server machine \.
This said sec_cl is already configured and proceeded
to
configure the cds_cl and returned.
Checking the namespace showed that the /.:/hosts/\
has NOT been created after the admin only config.
Next action: Logged onto machine \ and tried to configure a
DCE client several times.
The rpc and sec_cl configured successfully
Configure a cds_cl from the command line
root@\ $ mkdce -s \ -c \ cds_cl
Enter password for DCE account cell_admin:
Configuring CDS Clerk (cds_cl)...
Waiting (up to 2 minutes) for cdsadv to find a CDS server.
Found a CDS server.
Modifying acls on hosts/\
Modifying acls on hosts/\/self
Modifying acls on hosts/\/cds-clerk
Modifying acls on hosts/\/profile
Modifying acls on /.:/lan-profile
CDS Clerk (cds_cl) configured successfully
Current state of DCE configuration:
cds_cl COMPLETE CDS Clerk
rpc COMPLETE RPC Endpoint Mapper
sec_cl COMPLETE Security Client
tn \
root@\ $ cdsli -rd
/.:/hosts
/.:/hosts/\
/.:/hosts/\
/.:/hosts/\
/.:/subsys
/.:/subsys/dce
/.:/subsys/dce/dfs
/.:/subsys/dce/sec
root@\ $ dcecp -c dir list /.:/hosts
/.../\/hosts/\
/.../\/hosts/\
/.../\/hosts/\
Further investigation of the problem revealed that the
/.:/hosts/\ directory still existed in the namespace, but the
child pointer from /.:/hosts had been deleted. The reason
/.:/hosts/\ was still in existence was both it's creation
timestamp and update timestamps (CDS_CTS and CDS_UTS) were dated
in the year 2000. Further analysis of the CDS namespace revealed
there were several incorrect timestamps throughout. This situation
only occurs if the system clock is set forward, then the CDSD is
started and stopped, then the system clock is set back.
.The dcecp command 'clearinghouse repair /.:/\ -timestamp'
can be used to correct any timestamps that are marked in the future.
Except in ptfset 19 there is a deadlock condition in the cdsd that
prevents this command from working. An e-fix for the deadlock has
been built. This e-fix has been placed on rmds4.boulder.ibm.com.
.Contacted Customer and let him know the e-fix was available. He will
apply the efix and run the repair command, then he will contact us
and inform us of the results.
Customer called to say that after applying the cdsd he was unable to
start DCE. Upon examination of the system I discovered the
hosts/\/self keytab had been deleted. The customer was able
to restore the /var/dce/krb5/v5srvtab from a tape backup and we
were able to bring up DCE.
.We ran the timestamp repair command and it corrected the future time
stamps in the CDS namespace. We ran an admin unconfig of the \,
\, and \ systems to remove the orphaned directories in the
CDS namespace. We re-configured the DCE clients and were able to
successfully re-configure the DFS file servers.
.Everything is up and running. Closing call with
customer consent.
Support Line: DCE: Cannot start /opt/dcelocal/bin/dtsd ITEM: FK7653L
Dated: March 1998 Category: N/A
This HTML file was generated 99/06/24~13:30:14
Comments or suggestions?
Contact us