1837971 Members
3373 Online
110124 Solutions
New Discussion

syslog.log

 
SOLVED
Go to solution
Mazen Al-Jarrah
Advisor

syslog.log

I'm getting the following message in syslog.log:

vmunix: file: table is full


what should I do
8 REPLIES 8
Khalid A. Al-Tayaran
Valued Contributor
Solution

Re: syslog.log

T G Manikandan
Honored Contributor

Re: syslog.log

You should increase nfile kernel parameter in the kernel.


Thanks
Radhakrishnan Venkatara
Trusted Contributor

Re: syslog.log

check for nfile parameter


radhakrishnan
Negative thinking is a highest form of Intelligence
Bill Douglass
Esteemed Contributor

Re: syslog.log

You can do on-going monitoring of the file table from sar

sar -v 1

will show you the current size and the max limit for the process, inode and file trables in the kernel.

You can check the sa1 man oage for instructions on setting up a cron job to collect sar data on a regular basis for monitoring purposes.
Caesar_3
Esteemed Contributor

Re: syslog.log

Hello!

Increase the nfile in the kernel.

Caesar
yogesh_4
Regular Advisor

Re: syslog.log

Hi ,
Give # sar -v 5 5 and just observe the output. then start your apllication software and then give #sar -v 5 5 in nfile it will give 1288/1500 it shows that out of 1500 1288 files are being used. If limit exceeds then you have to increase "nfile" Kernal parameter.
Michael Steele_2
Honored Contributor

Re: syslog.log

As indicated increasing 'nfile' will help in correcting this problem. But it might also be necessary to identify the culprit process with all the open files; who's eating up your system file table? For this, 'lsof' works best.

lsof -p pid

This command will list all the open files associated to the PID and help you track down any runaway processes.

If you don't have it, you should, so get it here:

http://hpux.cict.fr/hppd/cgi-bin/search

Also regarding runaway processes, what does 'sar -v' report before and after a reboot? Dramatic change? Use 'lsof'.
Support Fatherhood - Stop Family Law
Donny Jekels
Respected Contributor

Re: syslog.log

increase the nfile kernel parameter

use "lsof -p pid" to find the process creating those open files

use 'sar -v' report - to find runaway process - ie. proc's owned by 1



live free or die
donny
"Vision, is the art of seeing the invisible"