Skip to main content

Core Dump and Crash Dump Solaris

Crash Dump : When an operating system 
or system hardware has an error (fatal)
system generates crash dump.


Core Dump : When any user process or
application has an error system
generates core dump.


Note: When an operating system crashes,
the save core command runs
automatically during the first boot.
This command retrieves the crash dump
from the dump device
[by default partition] and then writes
crash dump to the file at the following 
location i-e 
/var/crash/hostname/file

Crash Dump saves Kernel core information
in the below mentioned file i-e
/var/crash/hostname/vmcore.x

and it saves name list information along
with symbolic information in the 
below file i-e
/var/crash/hostname/unix.x


Note: Within the crash dump directory
file named as "Bounds" is created 
automatically when dumping happens 
for the first time. This file holds a number
that is used as suffix for the next dump 
to be set.This dump is used by root
administrator for system problem 
analysis.

To view crash dump Configuration 
we use command :

#dumpadm

This command reads the statement
from /etc/dumpadm.conf file and
displays output.

To configure/modify the crash dump 
configuration we use command:

#dumpadm -c -all -d /dev/dsk/c0t0d0s1


-c : to specify type of data
-d : to specify device that stores dump data as 
     the system crashes.

dsk : swap block device

Note: If SVM is configured in swap then :
/dev/md/dsk/d0


To generate Crash Dump manually
use the command :

#savecore -L /var/crash/hostanme

To view Core dump configuration
use command : 

#Coreadm
It reads /etc/coreadm.conf and 
displays output.       

To disable and enable core dump settings : 

#dumpadm -n 

and 

#dumpadm -y

Comments

Popular posts from this blog

Setting up X11 Access to the Solaris GUI Gnome Desktop

How to   access the GUI desktop environment on a Solaris 11 SPARC server from Windows, MAC, Solaris or Linux desktop computer. As most of the time SPARC based servers are installed using the Oracle Solaris 11 Text  Installer (installing the solaris-large-server group of software packages), the desktop  environment is not installed (mostly to keep the system lightweight) . So the only option for connecting remotely to the server is with an SSH client and a command line interface  (Known as Terminal). Most widely used software to connect to a command line is Putty. For beginners , who haven’t worked on any unix/linux system , it takes time to adjust to the commands and syntax of terminals (The so called black screen).   Installation Overview To accomplish our task   we will   follow these three steps: 1. Install the Gnome desktop environment on our SPARC server. Note – If we use the text installation method, the Oracle Solaris Desktop package (solar...

NTP Sync In Solaris

For Solaris 5.11: a) Create the /etc/inet/ntp.conf           $ cat ntp.conf             server 10.xx.x.xx       prefer b) Start the NTP Service.           # svcadm disable ntp           # svcadm enable ntp c) ntpq -p  ntpdate -q 10.xx.x.xx to (check time difference). For more info please refer: Visit here 2 . For Solaris 5.10:    a) Create the /etc/inet/ntp.conf           $ cat ntp.conf             server 10.xx.x.xx       prefer    b) Start the NTP Service.           # svcadm disable svc:/network/ntp:default           # svcadm enable svc:/network/ntp:default    c) ntpq -p  /usr/sbin/ntpdate -q 10.xx.x.xx to (check time difference). 3. For Solaris 5.9:  ...

Syslog in Solaris

 Syslog is system messaging feature  which takes system activities and  events which can be helpful for an administrator to maintain the system  and  for troubleshooting tasks. Daemon : Syslogd Database Files: /etc/syslog.conf : This file contains two different fields. a). Selector  b). Action a. Selector: It specifies that at which     event system report is to be generated.    It is sub-divided into two parts:     1. Facility : It specifies report         generation based on activities         in regards to user process,mail-system        ,authorisation process,daemons,        scheduler facilities etc.           2. Level : It defines importance of message         system task.There are various levels such as         Emerg for panic conditions , Crit for critic...