topic Re: ypbind failure in Operating System - HP-UX

ypbind failure

George Liu_4 — Mon, 15 Nov 2004 16:10:07 GMT

That is a working system for a long time. Suddenly found nis accounts are not there but ypcat passwd still display all nis accounts. restart the nis.client got the following messages,

# ./nis.client start
starting NIS CLIENT networking
starting up the rpcbind
rpcbind already started, using pid: 688
domainname earth
starting up the Network Information Service
starting up the ypbind daemon
FAILURE CODE: 1
calling ypset with 172.16.251.60
Sorry, I can't set up a udp connection to ypbind on host x25a.awc.
Checking NIS binding.
Bound to NIS server using domain earth.
starting up the keyserv daemon
/usr/sbin/keyserv

Re: ypbind failure

Steven E. Protter — Mon, 15 Nov 2004 16:27:47 GMT

Try killing the current yp daemon prior to restart. The system thinks its running. Thtat could be because something is running oir the process has a file with the process id saved.

Kill and re-run see if that helps.

Make sure all filesystems are mounted, especially /var

SEP

Re: ypbind failure

George Liu_4 — Mon, 15 Nov 2004 16:42:39 GMT

reboot the system and still getting the error... From syslog, it says
syslog: ypbind: /var/yp/secureservers line 17: netmask does not match network

Apparantly the line 17 has no problem that is

255.255.255.0 172.16.251.60

comment this line out and now /var/yp/secureservers is empty

restart the ypbind, got

# ./nis.client start
starting NIS CLIENT networking
starting up the rpcbind
rpcbind already started, using pid: 689
domainname earth
starting up the Network Information Service
starting up the ypbind daemon
/usr/lib/netsvc/yp/ypbind
calling ypset with 172.16.251.60
Sorry, ypbind on host x25a.awc has rejected your request.
Checking NIS binding.
Bound to NIS server using domain earth.
starting up the keyserv daemon
/usr/sbin/keyserv

There is no useful message logged on syslog at this time.

Re: ypbind failure

Robert-Jan Goossens — Mon, 15 Nov 2004 16:54:14 GMT

Hi,

Check this doc.

"ypset: Sorry, I can't set up a udp connection to ypbind on host"
DocId: KBRC00005709

Europe
http://www5.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000074024259

US
http://www2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000074024259

Hope this helps,
Robert-Jan

Re: ypbind failure

George Liu_4 — Mon, 15 Nov 2004 18:13:54 GMT

add "-ypset" in YP_BIND_OPTION in namesvrs files, and restart ypbind, yields,
# ./nis.client start
starting NIS CLIENT networking
starting up the rpcbind
rpcbind already started, using pid: 691
domainname earth
starting up the Network Information Service
starting up the ypbind daemon
ypbind will not use the server list available in the file /var/yp/binding//ypservers for binding purpose. Also if ypbind is invoked with -broadcast option, then -broadcast option is ignored.
/usr/lib/netsvc/yp/ypbind -ypset
calling ypset with 172.16.251.60
Checking NIS binding.
Bound to NIS server using domain earth.
starting up the keyserv daemon
/usr/sbin/keyserv

At this time, ypcat passwd displays all nis accounts, but the nis accounts are not reachable

# su - gtest
su: Unknown id: gtest

Re: ypbind failure

Ermin Borovac — Mon, 15 Nov 2004 21:53:30 GMT

Please try restarting password caching daemon.

# /sbin/init.d/pwgr stop
# /sbin/init.d/pwgr start

Re: ypbind failure

George Liu_4 — Tue, 16 Nov 2004 09:19:09 GMT

pwgrd daemon fixed the problem. So is pwgrd necessary to make nis client working? Any document for this? Thanks a lot

Re: ypbind failure

Ermin Borovac — Tue, 16 Nov 2004 18:14:14 GMT

Password caching daemon tends to cache NIS information and it won't update automatically.

You don't need to have pwgrd running, it can be disabled without adverse consequences to the system.

See pwgrd(1M) for more information.

Re: ypbind failure

George Liu_4 — Wed, 17 Nov 2004 09:06:41 GMT

Problem is when I stop pwgrd, nis user couldn't be reached. There may be bugs somewhere.