Sponsored Content
Operating Systems HP-UX Machine dumps crash on each reboot. Post 302950950 by Don Cragun on Thursday 30th of July 2015 10:55:51 AM
Old 07-30-2015
Is the machine failing to come up to multi-user mode because you don't have enough free space on /?
This User Gave Thanks to Don Cragun For This Post:
 

9 More Discussions You Might Find Interesting

1. Solaris

crash of my machine

I installed solaris 5.9 on a machine SunBlade100 512Mo of RAM and 18Go of hard disc, after the installation I have remark that the machine starts again after 10mn with 15 mn of walk, I downloaded and installed the last patchs on the machine but the poblème persists. someone can help me and tell me... (0 Replies)
Discussion started by: toufik
0 Replies

2. 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

3. HP-UX

HP UX Dumps

Hi Every one Pls Provide me the letest dumps of HP UX if any one can Thanks And Regards (0 Replies)
Discussion started by: hasnainshah
0 Replies

4. UNIX for Advanced & Expert Users

Where to set the right "Apache" to run after reboot on a RedHat 5 machine ?!

Hi, I'am working on a RedHat server (V5) and having on it 2 Apache instances, but after each reboot i have the wrong one starting so that i have to stop it doing "httpd -k stop" and than launch the right one doing "/etc/init.d/httpd -k start". For more Details, you may see the link i inserted... (4 Replies)
Discussion started by: mehdi1973
4 Replies

5. Red Hat

Filesystems disappear on KVM guest machine after reboot.

Hello, I have a KVM system running on RHEL 5.4. It hosts 4 guest VMs. One of the guest host fails to get back the mounted filesystems after the system reboots. Does anyone have any idea what the issue could be? Regards, Mahive. (1 Reply)
Discussion started by: mahive
1 Replies

6. Solaris

crash dumps

I am supporting a server running Solaris 4.3.The server is not having ddicated system administrator and i am requred to do minor maintenance tasks.l From few days, The server is automatically crashing and i just reboot the server. I also do not see anything in /var/adm/messages that can give an... (1 Reply)
Discussion started by: asalman.qazi
1 Replies

7. AIX

Post mortem for critical Production AIX System Reboot/Crash

Hello All, Critical AIX production box crashed/rebooted while our team is working on it and we need to generate a detailed report for that, below are few questions that need to be included in the report. (We are System Administration team and everyone in our team has root access via sudo as well... (3 Replies)
Discussion started by: lovesaikrishna
3 Replies

8. Solaris

Mounting done only after reboot the machine in Solaris 9

Hi Team I am facing an issue on solaris machine as mounting a remote path is only done after reboot the machine. without rebooting its going to hanging state and no process either. i am using the following parameters for mounting NFS share.. mount -F nfs remote_path:/abc/ mount_point... (1 Reply)
Discussion started by: boby.kumar
1 Replies

9. Red Hat

Disable xen machine to auto start on reboot

Hello Guys - I need to disable xen server not to start when the server is rebooted. 1) What is the parameter to be used to do this..below is the entry in my config file... on_reboot = "restart" 2) What is the default behaviors of the xen on reboot ? in case we comment this line from config... (0 Replies)
Discussion started by: saurabh84g
0 Replies
shutdown(1M)						  System Administration Commands					      shutdown(1M)

NAME
shutdown - shut down system, change system state SYNOPSIS
/usr/sbin/shutdown [-y] [-g grace-period] [-i init-state] [message] DESCRIPTION
shutdown is executed by the super user to change the state of the machine. In most cases, it is used to change from the multi-user state (state 2) to another state. By default, shutdown brings the system to a state where only the console has access to the operating system. This state is called single- user. Before starting to shut down daemons and killing processes, shutdown sends a warning message and, by default, a final message asking for confirmation. message is a string that is sent out following the standard warning message "The system will be shut down in ..." If the string contains more than one word, it should be contained within single (') or double (") quotation marks. The warning message and the user provided message are output when there are 7200, 3600, 1800, 1200, 600, 300, 120, 60, and 30 seconds remaining before shutdown begins. See EXAMPLES. System state definitions are: state 0 Stop the operating system. state 1 State 1 is referred to as the administrative state. In state 1 file systems required for multi-user operations are mounted, and logins requiring access to multi-user file systems can be used. When the system comes up from firmware mode into state 1, only the console is active and other multi-user (state 2) services are unavailable. Note that not all user processes are stopped when transitioning from multi-user state to state 1. state s, S State s (or S) is referred to as the single-user state. All user processes are stopped on transitions to this state. In the single-user state, file systems required for multi-user logins are unmounted and the system can only be accessed through the console. Logins requiring access to multi-user file systems cannot be used. state 5 Shut the machine down so that it is safe to remove the power. Have the machine remove power, if possible. The rc0 procedure is called to perform this task. state 6 Stop the operating system and reboot to the state defined by the initdefault entry in /etc/inittab. The rc6 procedure is called to perform this task. OPTIONS
-y Pre-answer the confirmation question so the command can be run without user intervention. -g grace-period Allow the super user to change the number of seconds from the 60-second default. -i init-state If there are warnings, init-state specifies the state init is to be in. By default, system state `s' is used. EXAMPLES
Example 1 Using shutdown In the following example, shutdown is being executed on host foo and is scheduled in 120 seconds. The warning message is output 2 minutes, 1 minute, and 30 seconds before the final confirmation message. example# shutdown -i S -g 120 "===== disk replacement =====" Shutdown started. Tue Jun 7 14:51:40 PDT 1994 Broadcast Message from root (pts/1) on foo Tue Jun 7 14:51:41... The system will be shut down in 2 minutes ===== disk replacement ===== Broadcast Message from root (pts/1) on foo Tue Jun 7 14:52:41... The system will be shut down in 1 minutes ===== disk replacement ===== Broadcast Message from root (pts/1) on foo Tue Jun 7 14:53:41... The system will be shut down in 30 seconds ===== disk replacement ===== Do you want to continue? (y or n): FILES
/etc/inittab controls process dispatching by init ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ SEE ALSO
boot(1M), halt(1M), init(1M), killall(1M), reboot(1M), ufsdump(1M), init.d(4), inittab(4), nologin(4), attributes(5) NOTES
When a system transitions down to the S or s state, the /etc/nologin file (see nologin(4)) is created. Upon subsequent transition to state 2 (multi-user state), this file is removed by a script in the /etc/rc2.d directory. SunOS 5.11 9 May 2001 shutdown(1M)
All times are GMT -4. The time now is 04:40 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy