Technical article 127086

ps: RDUBLK: Cannot find process ID xxx errors when doing a "ps -ef"

OpenServer 5.0.0OpenServer 5.0.2OpenServer 5.0.4OpenServer 5.0.5OpenServer 5.0.6OpenServer 5.0.7

Written · Last revised

Problem

When typing a "ps -ef", one or more processes report the error message:

ps: RDUBLK: Cannot find process ID xxx: No such device or
address (error 6).

How can I find out what these processes are and what does this error mean?

Cause

The `ps` command is unable to read the u-area for these
processes because they are swapped out.

Solution

This problem has been report to SCO Engineering.

Although these messages are bothersome, the problem is
harmless.  The problem is strictly within the ps command
and is a problem where it can't see the address space of
swapped out processes.
It is probably more of a concern that you have processes
swapped out than this error itself.  When the processes
become active again the ps command will be able to report
process information normally.

To see more information about the swapped out processes you can use the command:

# echo proc | crash

Or to find information about a specific PID, use:

# echo "proc #<PID>" | crash

The real problem is that the system is swapping, meaning that it doesn't have enough memory to run the processes that are currently running. In this situation, the system will swap out inactive processes to the swap space to free up memory for the more demanding processes.

To correct this you can either increase memory on the system or reduce the load by running less memory consuming processes.

To check the amount of memory use `memsize`, this reports
in bytes.
To check the swap space use the command `swap -l`, this
reports the swap space in 512-byte blocks.

To see the memory of your active processes, you can use the command:

# ps -ealf 2>/dev/null | pg
The SZ column shows the amount of memory in K that the processes are
using.  Check the processes that are using a lot of memory.
Alternatively, you could use skunkware utility:
`/usr/local/bin/memhog`.
Available at:
ftp://ftp2.sco.com/pub/skunkware/osr5/vols/hog-1.1-VOLS.tar
To keep the system from swapping, there needs to be enough
ram to run all of the processes.  A system that has run
out of memory may swap so much that it appears to be disk
bound.

From the Xinuos technical article database, record 127086. Reproduced with permission. The original is at www.sco.com/ta/127086, which is reachable but blocked from search engines. Xinuos marks this article against a retired product line. That refers to the product’s lifecycle, not to whether the advice still works — plenty of it still applies to running systems.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.