Operating System - HP-UX
1832460 Members
3177 Online
110043 Solutions
New Discussion

Tracking Processes That Have Died

 
SOLVED
Go to solution
Martin Corner
Advisor

Tracking Processes That Have Died

Hi,

I am trying to find a way to track processes that have died.

We have a Progress database running in a different timezone to our IT department. The users complain of slowness at various times during the day and we can get the process ID from Perfview. Unfortunately the process has always died so we can't see what was actually running. Perfview only tells us it was a database user in User Name.

So, apart from trying to trap the process by piping a continous ps -ef to file using cron. Is there any better solutions? Is there something in Measureware or Perfview I am missing?

TIA
5 REPLIES 5
Paula J Frazer-Campbell
Honored Contributor

Re: Tracking Processes That Have Died

Sue

Top ?
Glance?

Altought I believe sar is is your best bet for a start point.

http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xaeb779bffde7d4118fef0090279cd0f9,00.html

Paula
If you can spell SysAdmin then you is one - anon
Ollie R
Respected Contributor
Solution

Re: Tracking Processes That Have Died

Hi,

You could turn on process accounting:
man 1m acctsh

This will track data from all processes which have stopped/died.

Ollie.
To err is human but to not award points is unforgivable
Martin Corner
Advisor

Re: Tracking Processes That Have Died

We have sar, glance and measureware running but it still doesn't tell me about dead processes. I need the information from ps -ef about a particular process ID.

This would be easy if I was awake, but I need the information when I am alseep. Measureware tells me what PID was causing the problem but it doesn't give me the detailed information I need. I need the detailed information of a ps -ef PID. I am hoping somebody has a utility that does this or there is an option in Measureware/PerfView that I am missing.

Thanks
Martin Corner
Advisor

Re: Tracking Processes That Have Died

acctsh looks like what we are looking for.

Thanks for the help, much appreciated.
Paula J Frazer-Campbell
Honored Contributor

Re: Tracking Processes That Have Died

Sue

Because the pid will be different each time then it looks like a cron on ps to start your investigation.


#/bin/sh
echo "-----------------" >> /tmp/ps_watch
date >> /tmp/ps_watch
echo "-----------------" >> /tmp/ps_watch
ps -efl >> /tmp/ps_watch
echo " "


Run it from cron say every 120 seconds and then examine the results next day.

Ensure that your storage area has sufficient space to contain a nights ps info.

Also set env variables in your cron job and give ps its full path.

HTH

Paula



If you can spell SysAdmin then you is one - anon