Path: utzoo!utgpu!cunews!bnrgate!brtph3!brchh104!brchs1!bnr.ca!rice!sun-spots-request
From: giacobbe@pilot.njin.net (Jeff Giacobbe)
Newsgroups: comp.sys.sun
Subject: 4/330 server problems
Keywords: Miscellaneous
Message-ID: <252@brchh104.bnr.ca>
Date: 16 Nov 90 12:05:00 GMT
Sender: news@brchh104.bnr.ca
Organization: Sun-Spots
Lines: 22
Approved: Sun-Spots@rice.edu
X-Original-Date: 26 Oct 90 13:58:03 GMT
X-Sun-Spots-Digest: Volume 9, Issue 362, message 10
X-Note: Submissions: sun-spots@rice.edu, Admin: sun-spots-request@rice.edu

I've been having some strange, intermittent problems with our Sun 4/330
server recently.  We are running 4.0.3 and are currently (trying) to
support 4 diskless 3/80's and 10 diskless SLC's.

The 3/80's have worked fine since day one.  The problems have sprung up
around the 10 new SLC's and our new 669meg external storage unit.
Occasionally, when using the setup_client script, the server would
magically reboot itself...what fun!  Also, when trying to boot an SLC
client that I had just created using setup_client, it sometimes gets all
the way to the end of the boot process (..starting network daemons...) and
mysteriously hangs.  When I try to see whats wrong on the server end, all
the nfs daemons are dead!  Sometimes the server is so bad, the keyboard is
completely locked at a rebbot is my only option!

Has anyone else had problems supporting SLC clients with 4.0.3?  Any ideas
on why booting a new SLC client would trash the server's nfs daemons?

Any and all comments/ideas/suggestions would be greatly appreciated!

@xxxxx{==============-    giacobbe@pilot.njin.net    -==============}xxxxx@
|                                   or 					  |
|                      giacobbe@apollo.montclair.edu                      |