Very Computer

I have a solaris 7 machine running as an nis+ server in nis compatibilty
mode.  I set up RH Linux 6.2 as a nisplus client in the "compat" mode
for passwd, group, and shadow entries in the nsswitch.conf file.

Everything seemed to be working OK.  "ypcat passwd.byname" worked, the
"compat" features worked (i.e. -/+ in the passwd file did what I
expected), host lookups worked, etc., etc.

Then I took the network down for some routine maintenance, and upon
reboot, I can no longer get ypbind to bind to my domain.  I get the
following error every time...

  bash# ypbind --debug
  cleared entry for domain domain.name.edu: server 0.0.0.0, port 0
  parsing config file
  Trying entry: ypserver XXX.XXX.XXX.37

  parsed ypserver XXX.XXX.XXX.37
  bindto_server: domain domain.name.edu, host XXX.XXX.XXX.37
  clnt_create for server XXX.XXX.XXX.37
failed

I think the kicker here is the last line of the error message.  The
strange part is that ypbind doesn't die, it just sits there useless.

I've gone back through all the steps I followed in the HOWTOs for
setting up NIS clients on Linux.  The Solaris server was set up
according to their "Solaris Naming Setup and Configuration Guide"
manual, and I think it takes care of everything on the server side at
boot time, but perhaps this is a server problem (of course their logging
facilities suck, so it's difficult to track down the problem in
Solaris).

Any ideas?

-JR

Sent via Deja.com http://www.deja.com/
Before you buy.

shure? you use ypbind, which states you are setting up an nis (=yp) client,
not nisplus.

Quote:> in the "compat" mode
> for passwd, group, and shadow entries in the nsswitch.conf file.

how do you find your yp-server, rsp. how do you tell ypbind which ypserver
to use? are you running in broadcast mode? do you use a yp.conf, ypsesrvers
e.a.?

Quote:> Then I took the network down

the whole network or just your linux nic?

Quote:> for some routine maintenance, and upon
> reboot, I can no longer get ypbind to bind to my domain.  I get the
> following error every time...

>   bash# ypbind --debug
>   cleared entry for domain domain.name.edu: server 0.0.0.0, port 0

is domain.name.edu your entry?
is ypwhich reporting correct?

gerhard

Well, not really.  My default nsswitch.conf file in Linux had "nisplus",
so I tried
this.  It worked!  After I started experiencing problems, I changed
everything to
simply "nis", and still had no luck binding to the domain server.

Quote:> > in the "compat" mode
> > for passwd, group, and shadow entries in the nsswitch.conf file.

> how do you find your yp-server, rsp. how do you tell ypbind which ypserver
> to use? are you running in broadcast mode? do you use a yp.conf, ypsesrvers
> e.a.?

In the yp.conf file, I have the line:

  ypserver XXX.XXX.XXX.37

...where "XXX..." is the ip number of my server.

Quote:

> > Then I took the network down

> the whole network or just your linux nic?

We took the whole network down, including both the server, and the
client.

Quote:

> > for some routine maintenance, and upon
> > reboot, I can no longer get ypbind to bind to my domain.  I get the
> > following error every time...

> >   bash# ypbind --debug
> >   cleared entry for domain domain.name.edu: server 0.0.0.0, port 0

> is domain.name.edu your entry?
> is ypwhich reporting correct?

Sorry, the "domain.name.edu" is not my actual domain.  I just
substituted this
in for my real domain name, which is similar to my university's internet
domain name (I do realize they do not have to be this way, it was just
convenient).  "ypwhich" simply says that the domain is not bound.

Does this give you a better idea?

-EJR

Did you start ypbind on boot? Check with "chkconfig --list ypbind".
I've described very similar configuration (the only difference is
Solaris-based NIS server, instead of NIS+) here:

  http://www.geocities.com/ivanov_andrei/nis/

--
andrei