| Title: | DECdns - Digital's Distributed Name Service |
| Notice: | not to be confused with DNS: Domain Name Service (Kits: 1420,947)) |
| Moderator: | BULEAN::WHEATER |
| Created: | Tue Apr 14 1987 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 1443 |
| Total number of notes: | 5833 |
A DNS daemon on Digital UNIX V4.0 gives often transient access
problems.
On that particular system (Alpha-1000 - 128 MB) about 400 directories
are spread over 7 Clearinghouses, for a total of � 150 MB disk space used
for these clearinghouses. On the whole network more than 50 systems
are part of the DNS infrastructure (dnsd's).
When SHOW, SET, etc... operations are done, involving one of these
clearinghouses, sometimes the command is executed about immediately,
sometimes an error message is returned. This is true for any kind
of command, and the same command sometimes (50%) is executed successfully,
sometimes (50%) returning some error message.
We have not seen this behaviour before on Digital UNIX V3.2, nor on
ULTRIX V4.x, altough the size of DNS used to be 30% smaller on the
former systems.
The following 2 error messages are being shown :
1).
Error on entity: bc:.mam
dnserr 0
SPR. NO MESSAGE KEY dnserr 0
2).
Error on entity: bc:.vtl
Insufficient rights to perform requested operation
After a while, reexecuting the same command, the command is often successfull.
Another strange behaviour is that the command
show dns server cle <clearinghouse> all status
under those circumstances intermittently shows the state
"On" followed by the list of the directories contained in the
clearinghouse,
or "On" without that same list.
Is there any resource problem here ? How can we trace the fundamental
problem. Are there any particular tuning issues in this case, where a large
DNS environment is put on a single system ? What can we do to improve
the responsiveness ?
Kind regards,
Dominique.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1434.1 | BRSADV::PACCO | Horum omnium fortissimi sunt Belgae | Tue Apr 01 1997 09:58 | 17 | |
Another symptom is the following:
The directory skulk status becomes:
Last status = Failure
Phase = Spread
Reason = Failed to copy updates to clearinghouse bc:.dlrh01_ch
Reason = Software error detected in server
This is not recovered by the background skulk process. The only way out
is a 'set directory ... to new epoch ...'
Which are the possible causes for "Software error detected in server" ?
Kind regards,
Dominique.
| |||||
| 1434.2 | Unable to communicate with any DECdns server | BRSADV::PACCO | Horum omnium fortissimi sunt Belgae | Mon Apr 14 1997 06:31 | 70 |
Another expression of the same problem:
dns> sho dir .oc
SHOW
DIRECTORY bc:.oc
AT 14-APR-1997:11:25:53
DNS$ACS (set) = :
Flags = none
Rights = read, write, delete, test,
control
(V) Principal = bc:.pl1.m.mpl105.DNS$SERVER
DNS$ACS (set) = :
Flags = none
Rights = read, write, delete, test,
control
(V) Principal = bc:.pl1.m.dpl101.DNS$SERVER
DNS$ACS (set) = :
Flags = authenticated
Rights = read, write, delete, test,
control
(V) Principal = bc:.dpl101_ch
DNS$ACS (set) = :
Flags = propagate
Rights = read, test
(V) Principal = bc:.*...
DNS$ACS (set) = :
Flags = default, propagate
Rights = read, test
(V) Principal = bc:.*...
DNS$ACS (set) = :
Flags = propagate, group
Rights = read, write, delete, test,
control
Group = bc:.dns_admin
DNS$ACS (set) = :
Flags = default, propagate, group
Rights = read, write, delete, test,
control
Group = bc:.dns_admin
DNS$ACS (set) = :
Flags = propagate, group
Rights = control
Group = bc:.chr_admin
DNS$AllUpTo =
1997-04-14-05:36:35.162/08-00-2b-e6-d7-d0
DNS$Convergence =
DNS$CTS =
DNS$DirectoryVersion =
DNS$Epoch =
DNS$LastSkulk =
DNS$LastUpdate =
DNS$ParentPointer =
DNS$Replicas =
DNS$ReplicaState =
DNS$ReplicaType =
DNS$ReplicaVersion =
DNS$sKULKsTATUS =
DNS$UTS =
Error on entity: bc:.oc
Unable to communicate with any DECdns server
Function: dnsReadAttrValue
Error on entity: bc:.oc
Unable to communicate with any DECdns server
Function: dnsReadAttrValue
Error on entity: bc:.oc
Unable to communicate with any DECdns server
Function: dnsReadAttrValue
...
| |||||