10 More Discussions You Might Find Interesting
1. AIX
Hello,
I was trying to find information about below rpcbind issue and how can I fix it so that, it wont happen again.
Below is the one of the vulnerability from my security team,
RPC
service name: portmapper
service protocal: udp
Portmapper found at: 327xx
service port: 327xx
... (2 Replies)
Discussion started by: system.engineer
2 Replies
2. AIX
Hi,
I am trying to implement a service on AIX based on ONCRPC protocal and I want to use a RPC library called oncrpc4j because it is a non-blocked i/o library. I found it works fine on my work machine (WIndows 7) but failed on my AIX work station. The author of oncrpc4j told me that check that... (1 Reply)
Discussion started by: derekhsu
1 Replies
3. Solaris
Hello all,
I have read just about every rpcbind not starting thread and article on the internet it seems, but I have not found a solution to my problem as of yet. I have a solaris 10 server that has been running with no problems for a while. The other day it crashed and would not boot to the gui... (2 Replies)
Discussion started by: Madrox72
2 Replies
4. Ubuntu
Hi I am trying to configure NIS client on my Ubuntu 12.04.
But I could not put portmap without uninstalling rpcbind.
Do I need to have rpcbind there on the server, or how can I have both portmap and rpcbind at same time there on the server, because it's having conflict. (1 Reply)
Discussion started by: nixhead
1 Replies
5. Linux
Hi guys,
i explain my problem:
I've FC10 64bit installed on a server Dell R410.
When i boot the system with eth0 or eth1 linked (only one eth linked), all work fine and the system start normally.
When i boot the system with eth0 + eth1 linked,
the system hang when the rpcind service... (1 Reply)
Discussion started by: andreaden
1 Replies
6. Solaris
Hello experts..
What is the meaning of " RPC : rpcbind failure" in NFS ? What would be the reason for that? How can i resolve that issue?
give me all aspects (all views)..
Thanks in advance... (1 Reply)
Discussion started by: younus_syed
1 Replies
7. UNIX for Dummies Questions & Answers
I'm just going to throw this out there because I have no clue what is causing this problem or how to fix it. selinux is not enabled nor is any sort of firewall. (To my knowledge -- I did a kickstart install with firewall --disabled )
# rpcinfo
program version netid address ... (1 Reply)
Discussion started by: Colton
1 Replies
8. UNIX for Dummies Questions & Answers
Hi all, dummy here.... I have major errors on entering the shell. On login I get:
-bash: dircolors: command not found
-bash: tr: command not found
-bash: fgrep: command not found
-bash: grep: command not found
-bash: grep: command not found
-bash: id: command not found
-bash: [: =: unary... (12 Replies)
Discussion started by: wcmmlynn
12 Replies
9. AIX
$ errpt | more
IDENTIFIER TIMESTAMP T C RESOURCE_NAME DESCRIPTION
3074FEB7 0802050205 T H fscsi1 ADAPTER ERROR
B8113DD1 0802050205 T H fcs1 LINK ERROR
B8113DD1 0802050205 T H fcs1 LINK ERROR
3074FEB7 0802050205 T H fscsi0 ADAPTER ERROR
B8113DD1 ... (2 Replies)
Discussion started by: mcastill66
2 Replies
10. UNIX for Advanced & Expert Users
$ errpt | more
IDENTIFIER TIMESTAMP T C RESOURCE_NAME DESCRIPTION
3074FEB7 0802050205 T H fscsi1 ADAPTER ERROR
B8113DD1 0802050205 T H fcs1 LINK ERROR
B8113DD1 0802050205 T H fcs1 LINK ERROR
3074FEB7 0802050205 T H fscsi0 ADAPTER ERROR
B8113DD1 ... (0 Replies)
Discussion started by: mcastill66
0 Replies
LEARN ABOUT X11R4
rpcbind
rpcbind(1M) System Administration Commands rpcbind(1M)
NAME
rpcbind - universal addresses to RPC program number mapper
SYNOPSIS
rpcbind [-d] [-w]
DESCRIPTION
rpcbind is a server that converts RPC program numbers into universal addresses. It must be running on the host to be able to make RPC calls
on a server on that machine.
When an RPC service is started, it tells rpcbind the address at which it is listening, and the RPC program numbers it is prepared to serve.
When a client wishes to make an RPC call to a given program number, it first contacts rpcbind on the server machine to determine the
address where RPC requests should be sent.
rpcbind should be started before any other RPC service. Normally, standard RPC servers are started by port monitors, so rpcbind must be
started before port monitors are invoked.
When rpcbind is started, it checks that certain name-to-address translation-calls function correctly. If they fail, the network configura-
tion databases can be corrupt. Since RPC services cannot function correctly in this situation, rpcbind reports the condition and termi-
nates.
rpcbind maintains an open transport end for each transport that it uses for indirect calls. This is the UDP port on most systems.
rpcbind can only be started by the superuser.
The FMRI svc:network/rpc/bind property group config contains the following property settings:
enable_tcpwrappers
Specifies that the TCP wrappers facility is used to control access to TCP services. The value true enables checking. The default value
for enable_tcpwrappers is false. If the enable_tcpwrappers parameter is enabled, then all calls to rpcbind originating from non-local
addresses are automatically wrapped by the TCP wrappers facility. The syslog facility code daemon is used to log allowed connections
(using the info severity level) and denied traffic (using the warning severity level). See syslog.conf(4) for a description of syslog
codes and severity levels. The stability level of the TCP wrappers facility and its configuration files is External. As the TCP wrap-
pers facility is not controlled by Sun, intrarelease incompatibilities are not uncommon. See attributes(5).
verbose_logging
Specifies whether the TCP wrappers facility logs all calls orjust the denied calls. The default is false. This option has no effect if
TCP wrappers are not enabled.
allow_indirect
Specifies whether rpcbind allows indirect calls at all. By default, rpcbind allows most indirect calls, except to a number of standard
services(keyserv, automount, mount, nfs, rquota, and selected NIS and rpcbind procedures). Setting allow_indirect to false causes all
indirect calls to be dropped. The default is true. NIS broadcast clients rely on this functionality on NIS servers.
OPTIONS
The following options are supported:
-d Run in debug mode. In this mode, rpcbind does not fork when it starts. It prints additional information during operation, and
aborts on certain errors. With this option, the name-to-address translation consistency checks are shown in detail.
-w Do a warm start. If rpcbind aborts or terminates on SIGINT or SIGTERM, it writes the current list of registered services to
/var/run/portmap.file and /var/run/rpcbind.file. Starting rpcbind with the -w option instructs it to look for these files and
start operation with the registrations found in them. This allows rpcbind to resume operation without requiring all RPC services
to be restarted.
FILES
/var/run/portmap.file Stores the information for RPC services registered over IP based transports for warm start purposes.
/var/run/rpcbind.file Stores the information for all registered RPC services for warm start purposes.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
|Interface Stability |See below. |
+-----------------------------+-----------------------------+
TCP wrappers is External.
SEE ALSO
smf(5), rpcinfo(1M), svcadm(1M), svccfg(1M), rpcbind(3NSL), syslog.conf(4), attributes(5), smf(5)
For information on the TCP wrappers facility, see the hosts_access(4) man page, delivered as part of the Solaris operating environment in
/usr/sfw/man and available in the SUNWtcpd package.
NOTES
Terminating rpcbind with SIGKILL prevents the warm-start files from being written.
All RPC servers are restarted if the following occurs: rpcbind crashes (or is killed with SIGKILL) and is unable to to write the warm-start
files; rpcbind is started without the -w option after a graceful termination. Or, the warm start files are not found by rpcbind.
The rpcbind service is managed by the service management facility, smf(5), under the service identifier
svc:/network/rpc/bind
Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M).
The configuration properties of this service can be modified with svccfg(1M).
SunOS 5.10 29 Oct 2004 rpcbind(1M)