Interpreting NIS ypserv.log

Rosli Ahmad — Tue, 15 Nov 2005 04:04:33 GMT

Hi,
We have NIS running in environment all this while, but lately we notice our slave machines load shot up to 100%. We then run the debug mode but have problem in interpreting the ypserv log.

We think it's the ypdb_* calls below are the culprit as these entries doesn't exist under normal circumstances.

<>
connect from 172.30.xxx.86
ypdb_close_all() called
ypdb_close_all (mydomain/group.bygid|0)
ypdb_close_all (mydomain/passwd.byuid|1)
ypdb_close_all (mydomain/passwd.byname|2)
ypdb_open("mydomain", "passwd.byname")
->Returning OK!
Opening: mydomain/passwd.byname (0) 8052be8
-> First value returned.
ypproc_all_2_svc(): [From: 172.30.xxx.193:960]
domain = "mydomain"
map = "passwd.byname"
ypdb_open("mydomain", "passwd.byname")
Found: mydomain/passwd.byname (2)
ypdb_close() called
connect from 172.30.xxx.193
ypdb_close_all() called
ypdb_close_all (mydomain/group.bygid|0)
ypdb_close_all (mydomain/passwd.byuid|1)
ypdb_close_all (mydomain/passwd.byname|2)
ypdb_open("mydomain", "passwd.byname")
->Returning OK!
Opening: mydomain/passwd.byname (0) 8052bf8
-> First value returned.
ypdb_close() called
.
.
.
<>

Does anyone ever interpret the ypserv.log or aware of any reference material we can refer to?

We're practically in hot soup already.

Thanks.

Re: Interpreting NIS ypserv.log

Steven E. Protter — Tue, 15 Nov 2005 04:29:53 GMT

Hello Rosli,

Hot soup? Sounds like a good thing? Guess not.

Try doing some logins on the slave server, direct or via su - username

See if the logs produce anything interesting.

Is there perhaps a Master NIS server offline?

SEP

Re: Interpreting NIS ypserv.log

Rosli Ahmad — Tue, 15 Nov 2005 21:18:04 GMT

Hi Peter,
No, you wouldn't want to taste this soup...

The login is fine so is the NIS master. We just don't understand why the ypdb_* keep happening.

Any good link describing NIS in details, explaining what ypdb_* is all about?

Thanks.

topic Re: Interpreting NIS ypserv.log in Operating System - HP-UX

Interpreting NIS ypserv.log

Re: Interpreting NIS ypserv.log

Re: Interpreting NIS ypserv.log