11-06-2006
Another NMON
Anyone ever experienced a core dump when running NMON. I am running AIX 5.3 on an 8 CPU LPAR (P570). This has only recently started to happen.
10 More Discussions You Might Find Interesting
1. AIX
Can any one help where i can find articals about nomn
I need to know how to read this tools
┌─CPU-Utilisation-Small-View───────────────────────────────────────────────────┐
│ 0----------25-----------50----------75----------100│
│CPU User% Sys% Wait% Idle%| ... (3 Replies)
Discussion started by: habuzahra
3 Replies
2. AIX
HI Im new on this world.
Im working with nmon and I understand that this tool generates a files that later with excel I can see the graphcial of my server.
The problem is that this process is execute manualy and I need to meake automatic.
How can I do That.
Sorry for my english!! :o (3 Replies)
Discussion started by: jegtoro
3 Replies
3. AIX
How to analyze nmon output or is there any tool for analyzing. (2 Replies)
Discussion started by: vjm
2 Replies
4. AIX
Hi All,
I have a p550 server with 4 proc. But when i run nmon analyzer in cpu_sum it show 5 processors cpu0 cpu1 cpu2 cpu3 cpu4. Why it is showing 5 processors. (6 Replies)
Discussion started by: vjm
6 Replies
5. AIX
Hi,
I want to know how to use nmon in aix?
I have donwloaded nmon (2 Replies)
Discussion started by: manoj.solaris
2 Replies
6. AIX
HI,
I have downloaded nmon 3.3c nmon analyzer, and run the command on aix ./nmon -f
After that I have terminated the process and found .nmon file.
when i have tried to open that file in nmon analyzer i.e in excel I am getting the error "no valid input data nmon run may have failed"
... (8 Replies)
Discussion started by: manoj.solaris
8 Replies
7. Red Hat
Hi guys,
as per subject i am setting up NMON for the above OS but it is 64-bit Linux.
I downloaded the 32-bit NMON for RHEL45 as it is the only one available for RHEL45.
However, I ran into problem with the binary file.
# ./nmon_x86_rhel45
./nmon_x86_rhel45: error while loading shared... (13 Replies)
Discussion started by: DrivesMeCrazy
13 Replies
8. AIX
Hi All,
First of all, I am a DBA and not an AIX admin. I am new at using this NMON tool.
In interactive mode, I can start nmon, push 't' to have the list of process with their statistic (ie cpu% etc.).
I would like to know if there is a way to redirect that screen output into a log... (1 Reply)
Discussion started by: Nayas
1 Replies
9. AIX
Hi guys, I am an Oracle DBA and I have an account with some databases on an AIX 5.3 server. I am trying to figure out if I really need to add memory to this box or not, the account team keeps pushing me to make a decision and I don't want to waste their money if I don't need to right now, we could... (4 Replies)
Discussion started by: nibbsbitt
4 Replies
10. Shell Programming and Scripting
Hi, my name is Steve Ngai from Malaysia. This is my first post. Hope to learn more about Unix from this forum.
My first question is can nmon be customized? When I run nmon, I need to manually type c to see CPU usage, then m for memory usage. Can I pass it some nmon option to automatically see... (2 Replies)
Discussion started by: ngaisteve1
2 Replies
KGDB(1) BSD General Commands Manual KGDB(1)
NAME
kgdb -- kernel debugger
SYNOPSIS
kgdb [-a | -f | -fullname] [-b rate] [-q | -quiet] [-v] [-w] [-d crashdir] [-c core | -n dumpnr | -r device] [kernel [core]]
DESCRIPTION
The kgdb utility is a debugger based on gdb(1) that allows debugging of kernel core files.
The options are as follows:
-a Increase the annotation level. An annotation level of 1 features the historical -fullname option of gdb(1). This is useful
when running kgdb in Emacs. The -f or -fullname options are supported for backward compatibility as well.
-b rate Set the baudrate to rate.
-q Suppress printing of the banner when the debugger starts. The -quiet form is supported for compatibility as well.
-v Increase verbosity.
-w Opens kmem-based targets in read-write mode. (This is identical to what --wcore used to do in previous gdb versions for
FreeBSD.)
-d crashdir Use crashdir instead of the default, /var/crash to locate kernel core dump files in. The name vmcore. plus the dump number will
be appended to determine the actual dump file name.
-c core Explicitly use core as the core dump file.
-n dumpnr Use the kernel core dump file numbered dumpnr for debugging.
-r device Use device to connect kgdb to for a remote debugging session.
The -c, -n, and -r options are mutually exclusive.
Optionally, the name of the kernel symbol file and the name of the core dump file can be supplied on the command-line as positional argu-
ments. If no kernel symbol file name has been given, the symbol file of the currently running kernel will be used. If no core dump file has
been specified through either of the options or the last command-line argument, /dev/mem will be opened to allow debugging the currently run-
ning kernel.
FILES
/dev/mem Default memory image to open if no core dump file has been specified.
/var/crash Default directory to locate kernel core dump files.
SEE ALSO
gdb(1)
HISTORY
The kgdb utility first appeared in its current form in FreeBSD 5.3.
BSD
October 11, 2006 BSD