06-01-2012
Okay, so why don't you post the rpc-bind log file last lines ?
10 More Discussions You Might Find Interesting
1. Solaris
I had a power failure the other day and when my relatively new Solaris 10 machine rebooted it is thrown into maintenance mode.
I've found the following lines in the /var/adm/messages file, I'm assuming this is the root cause of the problem. However, I don't have the slightest idea on how to... (9 Replies)
Discussion started by: cheetobandito
9 Replies
2. HP-UX
I think that if the directory /tcb exists, HP-UX is in trusted mode and the passwd data is somewhere in /tcb/files/auth. But that's all I remember.
Also I think recent versions of HP-UX can have a /etc/shadow file. (0 Replies)
Discussion started by: Perderabo
0 Replies
3. AIX
Hi,
I installed AIX 5.2 on a P5 9110-51A (powerpc).
The installation was successful, however, after each reboot it goes to service mode.
If I enter SMS menu, select boot device and select "normal mode" everything is ok, the system boots. But if I issue a reboot, it goes back to diagnostics... (6 Replies)
Discussion started by: gsorin
6 Replies
4. Solaris
Hello All,
On solaris 10 server i could see the FTP service is in maintenance mode always :mad:
Could some assist?
svcs -xv
svc:/network/nfs/nlockmgr:default (NFS lock manager)
State: maintenance since Tue 28 Jul 2009 11:47:55 AM BST
Reason: Restarting too quickly.
See: Sun... (5 Replies)
Discussion started by: bullz26
5 Replies
5. Solaris
Hi,
I have installed Hudson on a Solaris 11 server, using the installation instructions available at Paul Oswald: Hudson Solaris SMF Manifest.
When I perform svcs -l hudson, I get:
fmri svc:/application/hudson:default
name Hudson Continuous Build Server
enabled true... (4 Replies)
Discussion started by: JVerstry
4 Replies
6. Solaris
I have a Solaris 10 SunFire v880 machine and I'm having trouble with Samba.
Samba has worked on this machine but since the machine has been re-booted Samba has not worked.
Machine details are:
cat /etc/release
Solaris 10 10/08 s10s_u6wos_07b SPARC
Copyright 2008... (2 Replies)
Discussion started by: KenLynch
2 Replies
7. Solaris
Hi Guys,
I have a sunblade 1500. I booted the system and it booted to maintenance mode. How can I fix this?
Thanks lots (8 Replies)
Discussion started by: cjashu
8 Replies
8. Solaris
:confused:
when i tried to look the status of DNS-client, it is in maintenance mode.....
Please tell me how to bring it back to online mode...PLEASE TELL ME STEP BY STEP.... PLEASE...
:wall: (2 Replies)
Discussion started by: vamshigvk475
2 Replies
9. AIX
Hi this may be a easy question to answer but thanks in advance.
So I was able to download the VIOS media from IBM and currently I am burning it to a cd/dvd right now.
The steps I've collected so far are from the net. can you please confirm and add on to the steps if there are any steps... (0 Replies)
Discussion started by: Adnans2k
0 Replies
10. Solaris
i booted into maintenance mode
boot -- -s
from the console
I got the
Root password for system maintenance (control-d to bypass)
I did control -d
and then logged in
it told me that I was booting into boot -s
but after I did a control -d and logged in
who -r shows
... (9 Replies)
Discussion started by: goya
9 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)