10 More Discussions You Might Find Interesting
1. 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
2. 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
3. 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
4. IP Networking
Hi Folks,
I am facing a problem using RPC based connection between two different OS ( RHEL 5 and Windows XP).
We have a Camelot ( Cad Navigation Equipment - Running is RHEL5) which is connected to an FEI equipment ( Running in Windows XP).The connection uses an RPC based Driver for... (0 Replies)
Discussion started by: asheshrocky
0 Replies
5. Solaris
Hi Folks,
I am facing a problem using RPC based connection between two different OS ( RHEL 5 and Windows XP).
We have a Camelot ( Cad Navigation Equipment - Running is RHEL5) which is connected to an FEI equipment ( Running in Windows XP).The connection uses an RPC based Driver for... (0 Replies)
Discussion started by: asheshrocky
0 Replies
6. Solaris
Hi all,
I have some sort of problem with BIND DNS server my environment as follows.
bash-3.00# cat /etc/release
Solaris 10 6/06 s10s_u2wos_09a SPARC
Copyright 2006 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to... (3 Replies)
Discussion started by: h@foorsa.biz
3 Replies
7. 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
8. 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
9. Shell Programming and Scripting
Hi,
I have an array of strings. Each string has 4 comma separated values. I am binding this array to a SQL where I am required to do an INSERT after grouping.
The binding is done as :
$insertADWSth->bind_param_array(1,A_CONSTANT_STRING);... (1 Reply)
Discussion started by: sinpeak
1 Replies
10. Solaris
Hi all,
Was hoping someone could shed some light on my problem,
rpc bind is in maintenance mode on Solaris 10 and won't fire up.
contents of the error log are:
rpcbind failed with 1.
bash-3.00#
Because rpc-bind isn't working, it's stopping nfs and autofs from working too
... (6 Replies)
Discussion started by: callmebob
6 Replies
rpc.lockd(8) System Manager's Manual rpc.lockd(8)
NAME
rpc.lockd, lockd - Network lock daemon
SYNOPSIS
/usr/sbin/rpc.lockd [-b hostname] [-c] [-d debug] [-g graceperiod] [-h hashsize] [-s] [-t timeout]
OPTIONS
The default behavior will create and bind a socket for each protocol per interface on the system. When the -b switch is specified, one
socket per protocol will be created and bind to the passed IP address. Available only on TruCluster Server systems. This option starts the
clusterwide lock daemon, which helps provide highly available NFS service. Do not use -c directly. Highly available NFS service is config-
ured by default and typically does not require intervention. If you do need to start the clusterwide lock daemon, use the CAA command,
caa_start cluster_lockd.
For more information, see the TruCluster Server Administration manual. Internal Use Only. Use this option only under the direction
of technical support personnel. Causes the rpc.lockd daemon to use the variable graceperiod (in seconds) as the grace period dura-
tion instead of the default value of 15 seconds. Internal Use Only. Causes the rpc.lockd daemon to use the variable timeout (in
seconds) as the interval instead of the default value of 5 seconds to retransmit a lock request to the remote server.
DESCRIPTION
The rpc.lockd daemon processes lock requests that are either sent locally by the kernel or remotely by another lock daemon. The NFS locking
service makes this advisory locking support possible by using the fcntl system call and the lockf subroutine. The rpc.lockd daemon forwards
lock requests for remote data to the server site's lock daemon. The rpc.lockd daemon then requests the status monitor daemon, rpc.statd,
for monitor service. The reply to the lock request is not sent to the kernel until the status daemon and the server site's lock daemon have
replied.
If either the status monitor or server site's lock daemon is unavailable, the reply to a lock request for remote data is delayed until all
daemons become available.
When a server recovers, it waits for a grace period for all client site lock daemons to submit reclaim requests. Client site lock daemons
are notified by rpc.statd of the server recovery and promptly resubmit previously granted lock requests. If a client site's lock daemon
fails to secure previously granted locks at the server site, it sends the signal SIGLOST to all the processes that were previously holding
locks and cannot reclaim them.
SEE ALSO
Commands: rpc.statd(8)
Functions: fcntl(2), signal(2), lockf(3)
rpc.lockd(8)