Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!goanna.cs.rmit.edu.au!news.apana.org.au!cantor.edge.net.au!news.teragen.com.au!news.access.net.au!news.mel.connect.com.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!cpk-news-hub1.bbnplanet.com!su-news-hub1.bbnplanet.com!news.bbnplanet.com!newsxfer3.itd.umich.edu!newsxfer.itd.umich.edu!uunet!in1.uu.net!128.255.40.11!news.uiowa.edu!news From: "J. Zhu" <jyzhu@usa.net> Newsgroups: comp.unix.bsd.bsdi.misc Subject: Help: Crash with NFS server! Date: Mon, 03 Mar 1997 23:44:23 -0600 Organization: USA Inc. Lines: 66 Message-ID: <331BB6B7.1701@usa.net> NNTP-Posting-Host: black.weeg.uiowa.edu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 3.01 (Win95; I) Xref: euryale.cc.adfa.oz.au comp.unix.bsd.bsdi.misc:6186 Hi there, We have a SunOS 4.1.3_U1 computer running under the NIS environment. The machine is configured as both NFS server and client, i.e it exports some of its file systems to the network and also can access other NFS file servers. Automount and ypbind are run on it. It has two network cards, an ether card called demo-e and a FDDI card called demo. The bad thing is that the machine has kept crashing a couple of times in the last 10 days. The following messages were seen from the system console. Feb 24 16:13:16 demo vmunix: NFS server samson not responding still trying Feb 24 16:13:16 demo vmunix: NFS server samson ok Feb 24 16:13:43 demo vmunix: NFS server samson not responding still trying Feb 24 16:13:43 demo vmunix: NFS server samson ok Feb 24 16:14:29 demo vmunix: NFS server samson not responding still trying Feb 24 16:14:29 demo vmunix: NFS server samson ok Feb 24 16:14:56 demo vmunix: NFS server samson not responding still trying Feb 24 16:14:56 demo vmunix: NFS server samson ok Feb 24 16:16:43 demo vmunix: NFS server samson not responding still trying Feb 24 16:16:53 demo vmunix: NFS server atlas not responding still trying For your information, the following are the contents of /etc/mtab for demo machine: /dev/sd0a / 4.2 rw,dev=0700 1 1 /dev/sd0g /usr 4.2 rw,dev=0706 1 2 /dev/sd2g /local/demo 4.2 rw,dev=0716 1 3 /dev/sd1g /local/demo1 4.2 rw,dev=070e 1 4 demo:(pid124) /home ignore ro,intr,port=724,map=auto.home,indirect,dev=8200 0 0 demo:(pid124) /net ignore ro,intr,port=724,map=-hosts,indirect,dev=8201 0 0 demo:(pid124) /u ignore ro,intr,port=724,map=auto.u,indirect,dev=8202 0 0 demo:(pid124) /t ignore ro,intr,port=724,map=auto.t,indirect,dev=8203 0 0 demo:(pid124) /d ignore ro,intr,port=724,map=auto.d,indirect,dev=8204 0 0 atlas:/vtool/cadappl.sunos /tmp_mnt/t/cadappl_sunos nfs rw,dev=8205 0 0 samson:/local/samson1/sun.usr.local /tmp_mnt/t/sunusrlocal_samson nfs rw,dev=820 7 0 0 atlas:/vtool/cadence/9403 /tmp_mnt/t/cds9403 nfs rw,dev=8208 0 0 tapeboy:/nsr /tmp_mnt/t/networker nfs rw,soft,intr,suid,dev=820a 0 0 We have other SunOS 4.1.3_U1 machines with the same configuration as the crashed mechine. They use same NFS file systems but work just fine. Supposedly, the machine should not be down even if it has hard time to talk to NFS file servers. The machine still crashed even after we replace the ether network card with a brand new one because we first suspect the problem might be from the card. After using nfsstat and netstat commands, we found nothing wrong from the reports. Another weird thing is that the machine always crashed around 4-5pm. Checking the cron in the machine, nothing special is going between 4-5pm. Any clues and suggestion about the problem will be greatly appreciated. Johnny Emailto:jyzhu@blue.weeg.uiowa.edu