Operating System - HP-UX
1753797
Members
6912
Online
108799
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
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
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
08-16-2010 09:23 AM
08-16-2010 09:23 AM
fsflush
Any idea how to fix the ipc handler issue with out rebooting the system - i get the below message and can not start any process.
Thanks.fsflush is utilizing high cpu utilization
Could not fork ident IPC handler,
thanks
Thanks.fsflush is utilizing high cpu utilization
Could not fork ident IPC handler,
thanks
Learning ...
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-16-2010 11:18 PM
08-16-2010 11:18 PM
Re: fsflush
You _cannot start any processes_ and are worried about one IPC handler only???
If I understood the problem correctly, you're about one step away from a situation where your system is totally unresponsive and you will have to crash it. Compared to that, being unable to start the IPC handler is a minor problem (and most likely a side effect of the main problem anyway).
The most common reason of "Could not fork" errors is that the system does not have any free memory and swap for forking new processes.
If you can, please run "swapinfo -tam" and look at the totals line. If all the swap is in use, you've found the problem.
Another possible cause might be that something has started so many processes that the kernel's process table is full. However, if that's the case, the kernel logs a specific message to identify the problem ("proc: table is full").
If you can, run "dmesg" and look at the latest kernel messages. They might offer more clues.
You should also run "ps -ef" as soon as possible, and save the output (copy & paste it to a file on your workstation if necessary).
If you have sessions logged in as root, don't log out of them; you may not be able to log back in.
If the system becomes uncontrollable and you have to crash it, use the TOC button or the TC command of the GSP/MP; this will cause the system to generate a crash dump in /var/adm/crash. The crash dump can be used to find out what was happening in the system at the time of crash. You can get a basic crash dump analysis automatically using the "crashinfo" tool (available on request from HP support). HP support may be able to do a more advanced analysis if you can send the dump to them.
See also:
http://www.unixguide.net/hp/hpuxcrashdump.shtml
http://olearycomputers.com/ll/hpq4.html
http://kristof.willen.be/node/1099
MK
If I understood the problem correctly, you're about one step away from a situation where your system is totally unresponsive and you will have to crash it. Compared to that, being unable to start the IPC handler is a minor problem (and most likely a side effect of the main problem anyway).
The most common reason of "Could not fork" errors is that the system does not have any free memory and swap for forking new processes.
If you can, please run "swapinfo -tam" and look at the totals line. If all the swap is in use, you've found the problem.
Another possible cause might be that something has started so many processes that the kernel's process table is full. However, if that's the case, the kernel logs a specific message to identify the problem ("proc: table is full").
If you can, run "dmesg" and look at the latest kernel messages. They might offer more clues.
You should also run "ps -ef" as soon as possible, and save the output (copy & paste it to a file on your workstation if necessary).
If you have sessions logged in as root, don't log out of them; you may not be able to log back in.
If the system becomes uncontrollable and you have to crash it, use the TOC button or the TC command of the GSP/MP; this will cause the system to generate a crash dump in /var/adm/crash. The crash dump can be used to find out what was happening in the system at the time of crash. You can get a basic crash dump analysis automatically using the "crashinfo" tool (available on request from HP support). HP support may be able to do a more advanced analysis if you can send the dump to them.
See also:
http://www.unixguide.net/hp/hpuxcrashdump.shtml
http://olearycomputers.com/ll/hpq4.html
http://kristof.willen.be/node/1099
MK
MK
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP