02-08-2002
What kind of server?
If you have the server documentation, it will have troubleshooting in it for these types of problems. If you have nothing on the keyboard when power is turned on (no beeps, or no lights flashing on num lock, caps lock...) then it could be a bad power supply, bad cpu. If you do get at least the first beep and some of the keyboard lights flash (before the monitor starts getting any messages to it) but you never start the boot or get to the openboot prompt, then it may be a disk drive.
Check docs.sun.com - they may have the documentation you need for your server there if you didn't save the hard-copy.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi
I faced a problem while booting linux which is as follows;-
*************************************************
Inode 146180 has illegal block(s)
xauth:error in locking authority file /home/root/.Xauthority
Fatal Server Error:
Could not create lock file in /tmp/tXo-lock
... (1 Reply)
Discussion started by: Abhishek
1 Replies
2. UNIX for Advanced & Expert Users
We have had a server (Solaris 2.6) hardisk crash. When booting the server we get:
ok> boot -S
Boot Device: /sbus/espdmc@e, 8400000/esp@e,8800000/sd@0,0
short read 0x2000 chars read
disk read error
The only way we can get into the console is to
ok> boot cdrom
whereby everything (e.g.... (3 Replies)
Discussion started by: Breen
3 Replies
3. HP-UX
hi friends,
i know that when there is a crash then that memory image is
put into /var/adm/crash
but if the system hangs up and if i have access to console of
that machine then how can i take the crash dump manully.
thanks (2 Replies)
Discussion started by: mxms755
2 Replies
4. Linux
Is it true that you can't have the crash dump server/client on the same server?
I know I've installed Nagios open source before, I though it's only for that kind of thing. I never though that Red hat ent 4 would be like client/server on the crash dump.
if someone is having problem with high... (0 Replies)
Discussion started by: itik
0 Replies
5. Programming
Problem
- Linux Client/Server Socket Application: Preventing Client from quitting on server crash
Hi,
I am writing a Linux socket Server and Client using TCP protocol on Ubuntu 9.04 x64.
I am having problem trying to implement a scenario where the client should keep running even when the... (2 Replies)
Discussion started by: varun.nagpaal
2 Replies
6. Red Hat
Hello Folks,
My RHEL 4.3 server got crashed due to hardware crash,system hard disk and motherboard replaced and RAID rebuilt done.
while rebooting the server the server is gone into single user mode due to /sda5 var partition not able to mount.
Error :- " wrong fs type, bad... (1 Reply)
Discussion started by: kmvinay
1 Replies
7. SCO
Hi there.
Well i have a really bad problem with my server:
UnixWare Version 5 Release 7
The system crash :wall: and show the error:
Panic: Kernel-mode address fault on user address 0x00000004 :eek:
If anyone knows about the reason of this error please give me a help
Sorry by my english.... (3 Replies)
Discussion started by: danilosevilla
3 Replies
8. Programming
The steps to test the problem
1. Open TCP Server
2. Open TCP Client
3. TCP Client sends data to Server.
4. Close TCP Server and the client also crash without any notification
Second wonderful test:
1. Comment the following statement in Client.c (at line 168) and compile it
Writen(... (1 Reply)
Discussion started by: sehang
1 Replies
9. Red Hat
hi,
i would like to configure netdump, but saving the var/crash in the server itself, not in another server.
could anybody tell me if this is possible?
thanks (4 Replies)
Discussion started by: pabloli150
4 Replies
10. UNIX for Dummies Questions & Answers
Environmnet: HP-UX B.11.31 U ia64
RDBMS: Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
Question:
When server hangs or node evicts, we open up tickets with Oracle Support and Oracle Support ask for some list of log files.
Currently we can not use the... (2 Replies)
Discussion started by: Siva SQL
2 Replies
power(9E) Driver Entry Points power(9E)
NAME
power - power a device attached to the system
SYNOPSIS
#include <sys/ddi.h>
#include <sys/sunddi.h>
int prefixpower(dev_info_t *dip, int component, int level);
INTERFACE LEVEL
Solaris DDI specific (Solaris DDI). This entry point is required. If the driver writer does not supply this entry point, the value NULL
must be used in the cb_ops(9S) structure instead.
PARAMETERS
dip Pointer to the device's dev_info structure.
component Component of the driver to be managed.
level Desired component power level.
DESCRIPTION
The power(9E) function is the device-specific Power Management entry point. This function is called when the system wants the driver to set
the power level of component to level.
The level argument is the driver-defined power level to which the component needs to be set. Except for power level 0, which is inter-
preted by the framework to mean "powered off," the interpretation of level is entirely up to the driver.
The component argument is the component of the device to be power-managed. The interpretation of component is entirely up to the driver.
When a requested power transition would cause the device to lose state, the driver must save the state of the device in memory. When a
requested power transition requires state to be restored, the driver must restore that state.
If a requested power transition for one component requires another component to change power state before it can be completed, the driver
must call pm_raise_power(9F) to get the other component changed, and the power(9E) entry point must support being re-entered.
If the system requests an inappropriate power transition for the device (for example, a request to power down a device which has just
become busy), then the power level should not be changed and power should return DDI_FAILURE.
RETURN VALUES
The power() function returns:
DDI_SUCCESS Successfully set the power to the requested level.
DDI_FAILURE Failed to set the power to the requested level.
CONTEXT
The power() function is called from user or kernel context only.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Interface stability |Evolving |
+-----------------------------+-----------------------------+
SEE ALSO
attach(9E), detach(9E), pm_busy_component(9F), pm_idle_component(9F), pm_raise_power(9F), cb_ops(9S)
Writing Device Drivers
Using Power Management
SunOS 5.10 12 Dec 2003 power(9E)