Sponsored Content
Full Discussion: Panic on SUN server
Operating Systems Solaris Panic on SUN server Post 302220064 by incredible on Wednesday 30th of July 2008 10:37:24 PM
Old 07-30-2008
And if you have contract with SUN, check if there's coredump created and uploaded it for root cause analysis of the issue.
What was done recently to the system? If you can track that, its easier for troubleshooting. perform fsck as instructed and check if the situation gets better
 

3 More Discussions You Might Find Interesting

1. Solaris

Sun server

I'm working on a new Sun Solaris server.It was right and run with it's installed Solaris.I used Ifconfig command and check all the file in /etc folder, and now the system can not login as ROOT user in to the server? I'm young in Unix ! I don't know what did I do? How can I comeback ? (8 Replies)
Discussion started by: Nilou
8 Replies

2. Red Hat

server panic

Hi, one of our linux server got panic with the following messages Jun 2 17:09:57 inchesfttu006 kernel: ------------------------ Jun 2 17:09:57 inchesfttu006 kernel: kernel BUG at kernel/exit.c:904! Jun 2 17:09:57 inchesfttu006 kernel: invalid operand: 0000 Jun 2 17:09:57 inchesfttu006... (1 Reply)
Discussion started by: rajasekg
1 Replies

3. Solaris

can any body tell me what is the difference between server panic and fatal error.

HI friends can any body tell me what is the difference between server panic and fatal error. (1 Reply)
Discussion started by: tv.praveenkumar
1 Replies
PANIC(9)						   BSD Kernel Developer's Manual						  PANIC(9)

NAME
panic -- Bring down system on fatal error SYNOPSIS
#include <sys/types.h> #include <sys/systm.h> void vpanic(const char *fmt, va_list ap); void panic(const char *fmt, ...); DESCRIPTION
The panic() and vpanic() functions terminate the NetBSD system. The message fmt is a printf(3) style format string which is printed to the console and saved in the variable panicstr for later retrieval via core dump inspection. A newline character is added at the end automati- cally, and is thus not needed in the format string. If a kernel debugger is installed, control is passed to it after the message is printed. If the kernel debugger is ddb(4), control may be passed to it, depending on the value of ddb.onpanic. See options(4) for more details on setting ddb.onpanic. If control is not passed through to ddb(4), a ddb(4)-specific function is used to print the kernel stack trace, and then control returns to panic(). If control remains in panic(), an attempt is made to save an image of system memory on the configured dump device. If during the process of handling the panic, panic() is called again (from the filesystem synchronization routines, for example), the system is rebooted immediately without synchronizing any filesystems. panic() is meant to be used in situations where something unexpected has happened and it is difficult to recover the system to a stable state, or in situations where proceeding might make the things worse, leading to data corruption/loss. It is not meant to be used in scenar- ios where the system could easily ignore and/or isolate the condition/subsystem and proceed. In general developers should try to reduce the number of panic() calls in the kernel to improve stability. RETURN VALUES
The panic() function does not return. SEE ALSO
sysctl(3), ddb(4), ipkdb(4), options(4), savecore(8), swapctl(8), sysctl(8) BSD
September 29, 2011 BSD
All times are GMT -4. The time now is 09:44 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy