Showing results for 
Search instead for 
Did you mean: 

Re: fsflush

Super Advisor


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,
Learning ...
Honored Contributor

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: