NETDUMP-SERVER(8) System Programs NETDUMP-SERVER(8)NAME
netdump-server - handle crash dumps over the network
SYNOPSIS
netdump-server [--port portnumber]
[--concurrent number]
[--pidfile path]
[--daemon]
[--help] [--usage]
DESCRIPTION
Listens to the network for clients that crashes and uses the netdump protocol to recieve a memory dump and a stack trace. The memory dump
and oops message are stored in a timestamped directory in /var/crash. The server can also run scripts when some events happen.
OPTIONS --port portnumber
Specifies the IP port number for the netdump server to listen to. The default is 6666.
--concurrent number
You can limit the amount of concurrent dumps being done at any one time. If more clients than the specified maximum connects at one
time the last ones will just be logged and then rebooted.
--pidfile path
Store a pidfile. The default service uses /var/run/ttywatch.pid. The default is not to write a pidfile.
--daemon
ttywatch should background itself and run as a daemon.
EXAMPLES
netdump-server --daemon
This launches the netdump-server and puts it in the background, listening for crashed clients.
EXIT STATUS
Exit status is 0 for a clean exit and non-0 for a non-clean exit.
FILES
/etc/netdump.conf
A configuration file read by netdump-server on startup. It is a "key=value" style file. Currently it supports the options: port,
max_concurrent_dumps, daemon and pidfile.
/etc/init.d/netdump-server
An init script to start a default system installation of netdump-server. This is normally turned off by default; use the command
/sbin/chkconfig netdump-server on
to enable the netdump-server service.
/var/crash
The main directory where the crash dump files are stored. Each dump is put in a subdirectory named with the ip of the crashed
machine and the date and time of the crash.
/var/crash/scripts
This directory can contain scripts that are run at various times. They all get passed the ip of the crashing machine as the first
argument, and each one except netdump-start gets the directory that the dump is written into as the second argument.
netdump-start - This is called when a client connects to the server to tell it that it has just started the netdump client. This
normally means that the machine just booted up.
netdump-crash - This is run when a client reports that it has crashed. If it returns a non-zero value the dump request will be
ignored and the client will be told to reboot immediately
netdump-nospace - This is run when there is not enough diskspace for the dump of the crashed machine. If this script exits with a
non-zero return value netdump-server will try once again (but only once) before giving up the dump. If this script exits with a zero
return value, netdump-server will reboot the client without performing a dump.
netdump-reboot - This is run when netdump-server is finished with a client and is about to tell the client to reboot itself.
SEE ALSO netdump(8)BUGS
Report any bugs you find to http://bugzilla.redhat.com/bugzilla
AUTHOR
Alexander Larsson <alexl@redhat.com>
Linux 14 Feb 2002 NETDUMP-SERVER(8)
Check Out this Related Man Page
savecore(1M) System Administration Commands savecore(1M)NAME
savecore - save a crash dump of the operating system
SYNOPSIS
/usr/bin/savecore [-Lvd] [-f dumpfile] [directory]
DESCRIPTION
The savecore utility saves a crash dump of the kernel (assuming that one was made) and writes a reboot message in the shutdown log. It is
invoked by the dumpadm service each time the system boots.
savecore saves the crash dump data in the file directory/vmcore.n and the kernel's namelist in directory/unix.n. The trailing .n in the
pathnames is replaced by a number which grows every time savecore is run in that directory.
Before writing out a crash dump, savecore reads a number from the file directory/minfree. This is the minimum number of kilobytes that must
remain free on the file system containing directory. If after saving the crash dump the file system containing directory would have less
free space the number of kilobytes specified in minfree, the crash dump is not saved. if the minfree file does not exist, savecore assumes
a minfree value of 1 megabyte.
The savecore utility also logs a reboot message using facility LOG_AUTH (see syslog(3C)). If the system crashed as a result of a panic,
savecore logs the panic string too.
OPTIONS
The following options are supported:
-d Disregard dump header valid flag. Force savecore to attempt to save a crash dump even if the header information stored on
the dump device indicates the dump has already been saved.
-f dumpfile Attempt to save a crash dump from the specified file instead of from the system's current dump device. This option may be
useful if the information stored on the dump device has been copied to an on-disk file by means of the dd(1M) command.
-L Save a crash dump of the live running Solaris system, without actually rebooting or altering the system in any way. This
option forces savecore to save a live snapshot of the system to the dump device, and then immediately to retrieve the data
and to write it out to a new set of crash dump files in the specified directory. Live system crash dumps can only be per-
formed if you have configured your system to have a dedicated dump device using dumpadm(1M).
savecore -L does not suspend the system, so the contents of memory continue to change while the dump is saved. This means
that live crash dumps are not fully self-consistent.
-v Verbose. Enables verbose error messages from savecore.
OPERANDS
The following operands are supported:
directory Save the crash dump files to the specified directory. If directory is not specified, savecore saves the crash dump
files to the default savecore directory, configured by dumpadm(1M).
FILES
directory/vmcore.n
directory/unix.n
directory/bounds
directory/minfree
/var/crash/'uname -n' default crash dump directory
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO adb(1), mdb(1), svcs(1), dd(1M), dumpadm(1M), svcadm(1M), syslog(3C), attributes(5), smf(5)NOTES
The system crash dump service is managed by the service management facility, smf(5), under the service identifier:
svc:/system/dumpadm:default
Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). The ser-
vice's status can be queried using the svcs(1) command.
If the dump device is also being used as a swap device, you must run savecore very soon after booting, before the swap space containing the
crash dump is overwritten by programs currently running.
SunOS 5.10 25 Sep 2004 savecore(1M)