Operating System - HP-UX
1752617 Members
4350 Online
108788 Solutions
New Discussion юеВ

nis client issue with hp ux 11.31

 
SOLVED
Go to solution
Sarjerao
Frequent Advisor

nis client issue with hp ux 11.31

Hello,
I have a strange problem with hp ux 11.31;
nis client unbale to start. Getting following error.
*************************
starting NIS CLIENT networking
starting up the rpcbind
rpcbind already started, using pid: 964
domainname qatlv.ndsoft.com
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 137.72.229.12
Sorry, I can't set up a udp connection to ypbind on host crab.
Checking NIS binding.
Bound to NIS server using domain qa.com
starting up the keyserv daemon
FAILURE CODE: 1
************************
While starting yp server syslog showing follwoing error---
Aug 18 22:44:21 crab syslog: ypbind: no entry in /var/yp/secureservers file
Aug 18 22:44:24 crab keyserv[4148]: svc_create: could not register prog 100029 vers 1 on ticlts
Aug 18 22:44:24 crab keyserv[4148]: rpc_negotiate_uid (ioctl:I_STR:TL_IOC_CREOPT): No such file or directory
Aug 18 22:44:24 crab keyserv[4148]: Couldn't negotiate for uid with loopback transport ticotsord
Aug 18 22:44:22 crab vmunix: WARNING: VxVM vxio V-5-0-23 Open on an spurious volume device (0x3000008) encountered. This device may be valid, but has not yet been configured in the kernel.
Aug 18 22:44:24 crab above message repeats 167 times
Aug 18 22:44:24 crab vmunix: tunopen(): CLONEOPEN not allowed
Aug 18 22:44:24 crab keyserv[4148]: svc_create: ticots: cannot open connection: no error specified
Aug 18 22:44:24 crab keyserv[4148]: /usr/sbin/keyserv: unable to create service for version 1
Aug 18 22:44:27 crab vmunix: WARNING: VxVM vxio V-5-0-23 Open on an spurious volume device (0x3000008) encountered. This device may be valid, but has not yet been configured in the kernel.
*****

/etc/rc.config.d/namesvrs configured properly.

You help appreciated.
8 REPLIES 8
TTr
Honored Contributor
Solution

Re: nis client issue with hp ux 11.31

Usually ticotsord and ticlts errors are caused by RPC. Post "rpcbind -p" output.

Consider Adding a logging and debugging options in /etc/rc.config.d/namesvrs in the YPSERV_OPTIONS and KEYSERV_OPTUIONS. Use something like
YPSERV_OPTIONS="-l /var/yp/ypserv.log"
KEYSERV_OPTIONS="-D"
Then check the log file and syslog for additional error details. This may tell you more about what is happening.

Steven E. Protter
Exalted Contributor

Re: nis client issue with hp ux 11.31

Shalom,

Perhaps pull the yp---- configuration from a working system? Preferably an 11.31 system but it may work from another OS level.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Sarjerao
Frequent Advisor

Re: nis client issue with hp ux 11.31

No log created with option specified;
YPSERV_OPTIONS="-l /var/yp/ypserv.log"

bash-3.2# rpcbind -d
checking netid "udp"
device /dev/udp present
netdir_getbyname for HOST_SELF succeeded
netdir_getbyname for HOST_SELF_CONNECT succeeded
netdir_getbyname for host HOST_SELF, service "rpcbind" succeeded
netdir_getbyname for host HOST_SELF_CONNECT, service "rpcbind" succeeded
checking netid "tcp"
device /dev/tcp present
netdir_getbyname for HOST_SELF succeeded
netdir_getbyname for HOST_SELF_CONNECT succeeded
netdir_getbyname for host HOST_SELF, service "rpcbind" succeeded
netdir_getbyname for host HOST_SELF_CONNECT, service "rpcbind" succeeded
checking netid "ticlts"
device /dev/tlclts present
dlopen of name-to-address library libstraddr.so.1 succeeded
netdir_getbyname for HOST_SELF succeeded
netdir_getbyname for HOST_SELF_CONNECT succeeded
netdir_getbyname for host HOST_SELF, service "rpcbind" succeeded
netdir_getbyname for host HOST_SELF_CONNECT, service "rpcbind" succeeded
checking netid "ticotsord"
device /dev/tlcotsod present
dlopen of name-to-address library libstraddr.so.1 succeeded
netdir_getbyname for HOST_SELF succeeded
netdir_getbyname for HOST_SELF_CONNECT succeeded
netdir_getbyname for host HOST_SELF, service "rpcbind" succeeded
netdir_getbyname for host HOST_SELF_CONNECT, service "rpcbind" succeeded
checking netid "ticots"
device /dev/tlcots present
dlopen of name-to-address library libstraddr.so.1 succeeded
netdir_getbyname for HOST_SELF succeeded
netdir_getbyname for HOST_SELF_CONNECT succeeded
netdir_getbyname for host HOST_SELF, service "rpcbind" succeeded
netdir_getbyname for host HOST_SELF_CONNECT, service "rpcbind" succeeded
TTr
Honored Contributor

Re: nis client issue with hp ux 11.31

I meant to write "rpcinfo -p".

> No log created with option specified
Did you restart the nis server? Maybe it does not get that far to create the log.

How about keyserv? Any additional debugging in syslog?
Sarjerao
Frequent Advisor

Re: nis client issue with hp ux 11.31

bash-3.2# rpcinfo -p
program vers proto port service
100000 4 tcp 111 rpcbind
100000 3 tcp 111 rpcbind
100000 2 tcp 111 rpcbind
100000 4 udp 111 rpcbind
100000 3 udp 111 rpcbind
100000 2 udp 111 rpcbind
bash-3.2#
Sarjerao
Frequent Advisor

Re: nis client issue with hp ux 11.31

Thanks lot for support.
I found the issue and fixed now. Done following >>>>
# /sbin/init.d/nfs.server stop
# /sbin/init.d/autofs stop
# /sbin/init.d/nfs.client stop
# /sbin/init.d/lockmgr stop
# /sbin/init.d/nfs.core stop

Then rebuild your /stand/ioconfig file by issuing the command:

# insf -e

Then see if you can get all the RPC daemons to start normally:

# /sbin/init.d/nfs.core start
# /sbin/init.d/lockmgr start
# /sbin/init.d/nfs.client start
# /sbin/init.d/autofs start
# /sbin/init.d/nfs.server start
#/sbin/init.d/nis.client start



Sarjerao
Frequent Advisor

Re: nis client issue with hp ux 11.31

Thanks all!!!!!!
TTr
Honored Contributor

Re: nis client issue with hp ux 11.31

I bet you looked at this. That's where I was heading too.

http://forums12.itrc.hp.com/service/forums/bizsupport/questionanswer.do?threadId=1151874