Is dmesg read "/var/adm/syslogsyslog.log"?

[xiongye_2]

when i type dmesg output is
file: table is full
file: table is full
file: table is full
file: table is full
file: table is full
file: table is full
file: table is full
file: table is full
file: table is full
file: table is full
file: table is full
file: table is full
file: table is full
I vi the file /var/adm/syslogsyslog.log
also find similar information.
What should I do ,to increase nfile parameter ?

[Scott Van Kalken]

http://docs.hp.com/hpux/onlinedocs/os/KCparams.OverviewAll.html


this document gives you an overwiev of kernel parameters and related ones.

If you need to change nfile this doc will tell you you'll also need to double check:

nrpoc maxusers npty nstrpty

[Steven Sim Kok Leong]

Hi,

First, it is important for you to verify whether this is normal (i.e. due to a normal increase of resource consumption such as more user accesses) or abnormal (i.e. an errant program or process such as one in an endless recursive loop).

To verify that, use lsof downloadable at:

http://hpux.cs.utah.edu/hppd/hpux/Sysadmin/lsof-4.61/

It will show you all the current open files on your system. nfiles is the kernel parameter identifying the limit on the number of opened files in the system. From your lsof output, check if any process(es) are opening up too many files unnecessarily.

Hope this helps. Regards.

Steven Sim Kok Leong

[Michael Tully]

As well as checking what Scott & Steven have had to say, also you may wish to look at how long this problem has been occurring. Have a look for any entries in the previous syslog (/var/adm/syslog/OLDsyslog.log)

If there are entries there as well it means your system is constantly running out of kernel resources and in which case you should plan on making the necessary changes to your system kernel.

I suggest you use 'sam' to this work unless you are confident of doing this at the command line level. If you have formulas that make up these values, 'sam' is the best way.

[Printaporn_1]

Hi,

after you fix the problem , just check that no new message not come into the syslog.
dmesg will not clear then message untill reboot.

[V. V. Ravi Kumar_1]

hi,
the following sentences are from dmesg man page.
---------------------------
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).
---------------------------

so dmesg doesn't look into /var/adm/syslog/syslog.log. it only takes recent alerts/errors from buffer. once reboot dmesg will not display the same messages. but u can find those in syslog.log.

through SAM u can increse the nfile, but before doing so ensure that it is because u have fallen short nfile. because sometimes it may be due to any process fallen in loop and generating large number of forks. use lsof to identify such files.

regds
ravi

[Uli Manschke]

Hi,

as far as I remember: the kernel messages are not automatically written to syslog.log, but you can have cron execute

dmesg - >> /var/adm/syslog/syslog.log
(or any other filename)

every now and then to add new messages to the file.

dmesg reads the FIFO kernel message buffer which has limited size and is used in case of kernel messages which cannot be sent to any responsible process or things like panic's etc.
Regards
uli

[MANOJ SRIVASTAVA]

to increase the parameterr you have to go to Sam--->Kernel Configuration--->Configurable Parameters ----> click on nfile and increase it , the new value should atleast be like 1.2 time sof the curretn value , then you can do a sar -v 2 10 and run this fromm the cron to collect data as to wether this get filled or not.

You may also like to look at :

http://docs.hp.com/hpux/onlinedocs/os/KCparams.OverviewAll.html


Manoj Srivastava