HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- couldn't kill process hpunix 11.23
Operating System - HP-UX
1834884
Members
2457
Online
110071
Solutions
Forums
Categories
Company
Local Language
back
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
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- 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
11-08-2007 02:05 AM
11-08-2007 02:05 AM
while shutting down the oracle database last night we got this error:
Job queue slave processes stopped
All dispatchers and shared servers shutdown
Thu Nov 8 00:30:15 2007
Process OS id : 13536 alive after kill
Errors in file
Thu Nov 8 00:50:16 2007
MMNL absent for 1218 secs; Foregrounds taking over
is there some system log we can look at that would identify what process 13536 was since it's no longer exists ?
(if this is a duplicate post i apologize)
Job queue slave processes stopped
All dispatchers and shared servers shutdown
Thu Nov 8 00:30:15 2007
Process OS id : 13536 alive after kill
Errors in file
Thu Nov 8 00:50:16 2007
MMNL absent for 1218 secs; Foregrounds taking over
is there some system log we can look at that would identify what process 13536 was since it's no longer exists ?
(if this is a duplicate post i apologize)
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-08-2007 02:30 AM
11-08-2007 02:30 AM
Solution
I doubt it would be in any system level logs. The only place I could maybe see it is if you were shutting down the server, it may be in the /etc/rc.log.old. Even then I doubt the amount of detail in there would be enough to identify what that process is. It would have to of been provided by the /sbin/init.d/oracle stop or whatever script you use to stop the database.
Which the ones I see, typically don't show that level of detail.
Which the ones I see, typically don't show that level of detail.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-08-2007 05:40 AM
11-08-2007 05:40 AM
Re: couldn't kill process hpunix 11.23
If you have Glance Plus installed and the MWA collectors running you could get a list of PIDS from that timeframe.
An option for the future if the above isn't available. A minute or so before running the Oracle shutdown script, start running ps -ef and capture the output every 10 seconds or so. Run this in a cron script for the duration of the oracle shutdown. Review the output when done.
An option for the future if the above isn't available. A minute or so before running the Oracle shutdown script, start running ps -ef and capture the output every 10 seconds or so. Run this in a cron script for the duration of the oracle shutdown. Review the output when done.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP