Sponsored Content
Full Discussion: Issue in reboot
Operating Systems HP-UX Issue in reboot Post 302378949 by mystition on Wednesday 9th of December 2009 07:13:51 AM
Old 12-09-2009
Issue in reboot

Hi,

Whenever I reboot this server remotely by using the command 'shutdown -r now' or 'reboot'. The server does not return to normal multi-user mode. It boots in single user mode.
To bring back the server, someone is required to connect via console and fire 'init 3'.

Please suggest on what can be the reason behind this and the solution?

OS: TRU UNIX 5.1B
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

reboot

Hi all, Quick question. Does anyone know what is the compination of buttons that I have to press to stop the start up so I can bring the system in a single user mode? I use HP Vis 9000 Thanks alot (1 Reply)
Discussion started by: guest100
1 Replies

2. UNIX for Dummies Questions & Answers

Finding last Reboot

All, Does anybody know of a Unix command or file name where I can find out when the Unix box was last rebooted? We're using HP-UX 10.2. Thanks, PP (3 Replies)
Discussion started by: Positive Parrot
3 Replies

3. Solaris

different between soft reboot and hard reboot

Hi Guru's Can any want here could explain to me the different between soft reboot and hard reboot . Best Regards Seelan (3 Replies)
Discussion started by: seelan3
3 Replies

4. Shell Programming and Scripting

best way to reboot ?

Hi What is the best way to reboot a Linux computer? i) Press the power switch ii) type 'init 6' as any user, then enter the root password when prompted iii) Pour metal filings in the top of the computer. iv) su to root then type 'init 6' (6 Replies)
Discussion started by: tjay83
6 Replies

5. SCO

SCO Reboot Issue

Hi, We are using SCO UNIX 7.1.3 and the server recently started rebooting by itself. Do anyone know how can i create a dump or crash dump while the server rebooots? Your quick help on this is really appreciated. Regards, Ravikumar R (1 Reply)
Discussion started by: rrb2009
1 Replies

6. Solaris

Controller Issue on X4600 after reboot

One of my X4600 server had a power loss and rebooted and now its giving me a strange problem servers internal disk controller naming has changed by itself ... the after failsafe boot md.conf file shows following c3txdx but shows internal disk at c4txdx ... what could be the reason for this and... (1 Reply)
Discussion started by: fugitive
1 Replies

7. Solaris

vnc issue after reboot

Hi , Everytime after reboot when user tries to start vnc below error is thrown $ vncserver :5 Couldn't start Xvnc; trying default font path. Please set correct fontPath in the vncserver script. Couldn't start Xvnc process. _XSERVTransSocketCreateListener: failed to bind listener... (7 Replies)
Discussion started by: chidori
7 Replies

8. Shell Programming and Scripting

Reboot script issue

Hi guys I am troubleshooting a script that informs me when a system has rebooted. The script is placed in /etc/rc3.d folder under root. The script is as follows: . /opt/scripts/function.sh PATH=/usr/bin EMAIL_ADD=<email address> ... (2 Replies)
Discussion started by: Junaid Subhani
2 Replies

9. IP Networking

Node switched itself from static to DHCP on reboot issue

I'm trying to figure out what circumstances would cause an Open Solaris 11.2 host to switch itself from a static to a DHCP ip address upon reboot. This has only happened once but is a cause for some concern as this machine will be part of a web server pool. Nothing has changed on the LAN that... (2 Replies)
Discussion started by: SmokeyJoe
2 Replies

10. Linux

Issue in Bonding during Reboot(Linux)

Respected Members, We encountered an issue during node reboot when eth1 and eth5 of bond1 were behaving unusual(both eth1 and eth5 were in unknown states and ifdown and ifup were used to rectify). Please find the messages and configuration files as below and please let me know for any other... (0 Replies)
Discussion started by: Mudit Bansal
0 Replies
SHUTDOWN(8)						    BSD System Manager's Manual 					       SHUTDOWN(8)

NAME
shutdown, poweroff -- close down the system at a given time SYNOPSIS
shutdown [-] [-h | -p | -r | -k] [-o [-n]] time [warning-message ...] poweroff DESCRIPTION
The shutdown utility provides an automated shutdown procedure for super-users to nicely notify users when the system is shutting down, saving them from system administrators, hackers, and gurus, who would otherwise not bother with such niceties. The following options are available: -h The system is halted at the specified time. -p The system is halted and the power is turned off (hardware support required) at the specified time. -r The system is rebooted at the specified time. -k Kick everybody off. The -k option does not actually halt the system, but leaves the system multi-user with logins disabled (for all but super-user). -o If one of the -h, -p or -r options are specified, shutdown will execute halt(8) or reboot(8) instead of sending a signal to init(8). -n If the -o option is specified, prevent the file system cache from being flushed by passing -n to halt(8) or reboot(8). This option should probably not be used. time Time is the time at which shutdown will bring the system down and may be the case-insensitive word now (indicating an immediate shut- down) or a future time in one of two formats: +number, or yymmddhhmm, where the year, month, and day may be defaulted to the current system values. The first form brings the system down in number minutes and the second at the absolute time specified. +number may be specified in units other than minutes by appending the corresponding suffix: ``s'', ``sec'', ``m'', ``min''. ``h'', ``hour''. warning-message Any other arguments comprise the warning message that is broadcast to users currently logged into the system. - If '-' is supplied as an option, the warning message is read from the standard input. At intervals, becoming more frequent as apocalypse approaches and starting at ten hours before shutdown, warning messages are displayed on the terminals of all users logged in. Five minutes before shutdown, or immediately if shutdown is in less than 5 minutes, logins are dis- abled by creating /var/run/nologin and copying the warning message there. If this file exists when a user attempts to log in, login(1) prints its contents and exits. The file is removed just before shutdown exits. At shutdown time a message is written to the system log, containing the time of shutdown, the person who initiated the shutdown and the rea- son. The corresponding signal is then sent to init(8) to respectively halt, reboot or bring the system down to single-user state (depending on the above options). The time of the shutdown and the warning message are placed in /var/run/nologin and should be used to inform the users about when the system will be back up and why it is going down (or anything else). A scheduled shutdown can be canceled by killing the shutdown process (a SIGTERM should suffice). The /var/run/nologin file that shutdown created will be removed automatically. When run without options, the shutdown utility will place the system into single user mode at the time specified. Calling ``poweroff'' is equivalent to running: shutdown -p now FILES
/var/run/nologin tells login(1) not to let anyone log in EXAMPLES
Reboot the system in 30 minutes and display a warning message on the terminals of all users currently logged in: # shutdown -r +30 "System will reboot" COMPATIBILITY
The hours and minutes in the second time format may be separated by a colon (``:'') for backward compatibility. SEE ALSO
kill(1), login(1), wall(1), nologin(5), halt(8), init(8), reboot(8) HISTORY
The shutdown utility appeared in 4.0BSD. BSD
December 15, 2014 BSD
All times are GMT -4. The time now is 01:01 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy