Sponsored Content
Operating Systems Solaris troubleshooting cause of amber light Post 302305457 by incredible on Thursday 9th of April 2009 02:35:08 AM
Old 04-09-2009
Sometimes this kind of situation justs work if you can try the following:
1-Gracefully shutdown and poweroff the system
2-Pull out the 2 power cords at the rear.
3- wait for about 30secs or so.
4-plug in powercords and monitor the console messages (ILOM messages, for any errrors)
5-Power on the system and see if the LED goes off.. Smilie
 

7 More Discussions You Might Find Interesting

1. SuSE

Amber Lights + Remote Servers

Ok, so we get reports from operations after they do walk throughs about servers with amber or red lights showing. They want us to resolve the issues. On Solaris I can run prtdiag to identify the amber lights and clear them (replace hardware or "reboot" the daemon). How do I remotely figure out... (1 Reply)
Discussion started by: BOFH
1 Replies

2. UNIX for Dummies Questions & Answers

Day light savings

Does anyone know how to reset a network printer to allow for the daylight savings?:) (0 Replies)
Discussion started by: Tweedy
0 Replies

3. Red Hat

AMBER md/g95/gfortran issue

Hi, i am trying to install AMBER10 which is a molecular dynamcis package onto two linux red hat pcs. I can successfully install the tools that comes with which uses gcc to compile, however AMBER10 requires either g95 or gfortran to compile. This is where the issue lies, i have installed both... (0 Replies)
Discussion started by: olifu02
0 Replies

4. AIX

Orange light has come on server

Hi all, we are using IBM e series server on which AIX 5.3 is runing , we got orange light on our server, so please can any one suggest me how to diabled this light. thanks alot in advance i followed these instruction befor but i couldn't able to diabled these light #diag then... (2 Replies)
Discussion started by: younusdba
2 Replies

5. AIX

p520 -- amber light

it shows up after the upgrade to SF240_415, after 2 hrs. amber light shows up on the led of 9111-520, but alog shows: everything seems to work, not sure what's going on.. (6 Replies)
Discussion started by: ppchu99
6 Replies

6. What is on Your Mind?

A bit of light entertainment. ;oD

;oD I received this snippet on facebook the other day... Enjoy:- (0 Replies)
Discussion started by: wisecracker
0 Replies

7. What is on Your Mind?

A little light entertainment... ;oD

New O'Reilly books... URL: New O'Reilly books - Album on Imgur I'll bet many of you have come across a few of these... ;oD (0 Replies)
Discussion started by: wisecracker
0 Replies
REBOOT(8)						    BSD System Manager's Manual 						 REBOOT(8)

NAME
reboot, poweroff, halt -- restarting, powering down and stopping the system SYNOPSIS
halt [-dlnpqvxz] poweroff [-dlnqvxz] reboot [-dlnqvxz] [arg ...] DESCRIPTION
The poweroff, halt and reboot utilities flush the file system cache to disk, send all running processes a SIGTERM, wait for up to 30 seconds for them to die, send a SIGKILL to the survivors and, respectively, power down, halt or restart the system. The action is logged, including entering a shutdown record into the login accounting file and sending a message via syslog(3). The options are as follows: -d Create a dump before halting or restarting. This option is useful for debugging system dump procedures or capturing the state of a corrupted or misbehaving system. -l Suppress sending a message via syslog(3) before halting or restarting. -n Do not flush the file system cache. This option should be used with extreme caution. It can be used if a disk or a processor is on fire. -p Attempt to powerdown the system. If the powerdown fails, or the system does not support software powerdown, the system will halt. This option is only valid for halt. -v To enable verbose messages on the console, pass the boothowto(9) flag AB_VERBOSE to reboot(2). -x To enable debugging messages on the console, pass the boothowto(9) flag AB_DEBUG to reboot(2). -z To silence some shutdown messages on the console, pass the boothowto(9) flag AB_SILENT to reboot(2). -q Do not give processes a chance to shut down before halting or restarting. This option should not normally be used. If there are any arguments passed to reboot they are concatenated with spaces and passed as bootstr to the reboot(2) system call. The string is passed to the firmware on platforms that support it. Normally, the shutdown(8) utility is used when the system needs to be halted or restarted, giving users advance warning of their impending doom. SEE ALSO
reboot(2), syslog(3), utmp(5), boot(8), init(8), rescue(8), shutdown(8), sync(8) HISTORY
A reboot command appeared in Version 6 AT&T UNIX. The poweroff command first appeared in NetBSD 1.5. CAVEATS
Once the command has begun its work, stopping it before it completes will probably result in a system so crippled it must be physically reset. To prevent premature termination, the command blocks many signals early in its execution. However, nothing can defend against delib- erate attempts to evade this. This command will stop the system without running any shutdown(8) scripts. Amongst other things, this means that swapping will not be dis- abled so that raid(4) can shutdown cleanly. You should normally use shutdown(8) unless you are running in single user mode. BUGS
The single user shell will ignore the SIGTERM signal. To avoid waiting for the timeout when rebooting or halting from the single user shell, you have to exec reboot or exec halt. BSD
February 16, 2011 BSD
All times are GMT -4. The time now is 07:33 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy