11-27-2008
post the output from
svcs -l /network/rpc/bind
9 More Discussions You Might Find Interesting
1. Solaris
Hi all,
I am using Solaris 10 OS on X86 platform. Long back i tried to configure DHCP server on my system but because of rpc-bind, total went in vein.Even now i am unable to access even USB also. When i tried to look for "volfs" service it was offline because one of its dependant... (0 Replies)
Discussion started by: vvpotugunta
0 Replies
2. Solaris
I would like to disable RPC bind permanently since I am not going to use rpc bind to network to any other machines. How do I do this so I can stop getting all these error messages? (3 Replies)
Discussion started by: jastanle84
3 Replies
3. Solaris
while i trying to mount from NAS i have this messages
mount -F nfs -o rw 172.16.110.13:/tremabkup /tremabkup
nfs mount: 172.16.110.13: : RPC: Rpcbind failure - RPC: Timed out
nfs mount: retrying: /tremabkup
nfs mount: 172.16.110.13: : RPC: Rpcbind failure - RPC: Timed out
nfs mount:... (2 Replies)
Discussion started by: thecobra151
2 Replies
4. Solaris
C: Rpcbind failure - RPC: Timed out error (solaris)
hello an nfs server on my sun fire v440 is not responding , i get the error bellow and lots of my networking services are not reponding, please helppppp its an emergency
RPC: Rpcbind failure - RPC: Timed out
i also get
NFS server... (2 Replies)
Discussion started by: feg
2 Replies
5. Solaris
My code
Hi Folks,
I am getting maintanance error for rpc/bind in one of solaris 10 server.I have tried disable,enabled,cleared all options and dont no how to make online.Please help me
Please find the below for details :-
Server1> svcs -a rpc/bind
svcs: -a ignored when used with... (0 Replies)
Discussion started by: susindram
0 Replies
6. Red Hat
Hi All,
Distros of machines : RHEL6
Bind Vesrion : Bind-9.7-3.2
I am trying to set up a test DNS for my home network. I have two rhel 6 machines A and B. Machine A has 2 NICs and is acting as a router also, one NIC is facing intranet and the otehr is facing intranet. On machine A i have... (0 Replies)
Discussion started by: Rohit Bhanot
0 Replies
7. Solaris
Fails to mount the server (10.125.224.22) during installation of a software on client, throwing the below error:
nfs mount: 10.125.224.22: : RPC: Rpcbind failure - RPC: Timed out
nfs mount: retrying: /cdrom
This happened after complete shutdown of the lab. The server came up fine but most... (1 Reply)
Discussion started by: frintocf
1 Replies
8. Red Hat
Hello friends
Internet query not working anymore with bind , i am not using forwarder dns server .
1.
resolv.conf file =>
search local.server
nameserver 127.0.0.1
2.
named.conf file =>
//
// named.conf
//
// Provided by Red Hat bind package to configure the ISC BIND named(8) DNS... (8 Replies)
Discussion started by: rink
8 Replies
9. Solaris
Hi,
I have an issue with RPC bind service and its failing with status 1. any help would be much appreciated.
THanks (2 Replies)
Discussion started by: Yakub Humami
2 Replies
LEARN ABOUT FREEBSD
lockd
RPC.LOCKD(8) BSD System Manager's Manual RPC.LOCKD(8)
NAME
rpc.lockd -- NFS file locking daemon
SYNOPSIS
rpc.lockd [-d debug_level] [-g grace period] [-h bindip] [-p port]
DESCRIPTION
The rpc.lockd utility provides monitored and unmonitored file and record locking services in an NFS environment. To monitor the status of
hosts requesting locks, the locking daemon typically operates in conjunction with rpc.statd(8).
Options and operands available for rpc.lockd:
-d The -d option causes debugging information to be written to syslog, recording all RPC transactions to the daemon. These messages are
logged with level LOG_DEBUG and facility LOG_DAEMON. Specifying a debug_level of 1 results in the generation of one log line per
protocol operation. Higher debug levels can be specified, causing display of operation arguments and internal operations of the dae-
mon.
-g The -g option allow to specify the grace period, in seconds. During the grace period rpc.lockd only accepts requests from hosts
which are reinitialising locks which existed before the server restart. Default is 30 seconds.
-h bindip
Specify specific IP addresses to bind to. This option may be specified multiple times. If no -h option is specified, rpc.lockd will
bind to INADDR_ANY. Note that when specifying IP addresses with -h, rpc.lockd will automatically add 127.0.0.1 and if IPv6 is
enabled, ::1 to the list.
-p The -p option allow to force the daemon to bind to the specified port, for both AF_INET and AF_INET6 address families.
Error conditions are logged to syslog, irrespective of the debug level, using log level LOG_ERR and facility LOG_DAEMON.
The rpc.lockd utility must NOT be invoked by inetd(8) because the protocol assumes that the daemon will run from system start time. Instead,
it should be configured in rc.conf(5) to run at system startup.
FILES
/usr/include/rpcsvc/nlm_prot.x RPC protocol specification for the network lock manager protocol.
SEE ALSO
syslog(3), rc.conf(5), rpc.statd(8)
STANDARDS
The implementation is based on the specification in "Protocols for X/Open PC Interworking: XNFS, Issue 4", X/Open CAE Specification C218,
ISBN 1 872630 66 9.
HISTORY
A version of rpc.lockd appeared in SunOS 4.
BUGS
The current implementation serialises locks requests that could be shared.
BSD
November 2, 2007 BSD