[Babase] uid, gid mapping problems on papio again

Hunter Matthews babase@www.eco.princeton.edu
Mon, 27 Jun 2005 11:06:59 -0400


My best guess[1] is that a high load on papio is causing a network
timeout when ypbind (the thing that says that user 2424 is 'kop') trys 
to hit the ypserver.

I have turned nscd ON, in an attempt to let it cache recent results.
Probably the best thing to do is see if this creaps up again once we
upgrade papio to the 2.6 kernel (which is far less prone to these sorts
of timeout shenanigans).

If ypbind were failing or DYING in some way, it would stay dead, not
fail and then come back - trust me, having audited the code for part of
it, if it has a hiccup its going down and staying down. Thus my theory
that its a temporary timeout/resource issue.

[1] The word guess in that sentence should be noted with care.



On Sun, 2005-06-26 at 17:07, Karl O. Pinc wrote:
> Followup:
> 
> uid=2424(kop) gid=2424(kop) groups=2424(kop),1005(alblab),1026(babase)
> [kop@papio conversion]$ date
> Sun Jun 26 16:17:26 EDT 2005
> 
> 
> Karl <kop@meme.com>
> Free Software:  "You don't pay back, you pay forward."
>                   -- Robert A. Heinlein
-- 
Hunter Matthews                          Unix / Network Administrator
Office: BioScience 145/244               Duke Univ. Biology Department
Key: F0F88438 / FFB5 34C0 B350 99A4 BB02  9779 A5DB 8B09 F0F8 8438
Never take candy from strangers. Especially on the internet.