- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Tracking Processes That Have Died
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-15-2003 01:06 AM
07-15-2003 01:06 AM
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
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-15-2003 01:19 AM
07-15-2003 01:19 AM
Re: Tracking Processes That Have Died
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-15-2003 01:27 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-15-2003 01:29 AM
07-15-2003 01:29 AM
Re: Tracking Processes That Have Died
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-15-2003 01:36 AM
07-15-2003 01:36 AM
Re: Tracking Processes That Have Died
Thanks for the help, much appreciated.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-15-2003 01:40 AM
07-15-2003 01:40 AM
Re: Tracking Processes That Have Died
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