Sponsored Content
Full Discussion: ypbind wont bind?
Top Forums UNIX for Dummies Questions & Answers ypbind wont bind? Post 302165728 by Colton on Friday 8th of February 2008 03:15:21 PM
Old 02-08-2008
I've tried this before as well, here is the output:

[root@node1 yp]# ./ypinit -s 192.168.0.2
Can't enumerate maps from 192.168.0.2. Please check that it is running.
[root@node1 yp]#

I feel like it's an issue on the master still, however...

[root@head colton]# rpcinfo -p localhost
program vers proto port service
100000 4 tcp 111 portmapper
100000 3 tcp 111 portmapper
100000 2 tcp 111 portmapper
100000 4 udp 111 portmapper
100000 3 udp 111 portmapper
100000 2 udp 111 portmapper
100000 4 0 111 portmapper
100000 3 0 111 portmapper
100000 2 0 111 portmapper
100024 1 udp 32768 status
100024 1 tcp 51059 status
100004 2 udp 757 ypserv
100004 1 udp 757 ypserv
100004 2 tcp 760 ypserv
100004 1 tcp 760 ypserv
100007 2 udp 794 ypbind
100007 1 udp 794 ypbind
100007 2 tcp 797 ypbind
100007 1 tcp 797 ypbind
100021 1 udp 32769 nlockmgr
100021 3 udp 32769 nlockmgr
100021 4 udp 32769 nlockmgr
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 4 udp 2049 nfs
100021 1 tcp 33947 nlockmgr
100021 3 tcp 33947 nlockmgr
100021 4 tcp 33947 nlockmgr
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100003 4 tcp 2049 nfs
100009 1 udp 611 yppasswdd
100011 1 udp 638 rquotad
100011 2 udp 638 rquotad
100011 1 tcp 641 rquotad
100011 2 tcp 641 rquotad
100005 1 udp 32773 mountd
100005 1 tcp 52384 mountd
100005 2 udp 32773 mountd
100005 2 tcp 52384 mountd
100005 3 udp 32773 mountd
100005 3 tcp 52384 mountd
600100069 1 udp 707 fypxfrd
600100069 1 tcp 709 fypxfrd
[root@head colton]#

...still looks to me like everything is running, hence my frustration.
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Apache wont start

Hi, like a lot of people that post here, I am new at UNIX. The only UNIX I have ever messed with is my iBook running MacOSX (10.1). I have a grasp of the basic commands and understanding of the system but only to a point. I searched the archive and FreeBSD.org and apache.org but I couldn't find... (4 Replies)
Discussion started by: Alpha_Harblo
4 Replies

2. UNIX for Dummies Questions & Answers

Monitor wont come on...

I know this may not be the right forum, but here goes. Last night I was playing my favorite game Everquest and my monitor goes blank... I was able to save out of my game and shut it down... My question is this: I thought my monitor had died but this morning I was able to get it to come back... (6 Replies)
Discussion started by: Kelam_Magnus
6 Replies

3. Solaris

file wont remove

check this out ls -l nmo* -rwsr-s--- 1 root dba 19312 Mar 31 14:44 nmo -rw-r----- 1 oracle dba 0 May 19 2004 nmo0 -rwxr-x--- 1 oracle dba 16512 Mar 31 14:44 nmocat # rm nmo0 nmo0: No such file or directory # id uid=0(root) gid=1(other) what... (8 Replies)
Discussion started by: csaunders
8 Replies

4. Solaris

SMC wont start

Today I attempted to use SMC for the first time on SUNSVR01 since 4 November. The SMC toolbox loads just fine but when I attempt to run any of the tools in SMC, I get red stop signs with labels like "com.sun.admin.hostmgr.client.vhostmgr" in the GUI. At the bottom of the screen, I get the... (0 Replies)
Discussion started by: wjseaman
0 Replies

5. Solaris

ypbind - multiple instances starting

I have built this Solaris 10 server, uses NIS. When the server starts up, two instances of ypbind start. This prevents the server from binding to any domain. The SMF in turn prevents any other network services (sshd and the like) from starting up. Has anyone seen this problem before? (0 Replies)
Discussion started by: blowtorch
0 Replies

6. HP-UX

Wont boot

I am new to HP-UX. I have a external SCSI drive with HP-UX on it. I was trying to clone it to another external scsi drive. I added the new drive to existing LVM. Then I used dd command. But it failed with I/O error. Now I cannot boot it from original drive. It's saying panic: LVM: Configuration... (11 Replies)
Discussion started by: forhad
11 Replies

7. HP-UX

ypbind start/stop

Hi, How to start or stop ypbind on HP-UX machine. Searched a little but could not find. thanks, (2 Replies)
Discussion started by: jredx
2 Replies

8. AIX

check the status of ypbind

hello , How do i to check the status of ypbind on AIX(5.3) platform ? Thanks AVK Linux (1 Reply)
Discussion started by: avklinux
1 Replies

9. Shell Programming and Scripting

script wont run

$ ls -l total 44 drwx------ 2 ivanachu users 512 Dec 6 19:15 VILEARN -rw------- 1 ivanachu users 74 Dec 5 18:42 cond -rwx------ 1 ivanachu users 97 Dec 5 21:30 cond2 -rwxrwxrwx 1 ivanachu users 4979 Feb 10 22:42 createHAqmgr.ksh -rw------- 1 ivanachu users 28 Dec 4... (10 Replies)
Discussion started by: ivanachukapawn
10 Replies
rpcinfo(1M)                                               System Administration Commands                                               rpcinfo(1M)

NAME
rpcinfo - report RPC information SYNOPSIS
rpcinfo [-m | -s] [host] rpcinfo -p [host] rpcinfo -T transport host prognum [versnum] rpcinfo -l [-T transport] host prognum versnum rpcinfo [-n portnum] -u host prognum [versnum] rpcinfo [-n portnum] -t host prognum [versnum] rpcinfo -a serv_address -T transport prognum [versnum] rpcinfo -b [-T transport] prognum versnum rpcinfo -d [-T transport] prognum versnum DESCRIPTION
rpcinfo makes an RPC call to an RPC server and reports what it finds. In the first synopsis, rpcinfo lists all the registered RPC services with rpcbind on host. If host is not specified, the local host is the default. If -s is used, the information is displayed in a concise format. In the second synopsis, rpcinfo lists all the RPC services registered with rpcbind, version 2. Note that the format of the information is different in the first and the second synopsis. This is because the second synopsis is an older protocol used to collect the information displayed (version 2 of the rpcbind protocol). The third synopsis makes an RPC call to procedure 0 of prognum and versnum on the specified host and reports whether a response was received. transport is the transport which has to be used for contacting the given service. The remote address of the service is obtained by making a call to the remote rpcbind. The prognum argument is a number that represents an RPC program number (see rpc(4)). If a versnum is specified, rpcinfo attempts to call that version of the specified prognum. Otherwise, rpcinfo attempts to find all the reg- istered version numbers for the specified prognum by calling version 0, which is presumed not to exist; if it does exist, rpcinfo attempts to obtain this information by calling an extremely high version number instead, and attempts to call each registered version. Note that the version number is required for -b and -d options. The EXAMPLES section describe other ways of using rpcinfo. OPTIONS
-T transport Specify the transport on which the service is required. If this option is not specified, rpcinfo uses the transport specified in the NETPATH environment variable, or if that is unset or NULL, the transport in the netconfig(4) data- base is used. This is a generic option, and can be used in conjunction with other options as shown in the SYNOPSIS. -a serv_address Use serv_address as the (universal) address for the service on transport to ping procedure 0 of the specified prognum and report whether a response was received. The -T option is required with the -a option. If versnum is not specified, rpcinfo tries to ping all available version numbers for that program number. This option avoids calls to remote rpcbind to find the address of the service. The serv_address is specified in universal address format of the given transport. -b Make an RPC broadcast to procedure 0 of the specified prognum and versnum and report all hosts that respond. If transport is specified, it broadcasts its request only on the specified transport. If broadcasting is not supported by any transport, an error message is printed. Use of broadcasting should be limited because of the potential for adverse effect on other systems. -d Delete registration for the RPC service of the specified prognum and versnum. If transport is specified, unregister the service on only that transport, otherwise unregister the service on all the transports on which it was regis- tered. Only the owner of a service can delete a registration, except the superuser, who can delete any service. -l Display a list of entries with a given prognum and versnum on the specified host. Entries are returned for all transports in the same protocol family as that used to contact the remote rpcbind. -m Display a table of statistics of rpcbind operations on the given host. The table shows statistics for each version of rpcbind (versions 2, 3 and 4), giving the number of times each procedure was requested and successfully ser- viced, the number and type of remote call requests that were made, and information about RPC address lookups that were handled. This is useful for monitoring RPC activities on host. -n portnum Use portnum as the port number for the -t and -u options instead of the port number given by rpcbind. Use of this option avoids a call to the remote rpcbind to find out the address of the service. This option is made obsolete by the -a option. -p Probe rpcbind on host using version 2 of the rpcbind protocol, and display a list of all registered RPC programs. If host is not specified, it defaults to the local host. This option is not useful for IPv6; use -s (see below) instead. Note that version 2 of the rpcbind protocol was previously known as the portmapper protocol. -s Display a concise list of all registered RPC programs on host. If host is not specified, it defaults to the local host. -t Make an RPC call to procedure 0 of prognum on the specified host using TCP, and report whether a response was received. This option is made obsolete by the -T option as shown in the third synopsis. -u Make an RPC call to procedure 0 of prognum on the specified host using UDP, and report whether a response was received. This option is made obsolete by the -T option as shown in the third synopsis. EXAMPLES
Example 1: RPC services. To show all of the RPC services registered on the local machine use: example% rpcinfo To show all of the RPC services registered with rpcbind on the machine named klaxon use: example% rpcinfo klaxon The information displayed by the above commands can be quite lengthy. Use the -s option to display a more concise list: example% rpcinfo -s klaxon program vrsn netid(s) service owner 100000 2,3,4 tcp,udp,ticlts,ticots,ticotsord rpcbind superuser 100008 1 ticotsord,ticots,ticlts,udp,tcp walld superuser 100002 2,1 ticotsord,ticots,ticlts,udp,tcp rusersd superuser 100001 2,3,4 ticotsord,ticots,tcp,ticlts,udp rstatd superuser 100012 1 ticotsord,ticots,ticlts,udp,tcp sprayd superuser 100007 3 ticotsord,ticots,ticlts,udp,tcp ypbind superuser 100029 1 ticotsord,ticots,ticlts keyserv superuser 100078 4 ticotsord,ticots,ticlts - superuser 100024 1 ticotsord,ticots,ticlts,udp,tcp status superuser 100021 2,1 ticotsord,ticots,ticlts,udp,tcp nlockmgr superuser 100020 1 ticotsord,ticots,ticlts,udp,tcp llockmgr superuser To show whether the RPC service with program number prognum and version versnum is registered on the machine named klaxon for the transport TCP use: example% rpcinfo -T tcp klaxon prognum versnum To show all RPC services registered with version 2 of the rpcbind protocol on the local machine use: example% rpcinfo -p To delete the registration for version 1 of the walld (program number 100008) service for all transports use: example# rpcinfo -d 100008 1 or example# rpcinfo -d walld 1 ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ SEE ALSO
rpcbind(1M), rpc(3NSL), netconfig(4), rpc(4), attributes(5) SunOS 5.10 13 Jul 2001 rpcinfo(1M)
All times are GMT -4. The time now is 10:00 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy