10-01-2002
If your host is not an nfs server, this message is not a big deal and you can ignore it.
If your host is an nfs server, this message means that something is wrong with mountd. As a result of this, your shutdown message will not be broadcast to any other systems which have remote mounted and of your local filesystems. That still is not a big deal in itself, but you need to investgate why your mountd has failed. Prior to the shutdown you were running an nfs server without a functioning mountd. That means that if the nfs clients had rebooted they could not remount the filesystems.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Help unable to shutdown- RPC problems
I seem to have consistent problems shuting down whichever init state I use
basically I get the following errors messages followed by a return to the prompt
# shutdown -i6 -g0 -y
Shutdown started. Tue Oct 1 09:47:03 BST 2002
Broadcast Message from... (1 Reply)
Discussion started by: vviscomi
1 Replies
2. Solaris
Hello.
I have just installed solaris on my PC (standalone). It allows to reboot. But IF I shut down and the restart by pressing the button - It does not show my solaris OS and I am then forced to perform fresh installation.
Could you please let me know the fix for it - So that shutdown and... (3 Replies)
Discussion started by: panchpan
3 Replies
3. Infrastructure Monitoring
hi folks, i have a snag, when i attempt shutdown of solaris 10 on a sunfire v240 it seems to pause for ages, and goes no further, im busy learning my way around the system so please be patient.
/etc(R)-bash-3.00$ init 6
/etc(R)-bash-3.00$ svc.startd: The system is coming down. Please wait.... (7 Replies)
Discussion started by: alienkidmj12
7 Replies
4. UNIX for Dummies Questions & Answers
I have Oracle 9i R2 on AIX 5.2. My Database is running in shared server mode (MTS).
Sometimes when I shutdown the database it shutsdown cleanly in 4-5 mints and sometimes it takes good 15-20 minutes and then I get some ora-600 errors and only way to shutdown is by opening another session and... (7 Replies)
Discussion started by: aixhp
7 Replies
5. OS X (Apple)
I have a smart-ups connected to my OS X Snow Leopard server ver. 10.6. Based on the docs and forums I read, I have been trying to use the software provided by APC, PCNS. I have also tried to just use the UPS communications cable provided and use the OS' "UPS options". Neither of them work exactly... (1 Reply)
Discussion started by: mckorn99
1 Replies
6. 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
7. Solaris
Hello I am having an issue with a server SUN FIRE T2000 (Solaris 10).
First of all the server didn't boot normaly so I did a full restoration of the file systems.
Now the server boot, most of the services are available (not all the services), but I keep on seeing
RPC: Rpcbind failure -... (4 Replies)
Discussion started by: feg
4 Replies
8. 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
9. 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
10. UNIX for Beginners Questions & Answers
the only way we can power off is if we actually press power button on server. Running on HP DL-G4. from root, when we issue command it just returns to root prompt. (1 Reply)
Discussion started by: amexboy
1 Replies
LEARN ABOUT ULTRIX
rpc_allow_remote_shutdown
rpc_allow_remote_shutdown(3ncs) rpc_allow_remote_shutdown(3ncs)
Name
rpc_allow_remote_shutdown - allow or disallow remote shutdown of a server (server only)
Syntax
#include <idl/c/rpc.h>
void rpc_$allow_remote_shutdown(allow, checkproc, status)
unsigned long allow;
rpc_$shut_check_fn_t checkproc;
status_$t *status;
Arguments
allow A value indicating `false' if zero, `true' otherwise.
checkproc A pointer to a Boolean function.
status The completion status. If the completion status returned in is equal to status_$ok , then the routine that supplied it
was successful.
Description
The routine allows or disallows remote callers to shut down a server using
By default, servers do not allow remote shutdown via If a server calls with allow true (not zero) and checkproc nil, then remote shutdown
will be allowed. If allow is true and checkproc is not nil, then when a remote shutdown request arrives, the function denoted by checkproc
is called and the shutdown is allowed if the function returns true. If allow is false (zero), remote shutdown is disallowed.
Diagnostics
This section lists status codes for errors returned by this routine in
rpc_$not_in_call An internal error.
rpc_$you_crashed This error can occur if a server has crashed and restarted. A client RPC runtime library sends the error to the server
if the client makes a remote procedure call before the server crashes, then receives a response after the server
restarts.
rpc_$proto_error An internal protocol error.
Files
See Also
intro(3ncs), rpc_shutdown(3ncs), rrpc_shutdown(3ncs)
rpc_allow_remote_shutdown(3ncs)