Several people wrote that a stop/restart of syslogd will cause previous
error messages to appear. I do know the initial reason this error message
appeared but was concerned that this message appeared again.
(FWIW, this happened due to a user attempting to use lynx to snarf a 600M
file. lynx wants to save a temp file in /tmp and then copy/move it to a
specified name/directory. However /tmp didn't have that much free space.)
Many thanks to all who responded:
Unixboy@aol.com
Arthur Darren Dunham <add@netcom.com>
"DAVID,Anthony" <Anthony.DAVID@dewrsb.gov.au>
Duncan Phillips <dphillip@halfdome.acs.uci.edu>
Dan Penrod <dan@nortom.com>
Darren Evans-Young <darren@bama.ua.edu>
-- James
-----------------------------------------------------
"One World, One Web, One Program" -> Microsoft Promotional Ad
"Ein Volk, Ein Reich, Ein Fuhrer" -> Adolf Hitler
========
From: Unixboy@aol.com
hey guy....This is a very misleading message. What has happened is
this...Syslog maintains a buffer that was written out when you
stopped/started syslogd. The information maintained here is what is
written out when dmesg is executed. This so misleading...I wish SUN would
fix it...In the meantime we have to read carefully...
Don't worry at all
========
From: Arthur Darren Dunham <add@netcom.com>
When syslog starts, it dumps the kernel message buffer to the messages
file. You should find a very similar copy of the above earlier in your
messages file, with a different time stamp. It'll dump it every time you
start syslog.
========
From: Duncan Phillips <dphillip@halfdome.acs.uci.edu>
It might be something left from the system buffer that gets read each
time syslogd starts and stuffed into /var/adm/messages. It's probably
been in the system buffer since your reboot (crash?).
========
Initial question:
>I am seeing the following in my message log. Is this a drive potentially
>going bad or something else - perhaps a process spazzing? The machine has
>been up for 15 days with no problems (that I can tell) - this appeared
>after issueing "/etc/init.d/syslog stop;/etc/init.d/syslog start".
>
>Will summarize - tia.
>
>-- james
>
>(snip)
>
>Apr 30 22:28:07 ns1 unix: SUNW,hme0: CheerIO 2.0 (Rev Id = c1) Found
>Apr 30 22:28:07 ns1 unix: SUNW,hme0 is /pci@1f,0/pci@1,1/network@1,1
>Apr 30 22:28:07 ns1 unix: dump on /dev/dsk/c0t0d0s4 size 262208K
>Apr 30 22:28:07 ns1 unix: SUNW,hme0: Using Internal Transceiver
>Apr 30 22:28:07 ns1 unix: SUNW,hme0: 100 Mbps full-duplex Link Up
>Apr 30 22:28:07 ns1 unix: pci9004,81780 is /pci@1f,0/pci@1/scsi@1
>Apr 30 22:28:07 ns1 last message repeated 1 time
>Apr 30 22:28:07 ns1 unix: sd0 at pci9004,81780: target 0 lun 0
>Apr 30 22:28:07 ns1 unix: sd0 is /pci@1f,0/pci@1/scsi@1/sd@0,0
>Apr 30 22:28:07 ns1 unix: <QUANTUM-VIKING4.5WSE-880R cyl 5148 alt 2 hd 8
> sec 216>
>Apr 30 22:28:07 ns1 unix: panic[cpu0]/thread=0x3001fe80: zero
>Apr 30 22:28:07 ns1 unix: syncing file systems... 1752 1712 1712 1712 1712
> 1712 1712 1712 1712 1712 1712 1712 1712 1712 1712 1712 1712 1712 1712
> 1712 1712 1712 1712 1712 1712 1712 1712 1712 1712 1712 cannot sync --
> giving up
>Apr 30 22:28:07 ns1 unix: 2546 static and sysmap kernel pages
>Apr 30 22:28:07 ns1 unix: 37 dynamic kernel data pages
>Apr 30 22:28:07 ns1 unix: 99 kernel-pageable pages
>Apr 30 22:28:07 ns1 unix: su1 at ebus0: offset 14,3062f8
>Apr 30 22:28:07 ns1 unix: su1 is /pci@1f,0/pci@1,1/ebus@1/su@14,3062f8
>
>
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:14:07 CDT