Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Help unable to shutdown- RPC problems Post 29165 by MBGPS on Tuesday 1st of October 2002 08:36:18 AM
Old 10-01-2002
Ok solved the rpc problem but still the box still doesnt seem to be shutting down:

# shutdown -y -i6 -g0

Shutdown started. Tue Oct 1 13:34:51 BST 2002

Changing to init state 6 - please wait
#


Any ideas?
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Help unable to shutdown- RPC problems

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

Unable to shutdown and start machine

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

unable to shutdown solaris 10

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

Script to force Oracle database shutdown when shutdown immediate does not work

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)

Problems using shutdown -u command

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

RPC: Rpcbind failure - RPC: Timed out

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

Error : "RPC: Rpcbind failure - RPC: Timed out"

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

RPC: Rpcbind failure - RPC: Timed out error (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

nfs mount: RPC: Rpcbind failure - RPC: Timed out

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

Linux SuSE SLES 8 error..unable to issue shutdown command

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
SHUTDOWN(8)						Linux System Administrator's Manual					       SHUTDOWN(8)

NAME
shutdown - bring the system down SYNOPSIS
/sbin/shutdown [-t sec] [-arkhncfF] time [warning-message] DESCRIPTION
shutdown brings the system down in a secure way. All logged-in users are notified that the system is going down, and login(1) is blocked. It is possible to shut the system down immediately or after a specified delay. All processes are first notified that the system is going down by the signal SIGTERM. This gives programs like vi(1) the time to save the file being edited, mail and news processing programs a chance to exit cleanly, etc. shutdown does its job by signalling the init process, asking it to change the runlevel. Runlevel 0 is used to halt the system, runlevel 6 is used to reboot the system, and runlevel 1 is used to put to system into a state where administrative tasks can be performed; this is the default if neither the -h or -r flag is given to shutdown. To see which actions are taken on halt or reboot see the appropriate entries for these runlevels in the file /etc/inittab. OPTIONS
-a Use /etc/shutdown.allow. -t sec Tell init(8) to wait sec seconds between sending processes the warning and the kill signal, before changing to another runlevel. -k Don't really shutdown; only send the warning messages to everybody. -r Reboot after shutdown. -h Halt after shutdown. -n [DEPRECATED] Don't call init(8) to do the shutdown but do it ourself. The use of this option is discouraged, and its results are not always what you'd expect. -f Skip fsck on reboot. -F Force fsck on reboot. -c Cancel an already running shutdown. With this option it is of course not possible to give the time argument, but you can enter a explanatory message on the command line that will be sent to all users. time When to shutdown. warning-message Message to send to all users. The time argument can have different formats. First, it can be an absolute time in the format hh:mm, in which hh is the hour (1 or 2 dig- its) and mm is the minute of the hour (in two digits). Second, it can be in the format +m, in which m is the number of minutes to wait. The word now is an alias for +0. If shutdown is called with a delay, it creates the advisory file /etc/nologin which causes programs such as login(1) to not allow new user logins. Shutdown removes this file if it is stopped before it can signal init (i.e. it is cancelled or something goes wrong). It also removes it before calling init to change the runlevel. The -f flag means `reboot fast'. This only creates an advisory file /fastboot which can be tested by the system when it comes up again. The boot rc file can test if this file is present, and decide not to run fsck(1) since the system has been shut down in the proper way. After that, the boot process should remove /fastboot. The -F flag means `force fsck'. This only creates an advisory file /forcefsck which can be tested by the system when it comes up again. The boot rc file can test if this file is present, and decide to run fsck(1) with a special `force' flag so that even properly unmounted filesystems get checked. After that, the boot process should remove /forcefsck. The -n flag causes shutdown not to call init, but to kill all running processes itself. shutdown will then turn off quota, accounting, and swapping and unmount all filesystems. ACCESS CONTROL
shutdown can be called from init(8) when the magic keys CTRL-ALT-DEL are pressed, by creating an appropriate entry in /etc/inittab. This means that everyone who has physical access to the console keyboard can shut the system down. To prevent this, shutdown can check to see if an authorized user is logged in on one of the virtual consoles. If shutdown is called with the -a argument (add this to the invocation of shutdown in /etc/inittab), it checks to see if the file /etc/shutdown.allow is present. It then compares the login names in that file with the list of people that are logged in on a virtual console (from /var/run/utmp). Only if one of those authorized users or root is logged in, it will proceed. Otherwise it will write the message shutdown: no authorized users logged in to the (physical) system console. The format of /etc/shutdown.allow is one user name per line. Empty lines and comment lines (prefixed by a #) are allowed. Currently there is a limit of 32 users in this file. Note that if /etc/shutdown.allow is not present, the -a argument is ignored. FILES
/fastboot /etc/inittab /etc/init.d/halt /etc/init.d/reboot /etc/shutdown.allow NOTES
A lot of users forget to give the time argument and are then puzzled by the error message shutdown produces. The time argument is manda- tory; in 90 percent of all cases this argument will be the word now. Init can only capture CTRL-ALT-DEL and start shutdown in console mode. If the system is running the X window System, the X server pro- cesses all key strokes. Some X11 environments make it possible to capture CTRL-ALT-DEL, but what exactly is done with that event depends on that environment. Shutdown wasn't designed to be run setuid. /etc/shutdown.allow is not used to find out who is executing shutdown, it ONLY checks who is currently logged in on (one of the) console(s). AUTHOR
Miquel van Smoorenburg, miquels@cistron.nl SEE ALSO
fsck(8), init(8), halt(8), poweroff(8), reboot(8) Juli 31, 2001 SHUTDOWN(8)
All times are GMT -4. The time now is 05:17 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy