• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2289
  • Last Modified:

Sun Enterprise 250 - need help reviewing messages log - Solaris Newbie

Hello all,

 I need some assistance with reading the following bootup information from my development SUN Enterprise 250 server.  I'm already aware of the bad fan, is there anything else I should be concerned about (or look into it).

--------------------------------------------------------------------------------------------------------------------------------------------
Jun  1 08:42:48 NONAMEunix: ^MSunOS Release 5.7 Version Generic_106541-23 64-bit [UNIX(R) System V Release 4.0]
Jun  1 08:42:48 NONAMEunix: Copyright (c) 1983-1999, Sun Microsystems, Inc.
Jun  1 08:42:48 NONAMEunix: Ethernet address = 8:0:20:b0:39:34
Jun  1 08:42:48 NONAMEunix: mem = 524288K (0x20000000)
Jun  1 08:42:48 NONAMEunix: avail mem = 510050304
Jun  1 08:42:48 NONAMEunix: root nexus = Sun (TM) Enterprise 250 (2 X UltraSPARC-II 248MHz)
Jun  1 08:42:48 NONAMEunix: pci0 at root: UPA 0x1f 0x4000
Jun  1 08:42:48 NONAMEunix: pci0 is /pci@1f,4000
Jun  1 08:42:48 NONAMEunix: /pci@1f,4000/scsi@3 (glm0):
Jun  1 08:42:48 NONAME Rev. 5 Symbios 53c875 found.
Jun  1 08:42:48 NONAMEunix: /pci@1f,4000/scsi@3 (glm0):
Jun  1 08:42:48 NONAME target1-scsi-options=0x5f8
Jun  1 08:42:48 NONAMEunix: /pci@1f,4000/scsi@3 (glm0):
Jun  1 08:42:48 NONAME target2-scsi-options=0x5f8
Jun  1 08:42:48 NONAMEunix: /pci@1f,4000/scsi@3 (glm0):
Jun  1 08:42:48 NONAME target3-scsi-options=0x5f8
Jun  1 08:42:48 NONAMEunix: /pci@1f,4000/scsi@3 (glm0):
Jun  1 08:42:48 NONAME target4-scsi-options=0x5f8
Jun  1 08:42:48 NONAMEunix: /pci@1f,4000/scsi@3 (glm0):
Jun  1 08:42:48 NONAME target5-scsi-options=0x5f8
Jun  1 08:42:48 NONAMEunix: /pci@1f,4000/scsi@3 (glm0):
Jun  1 08:42:48 NONAME target6-scsi-options=0x5f8
Jun  1 08:42:48 NONAMEunix: PCI-device: scsi@3, glm0
Jun  1 08:42:48 NONAMEunix: glm0 is /pci@1f,4000/scsi@3
Jun  1 08:42:48 NONAMEunix: /pci@1f,4000/scsi@3,1 (glm1):
Jun  1 08:42:48 NONAME Rev. 5 Symbios 53c875 found.
Jun  1 08:42:48 NONAMEunix: PCI-device: scsi@3,1, glm1
Jun  1 08:42:48 NONAMEunix: glm1 is /pci@1f,4000/scsi@3,1
Jun  1 08:42:48 NONAMEunix: sd0 at glm0:
Jun  1 08:42:48 NONAMEunix:  target 0 lun 0
Jun  1 08:42:48 NONAMEunix: sd0 is /pci@1f,4000/scsi@3/sd@0,0
Jun  1 08:42:48 NONAMEunix:    <SUN18G cyl 7506 alt 2 hd 19 sec 248>
Jun  1 08:42:49 NONAMEunix: sd6 at glm0:
Jun  1 08:42:49 NONAMEunix:  target 6 lun 0
Jun  1 08:42:49 NONAMEunix: sd6 is /pci@1f,4000/scsi@3/sd@6,0
Jun  1 08:42:49 NONAMEunix: sd7 at glm0:
Jun  1 08:42:49 NONAMEunix:  target 8 lun 0
Jun  1 08:42:49 NONAMEunix: sd7 is /pci@1f,4000/scsi@3/sd@8,0
Jun  1 08:42:49 NONAMEunix:    <SUN18G cyl 7506 alt 2 hd 19 sec 248>
Jun  1 08:42:56 NONAMEunix: root on /pseudo/md@0:0,0,blk fstype ufs
Jun  1 08:42:56 NONAMEunix: WARNING: forceload of misc/md_trans failed
Jun  1 08:42:56 NONAMEunix: WARNING: forceload of misc/md_raid failed
Jun  1 08:42:56 NONAMEunix: WARNING: forceload of misc/md_hotspares failed
Jun  1 08:42:56 NONAMEunix: pci1 at root: UPA 0x1f 0x2000
Jun  1 08:42:56 NONAMEunix: pci1 is /pci@1f,2000
Jun  1 08:42:57 NONAMEunix: PCI-device: ebus@1, ebus0
Jun  1 08:42:57 NONAMEunix: WARNING: Fan failure has been detected
Jun  1 08:42:57 NONAMEunix: envctrltwo0 at ebus0: offset 14,600000
Jun  1 08:42:57 NONAMEunix: envctrltwo0 is /pci@1f,4000/ebus@1/SUNW,envctrltwo@14,600000
Jun  1 08:42:59 NONAMEunix: su0 at ebus0: offset 14,3083f8
Jun  1 08:42:59 NONAMEunix: su0 is /pci@1f,4000/ebus@1/su@14,3083f8
Jun  1 08:42:59 NONAMEunix: su1 at ebus0: offset 14,3062f8
Jun  1 08:42:59 NONAMEunix: su1 is /pci@1f,4000/ebus@1/su@14,3062f8
Jun  1 08:42:59 NONAMEunix: keyboard is </pci@1f,4000/ebus@1/su@14,3083f8> major <37> minor <0>
Jun  1 08:42:59 NONAMEunix: mouse is </pci@1f,4000/ebus@1/su@14,3062f8> major <37> minor <1>
Jun  1 08:42:59 NONAMEunix: stdin is </pci@1f,4000/ebus@1/su@14,3083f8> major <37> minor <0>
Jun  1 08:42:59 NONAMEunix: se0 at ebus0: offset 14,400000
Jun  1 08:42:59 NONAMEunix: se0 is /pci@1f,4000/ebus@1/se@14,400000
Jun  1 08:42:59 NONAMEunix: se1 at ebus0: offset 14,200000
Jun  1 08:42:59 NONAMEunix: se1 is /pci@1f,4000/ebus@1/se@14,200000
Jun  1 08:42:59 NONAMEunix: stdout is </pci@1f,4000/ebus@1/se@14,400000:a> major <20> minor <0>
Jun  1 08:43:00 NONAMEunix: cpu0: SUNW,UltraSPARC-II (upaid 0 impl 0x11 ver 0x20 clock 248 MHz)
Jun  1 08:43:00 NONAMEunix: cpu1: SUNW,UltraSPARC-II (upaid 1 impl 0x11 ver 0x20 clock 248 MHz)
Jun  1 08:43:00 NONAMEunix: cpu 1 initialization complete - online
Jun  1 08:43:04 NONAMEunix: SUNW,hme0: CheerIO 2.0 (Rev Id = c1) Found
Jun  1 08:43:04 NONAMEunix: PCI-device: network@1,1, hme0
Jun  1 08:43:04 NONAMEunix: hme0 is /pci@1f,4000/network@1,1
Jun  1 08:43:07 NONAMEunix: SUNW,hme0: Using Internal Transceiver
Jun  1 08:43:07 NONAMEunix: SUNW,hme0: 100 Mbps full-duplex Link Up
Jun  1 08:43:58 NONAMEunix: dump on /dev/md/dsk/d5 size 4097 MB
Jun  1 08:49:54 NONAMEntpd[230]: ntpd 4.0.72j Sat Oct 24 00:48:19 EDT 1998 (1)
Jun  1 08:49:55 NONAMEntpd[230]: using kernel phase-lock loop 0041
Jun  1 08:49:58 NONAMEunix: pseudo-device: pm0
Jun  1 08:49:58 NONAMEunix: pm0 is /pseudo/pm@0
Jun  1 08:49:58 NONAMEsyslog: /usr/sbin/pmconfig: /etc/power.conf line (31) failed to convert mount point /dev/md/dsk/d0 to prom name
Jun  1 08:49:58 NONAMEunix: pseudo-device: tod0
Jun  1 08:49:58 NONAMEunix: tod0 is /pseudo/tod@0
Jun  1 08:50:19 NONAMEsendmail[291]: k51Co1f00291: Losing ./qfk51Co1f00291: savemail panic
Jun  1 08:50:19 NONAMEsendmail[291]: k51Co1f00291: SYSERR(root): savemail: cannot save rejected email anywhere
Jun  1 08:51:02 NONAMEunix: pseudo-device: vol0
Jun  1 08:51:02 NONAMEunix: vol0 is /pseudo/vol@0
Jun  1 08:51:04 NONAMEunix: fd0 at ebus0: offset 14,3023f0
Jun  1 08:51:04 NONAMEunix: fd0 is /pci@1f,4000/ebus@1/fdthree@14,3023f0
Jun  1 08:51:25 NONAMEnmbd[477]: [2006/06/01 08:51:25, 0] nmbd/nmbd_responserecordsdb.c:(235)
Jun  1 08:51:25 NONAMEnmbd[477]:   find_response_record: response packet id 27670 received with no matching record.

------------------------------------------------------------------------------------------------------------------------------------------

TIA!
0
CeLLuS
Asked:
CeLLuS
  • 3
  • 2
  • 2
  • +3
2 Solutions
 
arthurjbCommented:
There are no fatal errors that I can see at a glance. (except the fan)

Are there any symptoms, or are you just curious about the messages?
0
 
PsiCopCommented:
Well, it looks like sendmail is not properly configured.
0
 
CeLLuSAuthor Commented:
Actually - This server crashed last night and I need to figure out what may have caused it.  according to my networking monitoring software (Whats up Gold) this system became unresponsive around 1AM.  It runs Telnet, SSH and apache services.   I searched the messages log but was unable to find anything around the time it crashed.  So all I have it this.  Are there any diagnostics I can run that my give me info on the health of this box?


Any maintenance tips for old sun Solaris boxes would be very much appreciated.

TIA!
0
Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
yuzhCommented:
You can use prtdiag (commandline command to check it out), type in:

/usr/platform/`uname -m`/sbin/prtdiag

the boot up message looks ok, you need to have a look check /var/adm/message* files for any error message before the reboot time
Jun  1 08:42:48

or
who -b
0
 
zzzztjCommented:
are you sure it's not run out of disk space? usually thats the only thing that will make a normally operational and stable box do what you suggest.

It's always a good idea to have /var as a seperate partition so that when it gets full it doesn't screw the root disk.

It was the entries in your log

Jun  1 08:42:56 NONAMEunix: WARNING: forceload of misc/md_trans failed
Jun  1 08:42:56 NONAMEunix: WARNING: forceload of misc/md_raid failed
Jun  1 08:42:56 NONAMEunix: WARNING: forceload of misc/md_hotspares failed

md and hotspares are both terms to do with solstice disk manager - md - mirrored disk (volume group in other peoples worlds) and hot spares are used to replace failed mirrored slices

also

Jun  1 08:50:19 NONAMEsendmail[291]: k51Co1f00291: Losing ./qfk51Co1f00291: savemail panic
Jun  1 08:50:19 NONAMEsendmail[291]: k51Co1f00291: SYSERR(root): savemail: cannot save rejected email anywhere

Suggests a disk space problem

but


Jun  1 08:49:58 NONAMEsyslog: /usr/sbin/pmconfig: /etc/power.conf line (31) failed to convert mount point /dev/md/dsk/d0 to prom name

is a stange one to me, but again it's suggesting it can't access a mirrored disk.

If you tink this is relevent post the output of

#metastat

and

#format

0
 
arthurjbCommented:
zzzztj has a good point.  take a look at the output from the command;

 df -lk

See if any of the disks are full or in the 90% range.  It is possible that you had a disk full condition, and that rebooting cleared the problem.  It is likely to occur again if the disk sizes are too smal.

0
 
geotigerCommented:

The messages that you posted were between 08:42:48  and 08:51:25. They might not relate to what had caused your server crash at 1:00 am time. Do you have any log records around 1 am?


0
 
yuzhCommented:
>>Jun  1 08:42:56 NONAMEunix: WARNING: forceload of misc/md_trans failed
Jun  1 08:42:56 NONAMEunix: WARNING: forceload of misc/md_raid failed
Jun  1 08:42:56 NONAMEunix: WARNING: forceload of misc/md_hotspares failed

Thet are harmless errormessages from the drivers trying to be loaded even though there are no devices that will use them.

You can do:
metainit hsp001

and it will supress the message about hotspares.



0
 
CeLLuSAuthor Commented:
I ran  df -k and I get this:

Filesystem                 kbytes             used            avail           capacity       Mounted on
/proc                         0                    0                 0                0%              /proc
/dev/md/dsk/d0          4131866         2989744      1100804       74%            /
fd                              0                   0                  0                0%               /dev/fd
swap                         4352472        88                4352384      1%                /tmp
/dev/md/dsk/d8          9147129        8827214       228444        98%              /b01
/b01/s/home/jdoe      9147129         8827214       228444        98%              /home/jdoe

It looks like we do have /dev/md/dsk/d8 almost full.  Correct me if I'm wrong but since this partition doesn't contain any system files does would it have caused the crash?  By the way why would the partitions on this server only show as /dev/md/dsk/d0 & d8 instead of something like /dev/rdsk/c0t2d0s2 etc.  
0
 
arthurjbCommented:
>why would the partitions on this server only show as /dev/md/dsk/d0

This is good!  It means that whoever setup the machine understood disksuite, and raided or mirrored the disks.  (You can't tell from the device name if it is a mirror or a raid 5)
You can type;
metastat
and it will show the status of the underlying disks.  you should pipe it into more since it will scroll off the screen pretty fast.

I believe that /b01 and /home/jdoe are the same partition.  Do a df -lk and it will show only local disks...

You are correct that it is not likely that the filling of a non system partition would cause a crash.  But since the system doesn't have /var as a seperate partition, it is possible that if a process filled  /b01 then started dumping error messages, it could fill up / causing the crash.

I would work to get /b01 down below 85%.

Good Luck
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: CompTIA Healthcare IT Tech

This course will help prep you to earn the CompTIA Healthcare IT Technician certification showing that you have the knowledge and skills needed to succeed in installing, managing, and troubleshooting IT systems in medical and clinical settings.

  • 3
  • 2
  • 2
  • +3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now