Monitoring and controlling a crashing application

[Dan Am]

Hi all,
a customer has an application on a 9000, K-Class, and complains about the application crashing with "not enough memory". However "top" tells me there are reserves.

1. Can I have "sar" monitor this single process ? I cannot seem to find an option.

2. Could I adjust things with "ulimit" ?
Ulimit shows a limit on "stack size". Could that be the problem ?

3. What unit does the "C"-field in "ps -ef" measure ? Percent ? It' not on the man-page :-(

Lot of q's , sorry, but all circumnavigating the same prob.

TIA

Regards

Dan

[Steve Steel]

Hi


1)get glance to monitor a process.


2)use swapinfo -ta to see for memory.


3)if it coredumps what is the output of
file core

4)Quick and rough memory usage list

/bin/rm /tmp/$PPID 2>/dev/null
UNIX95= ps -e -o ruser,vsz,pid,args > /tmp/$PPID
head -n 1 /tmp/$PPID
tail -n +2 /tmp/$PPID| sort -rnk2
/bin/rm /tmp/$PPID 2>/dev/null

5)Do you have any messages in the syslog.

6)Look at kernel parameters
maxssiz maxdsiz

7)ulimit can be adjusted in the posix shell
to test
. see man sh-posix


ulimit [-HSacdfnst] [limit]

Set or display a resource limit. The limit for a specified
resource is set when limit is specified. The value of limit can
be a number in the unit specified with each resource, or the
keyword unlimited.

The -H and -S flags specify whether the hard limit or the soft
limit is set for the given resource. A hard limit cannot be
increased once it is set. A soft limit can be increased up to
the hard limit. If neither -H nor -S is specified, the limit
applies to both. The current resource limit is printed when
limit is omitted. In this case, the soft limit is printed unless
-H is specified. When more than one resource is specified, the
limit name and unit are printed before the value.
3:00:26
If no option is given, -f is assumed.





Hewlett-Packard Company - 18 - HP-UX Release 10.10: April 1997






sh-posix(1) sh-posix(1)




-a List all of the current resource limits.
-c The number of 512-byte blocks in the size of core dumps.
-d The number of kilobytes in the size of the data area.
-f The number of 512-byte blocks in files written by child
processes (files of any size can be read).
-n The number of file descriptors.
-s The number of kilobytes in the size of the stack area.
-t The number of seconds to be used by each process.



The C in ps is unimportant for this


Steve Steel

[Steve Steel]

Hi

fyi
cpu Processor utilization for scheduling. The default
heading for this column is C.


steve Steel

[Carlos Fernandez Riera]

Use tusc ( or truss),

Search these words on the forum to get the URL from where yopu can download.