11-08-2006
Solved. This LPAR had been setup wrongly. It has 8 physical CPUs and had been set to 24 logical (48 when lparstat is run). This was effecting the shared memory paging. When I ran nmon as a normal user (not root) the first thing it looked was /dev/kmem (kernel shared memory). When I changed the permissions on the device so world had rights to it the core dump occurred. I have now reduced the logical CPUs down to match the physical and nmon is now working again. Strange.
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
LEARN ABOUT ULTRIX
savecore
savecore(8) System Manager's Manual savecore(8)
Name
savecore - save a core dump of the operating system
Syntax
/etc/savecore [ options ] dirname [ system ] [ corename ]
Description
The command is meant to be called near the end of the file. The command saves the core dump of the system (assuming one was made) and
writes a reboot message in the shutdown log.
The command checks the core dump to be certain it corresponds with the current running ULTRIX. If it does, it saves the core image in the
file dirname/vmcore.n and saves the namelist in the file dirname/vmunix.n. The trailing .n in the pathnames is replaced by a number which
increments each time is run in that directory.
After saving the core and namelist images, will save the error logger buffer into a predetermined file. The error logger buffer contains
information about why the crash occurred. After completes, the daemon will extract the error logger file and translate its contents into a
form familiar to the program.
Before writes out a core image, it reads a number from the file dirname/minfree. If there are fewer free blocks on the filesystem that
contains dirname than the number obtained from the file, a core dump is not done. If the file does not exist, savecore always writes out
the core file (assuming that a core dump was taken).
The command also writes a reboot message in the shut down log. If the system crashed as a result of a panic, also records the panic string
in the shut down log.
For partial crash dumps, creates a sparse core image file in dirname/vmcore.n. If this sparse core image file is copied or moved to
another location, the file expands to its true size which can take too much file system space. Hence, to copy or move sparse core image
files, you must use the command. The command has a conversion option to create sparse output files.
Options
-c Clears the core dump. This option is useful when the core dump is corrupted in a way that will not allow to save it safely. Use the
option with caution, because once it clears the core dump, the core dump cannot be retrieved.
-d dumpdev dumplo
Specifies the dump device and the dump offset when running on a system image other than the currently running system image. The pro-
gram assumes that the running system image is and it reads the dump device and dump device offset are different in the system image
that crashed, the option provides the correct dump device and dump device offset.
-e Saves only the error logger buffer into a file. If used, core or namelist images are not saved.
-f corename
Takes the i corefile name as the file from which to extract the the crash dump data instead of the default dump device. This option
is used only for diskless workstations.
If the core dump was from a system other than /vmunix, the name of that system must be supplied as system. The program assumes that the
running image is
After successful completion, the core dump is cleared. Also, a message is written in the file which tells whether the dump succeeded or
failed.
Files
Shut down log
Current running ULTRIX system
See Also
dd(1), uerf(8)
savecore(8)