syslog message

[Felipe Ramirez Salcido]

What this syslog message means?

Apr 23 08:56:05 urrprd01 above message repeats 10 times
Apr 23 08:38:31 urrprd01 vmunix: file: table is full

And what problems will presents about this?
thank's for your help.

[Mark Vollmers]

Is there anything else in the log, or did this just appear out of nowhere? Did you notice anything with performance when or after it appears? It might refer to the inode table, that's just a guess.

Mark

[Alan Riggs]

It means your file table is full. verify this with sar -v. Correct it by increasing the size of your file table (Kernel modification to nfile parameter, reboot required).

[Patrick Wallek · Accepted solution]

Felipe,

The message indicates that your nfile table has been maxed out. You must increase this kernel value to fix this if you get this on a regular basis. If this is a one time thing, have some users log out and this should go away. The nfile parameter is the maximum number of files you can have open at one time.

Here are a couple of documents in the TKB you can take a look at for more information:
http://us-support3.external.hp.com/cki/bin/doc.pl/sid=24666da11ca93c4c6a/screen=ckiDisplayDocument?docId=200000038250854

http://us-support3.external.hp.com/cki/bin/doc.pl/sid=24666da11ca93c4c6a/screen=ckiDisplayDocument?docId=400000000013822

[A. Clay Stephenson]

This is a syslog message telling you that the kernel parameter nfile needs to be increased. You can make this entry quite large since each entry consumes only a few tens of bytes. You should be able to do a sar -v and check for
overflows and current settings. It the file-sz values are near the maximum you need to gen a new kernel.
Go into SAM
SAM->Kernel Configuration->Configurable Parameters and adjust nfile.
Then select Actions->Create a New Kernel.
Take the deafukr actions from there. I would increase nfiles by about 50%. (The kernel rebuild will require a reboot so that you may need to schedule after hours).

[Felipe Ramirez Salcido]

Hi, Than's to all of you for your answers.

I'm now understend a little bit mor about this message. A few weeks ago, I changed the maxusers, and the nproc kernel parameters of my HP-UX 11 system, in accordance with the recommendations from my aplication consultants (SAP consultants), have these modifications might cause this problem? How can I calculate or know the aproppiate value for nfile parameter?

[Felipe Ramirez Salcido]

Hi, Thank's to all for your help.

I'm now understanding a little bit mor about this message.
A few weeks ago, I changed the maxusers, and the nproc kernel parameters of my HP-UX 11 system, in accordance with the recommendations from my aplication consultants (SAP consultants), had these modifications caused this problem? How can I calculate or know the aproppiate value for nfile parameter in accordance with this other parameters?

[A. Clay Stephenson]

The kernel tuning guide suggests:
16 *(nproc + 16 + maxusers)/10 + 32 + 2 *(npty + nstrpty+nstrtel).
Since each entry is only about 32 bytes of kernel space, I would increase it by about 50-100% and go from there.