08-13-2013
RPC bind service in maintenance mode
Hi,
I have an issue with RPC bind service and its failing with status 1. any help would be much appreciated.
THanks
10 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
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
3. 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
4. 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
5. Solaris
Hi Guys,
Virtual Machine - Solaris 10 ssh service is in maintenance mode, when i tried to disable it it got disabled but when i enabling it ( svcadm enable ssh) it is coming in maintenance mode......
Pls help (10 Replies)
Discussion started by: saurabh84g
10 Replies
6. 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
7. 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
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. Solaris
Hi experts,
This is a production server.
Host information's are below
SunOS hostname_srv 5.10 Generic_150400-09 sun4v sparc sun4v
Now issue with ntp service, This host have zone in it with 9 hosts, Every hosts have ntp service issue. While i check for the service status it's in... (3 Replies)
Discussion started by: babinlonston
3 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
LEARN ABOUT FREEBSD
rpc.statd
RPC.STATD(8) BSD System Manager's Manual RPC.STATD(8)
NAME
rpc.statd -- host status monitoring daemon
SYNOPSIS
rpc.statd [-d] [-h bindip] [-p port]
DESCRIPTION
The rpc.statd utility is a daemon which co-operates with rpc.statd daemons on other hosts to provide a status monitoring service. The daemon
accepts requests from programs running on the local host (typically, rpc.lockd(8), the NFS file locking daemon) to monitor the status of
specified hosts. If a monitored host crashes and restarts, the remote daemon will notify the local daemon, which in turn will notify the
local program(s) which requested the monitoring service. Conversely, if this host crashes and re-starts, when the rpc.statd re-starts, it
will notify all of the hosts which were being monitored at the time of the crash.
The following option is available:
-d Cause 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. Error conditions are logged irrespective of this option, using level LOG_ERR.
-h bindip
Specify specific IP addresses to bind to. This option may be specified multiple times. If no -h option is specified, rpc.statd will
bind to INADDR_ANY. Note that when specifying IP addresses with -h, rpc.statd 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.
The rpc.statd 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 run from rc(8) after the network has been started.
FILES
/var/db/statd.status non-volatile record of currently monitored hosts.
/usr/include/rpcsvc/sm_inter.x RPC protocol specification used by local applications to register monitoring requests.
SEE ALSO
syslog(3), rc(8), rpc.lockd(8)
STANDARDS
The implementation is based on the specification in X/Open CAE Specification C218, "Protocols for X/Open PC Interworking: XNFS, Issue 4",
ISBN 1 872630 66 9
BUGS
There is no means for the daemon to tell when a monitored host has disappeared permanently (e.g. catastrophic hardware failure), as opposed
to transient failure of the host or an intermediate router. At present, it will re-try notification attempts at frequent intervals for 10
minutes, then hourly, and finally gives up after 24 hours.
The protocol requires that symmetric monitor requests are made to both the local and remote daemon in order to establish a monitored rela-
tionship. This is convenient for the NFS locking protocol, but probably reduces the usefulness of the monitoring system for other applica-
tions.
The current implementation uses more than 1Kbyte per monitored host in the status file (and also in VM). This may be inefficient for NFS
servers with large numbers of clients.
BSD
November 1, 2007 BSD