[797] in Moira
Hesiod problem this morning
daemon@ATHENA.MIT.EDU (David Krikorian)
Wed Oct 12 11:36:53 1994
Date: Wed, 12 Oct 94 11:36:49 -0400
From: David Krikorian <dkk@MIT.EDU>
To: op@MIT.EDU, moiradev@MIT.EDU
Cc: accounts@MIT.EDU
There was a Hesiod slowdown this morning with widespread affect.
Here's the story of the problem:
An accounts consultant manually registerd a user (with "moira") who
had been status 6 ("Enrolled/Not Registerable" -- email forwarding
only). The user was registered with a null name, which was obviously
no good. The user's account was immediately set back to status 6
(from status 1, "Active") and registered again, manually. This time a
valid username was used: "mleen".
A few things went wrong in AFS because the afs_*.pl incremental
scripts had invalid arguments. We fixed those yesterday. But also,
the user's original group (with no name) was still around. That is,
user mleen has two User Group lists, one with name "mleen" and one
with name "" (null).
This morning, the DCM generated a group.db file for hesiod containing
the following line:
.group HS UNSPECA ":*:7281:"
Hesiod was very slow until this line was deleted from the named data
files on Hesiod servers, and the named was restarted.
I have yet to delete the null group and its i_members entry, but that
seems like a pretty straight-forward and safe operation. Deleting the
null group will prevent this Hesiod problem from recurring tomorrow.
