proc: table is full

[Waqar Razi]

The dmesg command on hpux 10.20 server is giving the following output:

proc: table is full
proc: table is full
proc: table is full
proc: table is full
proc: table is full
proc: table is full
proc: table is full
proc: table is full
proc: table is full
proc: table is full
proc: table is full
proc: table is full
proc: table is full
proc: table is full
proc: table is full
proc: table is full
proc: table is full
proc: table is full
proc: table is full
proc: table is full
LPMC type : I-Cache Parity Error.
LPMC type : I-Cache Parity Error.
LPMC type : I-Cache Parity Error.

Can any one please give me some direction?

[Alex Glennie]

http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=701321

[Ivan Krastev]

See kernel param nproc usage (with sar) and increase it if its necessary.

regards,
ivan

[Patrick Wallek]

>>proc: table is full

Your process table is too small. Increase the 'nproc' kernel parameter, rebuild the kernel and reboot.

>>LPMC type : I-Cache Parity Error.

LPMC = Low Priority Machine Check. A parity error was detected in RAM. It was correctable though.

If you keep getting these then it can indicate a problem with RAM which should be corrected by replacing the offending DIMM. However, from this output it is impossible to determine which DIMM is bad.

[James R. Ferguson]

Hi Wagar:

You can proactively monitor your process table (nproc) and file system table (nfile) with 'sar -v'. See the manpages for 'sar' for more information.

Regards!

...JRF...

[Waqar Razi]

I have another question in this regard:

What is the difference between dmesg and dmesg -. Because when I am running dmesg, its giving me the above output, but the syslog has no error logs about it. But when I run dmesg -, it doesnt give me any output or error message.

[James R. Ferguson]

Hi (again) Wagar:

> What is the difference between dmesg and dmesg -. ?

See the 'dmesg' mangpages !!! --- " If the - argument is specified, dmesg computes (incrementally) the new messages since the last time it was run and places these on the standard output."

Regards!

...JRF...

[killer1]

Hi There..

dmesg looks in a system buffer for recently printed diagnostic messages and prints them on the standard output. The messages are those printed by the system when unusual events occur (such as when system tables overflow or the system crashes).

If the - argument is specified, dmesg computes (incrementally) the new messages since the last time it was run and places these on the standard output.

In your case there are no new messages, since it was run last time.

Regards.