topic Re: dmesg and syslog in Operating System - HP-UX

dmesg and syslog

manu_15 — Sat, 28 May 2005 21:38:01 GMT

Hi All,

Can anybody explain in detail ,what is the difference between dmesg and /var/adm/syslog/syslog.log

thanks in advance

Re: dmesg and syslog

Bill Hassell — Sat, 28 May 2005 22:13:11 GMT

dmesg reports the contents of the kernel message buffer. syslog is a general purpose logging facility and anyone can write messages to syslog (see man logger). syslog is an unrestricted file but dmesg only reports what is currently in the kernel message buffer--a small area in memory, about 50-100 lines. New messages push the oldest memories out of the buffer. There is no facility in HP-UX to monitor the message buffer so you have to create a cron job to track this buffer.

Re: dmesg and syslog

Senthil Kumar .A_1 — Sat, 28 May 2005 23:28:27 GMT

No pointers for this please..

Have pasted what i found in MAN pages..

dmesg -

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. This is
typically used with cron (see cron(1)) to produce the error log

The system error message buffer is of small, finite size. dmesg is
run only every few minutes, so there is no guarantee that all error
messages will be logged.

syslog...

This log is used by a application or daemons to report the problem they encounter.
This is done by the apps by invoking "logger" command. A entry can be added to by syslog.log by user by invoking "logger" command. It can be considered as a feature provided by UNIX system for app vendor or
programmer to log into syslog.log file.

The logger command provides a program interface to the syslog() system
log module (see syslog(3C)).

A message can be given on the command line, which is logged
immediately, or a file is read and each line is logged. If no file or
message is specified, the contents of the standard input are logged.

Regards.

Re: dmesg and syslog

manu_15 — Tue, 31 May 2005 20:23:11 GMT

Hi All..

Thanks for the replies..I have some more doubts about the same. Does hardware alerts will logged into the syslog..Also explain the normal procedure we follow for hardware related problems ( I mean checking the logs)

Thanks....

Re: dmesg and syslog

Nguyen Anh Tien — Tue, 31 May 2005 21:14:09 GMT

refer this link
http://www2.itrc.hp.com/service/james/dispDoc.do?docURL=http%3A%2F%2Fsearch.hp.com%2Fredirect.html%3Furl%3Dhttp%253A%2F%2Fforums1.itrc.hp.com%2Fservice%2Fforums%2Fquestionanswer.do%253FthreadId%253D645417%26qt%3D%2Bdmesg%2Bvs%2Bsyslog%26hit%3D3&aid=SEARCH_FORUMS&pil=3&serStr=dmesg+vs+syslog&pir=3

Re: dmesg and syslog

manu_15 — Tue, 31 May 2005 21:27:34 GMT

hi...

sorry..the above link I'm no able to open..

Re: dmesg and syslog

Bill Hassell — Tue, 31 May 2005 21:37:09 GMT

Hardware diagnostics will be logged into syslog if the online diagnostics have been installed. Type this command to see the RAM installed in your system:

echo "selclass qualifier memory;info;wait;infolog" | /usr/sbin/cstm

If you get a response that cstm was not found, you need to install the online diagnostics from your HP Support Plus CDROM.

Re: dmesg and syslog

Nguyen Anh Tien — Wed, 01 Jun 2005 02:18:40 GMT

sorry. check this:
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=645417

Re: dmesg and syslog

Senthil Kumar .A_1 — Thu, 02 Jun 2005 15:03:02 GMT

Hi manu,

i have attached a sample syslog file..
too bad ..i couldn't grep and sort it as some events spanned multiple days.. so i will not be able to present is in a fine manner.

But.. Usually.. the H/W issses reported by unix kernel(vmunix).. will be reported

date syatemname vmunix : Error

ex.. Please find more in the attachment.

Apr 3 15:15:35 unix_sys vmunix: ct_query failed. hw_path = 0/4/0/0

This doesn't go to say that , others wouldn't report H/W issues...Some daemons could report for example...for a tape drive,reported by veritas netbackup daemon.

Nov 28 11:58:19 bdhp4271 tldcd[1098]: TLD(40) key = 0x4, asc = 0x40, ascq = 0x1, HARDWARE ERROR, GENERAL..

so actually.. you need to get familiar with your system devices and daemons running.. and check how these are logged to syslog.. This
understanding will aid you in dechipering the syslog for issues in
future.

Regards.