Sponsored Content
Full Discussion: random Physical memory dump
Top Forums UNIX for Dummies Questions & Answers random Physical memory dump Post 302594786 by rformt on Wednesday 1st of February 2012 07:05:00 AM
Old 02-01-2012
Data random Physical memory dump

I am currently running unix open server 6.0 on a Dell Power Edge R720. The system will be running fine when the blue screen appears and states the system has performed a physical memory dump in # of ticks. I reboot the system and all looks well. Running diagnostics does not show anything wrong. The machine will run between 5 and 20 days before crashing. The number of days is always different each time.
 

10 More Discussions You Might Find Interesting

1. Programming

Physical Memory

Hi, My problem is next.... How can I work with physical memory in the Unix FreeBSD 2.2 or hight? What is the "mem" & "kmem" drivers? P.S./ writing device driver for UNIX FreeBSD 2.2 :D (2 Replies)
Discussion started by: Alex_T
2 Replies

2. UNIX for Dummies Questions & Answers

physical memory

It is just a general question....is there a limit on the memory? I am looking into a process to store image files on the unix server which will be accessed by the application, and I just wonder if there is any limit regarding the physical or virtual memory. I am very new to unix, so thanks for... (1 Reply)
Discussion started by: cchien
1 Replies

3. Shell Programming and Scripting

get physical and virtual memory

What command can i use to get the physical and virtual memory of a database? (7 Replies)
Discussion started by: tads98
7 Replies

4. UNIX for Advanced & Expert Users

vmstat -P (physical memory)

vmstat -P commands gives me an output as shown at the end of this message. my first question is about the difference between "total physical memory" and "total physical memory use" "Total Physical Memory" -"Total Physical Memory Use" 524288 pages-524026 pages= 262 pages does it mean... (0 Replies)
Discussion started by: gfhgfnhhn
0 Replies

5. Solaris

How to check physical memory

HI Please help me how to check the physical memory, model name and hardisk information. (5 Replies)
Discussion started by: jeelans
5 Replies

6. Solaris

physical memory

what is the command to find the physical memory in soalris OS and how to find whether paging is happening or not ? (2 Replies)
Discussion started by: jayaramanit
2 Replies

7. Solaris

How to find Total and Free Physical Memory and Logical Memory in SOLARIS 9

Hi, Im working on Solaris 9 on SPARC-32 bit running on an Ultra-80, and I have to find out the following:- 1. Total Physical Memory in the system(total RAM). 2. Available Physical Memory(i.e. RAM Usage) 3. Total (Logical) Memory in the system 4. Available (Logical) Memory. I know... (4 Replies)
Discussion started by: 0ktalmagik
4 Replies

8. Solaris

restrcit physical memory with zone.max-locked-memory

Is it possible to restrict physical memory in solaris zone with zone.max-locked-memory just like we can do with rcapd ? I do not want to used rcapd (1 Reply)
Discussion started by: fugitive
1 Replies

9. AIX

Physical Memory expansion

IBM says we cannot expand our physical memory on our 570's without upgrading all the existing DIMMS since all slots are currently full. Is it really so difficult for IBM to build servers that leave a couple vacant slots for future expansion? A technical explanation would be greatly appreciated.... (2 Replies)
Discussion started by: 1computerman
2 Replies

10. Solaris

Physical memory calculation

Below is Physical Memory result : -bash-3.00$ prtconf | grep "Memory size" Memory size: 36854 Megabytes -bash-3.00$ vmstat 1 2 | tail -1 0 0 0 28220616 1318888 15 143 0 0 0 0 0 253 2 15 0 5215 14989 5917 7 0 93 and the script i have to calculate this in Percentage is : #!/bin/sh... (3 Replies)
Discussion started by: mjoshi010207
3 Replies
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)
All times are GMT -4. The time now is 06:02 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy