From owner-freebsd-questions Wed Apr 8 21:37:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA16836 for freebsd-questions-outgoing; Wed, 8 Apr 1998 21:37:12 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from fciencias.ens.uabc.mx ([148.231.177.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA16828 for ; Wed, 8 Apr 1998 21:37:07 -0700 (PDT) (envelope-from mbarbosa@fciencias.ens.uabc.mx) Received: (from mbarbosa@localhost) by fciencias.ens.uabc.mx (8.8.7/8.8.7) id VAA00228; Wed, 8 Apr 1998 21:39:43 -0700 (PDT) (envelope-from mbarbosa) From: "Marco A. Barbosa S." Message-Id: <199804090439.VAA00228@fciencias.ens.uabc.mx> Subject: Re: nis/nfs problem (continued...) In-Reply-To: from Doug White at "Apr 8, 98 00:05:22 am" To: dwhite@resnet.uoregon.edu Date: Wed, 8 Apr 1998 21:39:42 -0700 (PDT) Cc: freebsd-questions@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Tue, 7 Apr 1998, Marco A. Barbosa S. wrote: > > > >> network segment on LAN (novell netware,ethernet,thin coax ) > > >> is ok, but Xcalibur gets stuck. If someone is logged in > > >> Fciencias, they still have net access to everywhere, > > >> but Xcalibur gets isolated. Any user in Fciencias, loses > > >> files and noone else can login due to nis/dns failure. > > > > > >Why does Xcalibur get stuck? How? Please be more specific. Can you ping > > >it? Can you connect out OK from xcalibur? > > > > sorry, I had specified all of that in an earlier mail... (try 1) but > > I kinda sent it to the owner I think... *chuckle* that is what the > > previous "ooops" was about... > > > > > > ok... stuck, as in... no more Xcalibur, noone on the network > > can connect to it... it does not exist... well, some times > > if you leave a telnet long enough to it, after 3 + minutes > > it gives you the ^] thing to tell you you can disconnect with > > it.. but nothing more... > > Okay, we've established that you can't contact Xcalibur when it goes brain > dead. Now, can Xcalibur connect to anyone during this period, ie if > you're sitting at the console can you ping/telnet anywhere? nope, I thought I had specified that... *smile* xcalibur gets isolated from the inside out and from the outside in... > > > >Either xcalibur is going south or your network is going south. Hangups > > >on the client sound like a loss of NIS connecivity, and a later > > >reconnection. You should get log entries when the NIS connection is lost > > >and regained. > > > > South? what do you mean south? > > It's an expression meaning that it stopped working -- it went on vacation, > probably to a warm vacation spot south of us :) well, I am in Baja, south of San Diego, I think it is already in a warm spot, kinda not wanting to work but most of the time working.. > > > Mar 26 20:13:25 Fciencias su: mbarbosa to root on /dev/ttyp3 > > Mar 26 20:24:26 Fciencias ypbind[100]: NIS server [148.231.177.8] for domain "RED_FC" not responding > > Mar 26 20:24:31 Fciencias routed[70]: interface ed1 to 148.231.177.14 broken: in=1 ierr=0 out=1 oerr=2 > > Routed notices. yep... lots of them... want some more? > > Mar 26 20:28:27 Fciencias /kernel: nfs server xcalibur:/usr/usuarios: not responding > > Hm, nfs notices that it goes away too. yep, everything takes a break > > > >Perhaps a daemon is going nuts? Check top. > > > > yes, that is my latest guess... otherwise, it would not have been > > fixed with the -HUPing... any ideas? btw, I am kinda in spring > > break.. *chuckle* else I would have replied sooner... sorry. > > No, actually, HUPping everything may fix it since it encourages the server > to dump all outstanding connections and reinitialize itself. Or it's some > very simple server that HUPping kills completely. well, I thought the hupping kinda forced the actual daemon to kinda reload the config files again but without dropping the stuff it was doing... you know... kinda restarting with what it already has, that is why I call it "warm-jump-start" *smile* then again, I can be wrong... > > What type of NIC is in Xcalibur, and what type of network is it connected > to? hmmm NIC... I think d-link combo thingie... and the same network as Fciencias, thin coax cable, netware, ethernet cards, hmmm main gateway is a novell box... want stats? let me check messages... Mar 10 12:52:34 Xcalibur /kernel: The Regents of the University of California. All rights reserved. Mar 10 12:52:34 Xcalibur /kernel: Mar 10 12:52:34 Xcalibur /kernel: FreeBSD 2.2.5-RELEASE #0: Tue Oct 21 14:33:00 GMT 1997 Mar 10 12:52:34 Xcalibur /kernel: jkh@time.cdrom.com:/usr/src/sys/compile/GENERIC Mar 10 12:52:34 Xcalibur /kernel: CPU: Pentium (119.75-MHz 586-class CPU) Mar 10 12:52:34 Xcalibur /kernel: Origin = "GenuineIntel" Id = 0x52c Stepping=12 Mar 10 12:52:34 Xcalibur /kernel: Features=0x1bf Mar 10 12:52:34 Xcalibur /kernel: real memory = 33554432 (32768K bytes) Mar 10 12:52:34 Xcalibur /kernel: avail memory = 30244864 (29536K bytes) Mar 10 12:52:34 Xcalibur /kernel: Probing for devices on PCI bus 0: Mar 10 12:52:34 Xcalibur /kernel: chip0 rev 2 on pci0:0 Mar 10 12:52:34 Xcalibur /kernel: chip1 rev 1 on pci0:7:0 Mar 10 12:52:34 Xcalibur /kernel: chip2 rev 0 on pci0:7:1 Mar 10 12:52:34 Xcalibur /kernel: vga0 rev 16 int a irq ?? on pci0:9 Mar 10 12:52:34 Xcalibur /kernel: Probing for devices on the ISA bus: Mar 10 12:52:34 Xcalibur /kernel: sc0 at 0x60-0x6f irq 1 on motherboard Mar 10 12:52:34 Xcalibur /kernel: sc0: VGA color <16 virtual consoles, flags=0x0> Mar 10 12:52:34 Xcalibur /kernel: ed0 at 0x300-0x31f irq 11 on isa Mar 10 12:52:34 Xcalibur /kernel: ed0: address 00:80:c8:35:16:03, type NE2000 (16 bit) Mar 10 12:52:35 Xcalibur /kernel: sio0 at 0x3f8-0x3ff irq 4 on isa Mar 10 12:52:35 Xcalibur /kernel: sio0: type 16550A Mar 10 12:52:35 Xcalibur /kernel: sio1 at 0x2f8-0x2ff irq 3 on isa Mar 10 12:52:35 Xcalibur /kernel: sio1: type 16550A Mar 10 12:52:35 Xcalibur /kernel: lpt0 at 0x378-0x37f irq 7 on isa Mar 10 12:52:35 Xcalibur /kernel: lpt0: Interrupt-driven port Mar 10 12:52:35 Xcalibur /kernel: lp0: TCP/IP capable interface Mar 10 12:52:35 Xcalibur /kernel: mse0 not found at 0x23c Mar 10 12:52:35 Xcalibur /kernel: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa Mar 10 12:52:35 Xcalibur /kernel: fd0: 1.44MB 3.5in Mar 10 12:52:35 Xcalibur /kernel: wdc0 at 0x1f0-0x1f7 irq 14 on isa Mar 10 12:52:35 Xcalibur /kernel: wdc0: unit 0 (wd0): Mar 10 12:52:35 Xcalibur /kernel: wd0: 4104MB (8406720 sectors), 8896 cyls, 15 heads, 63 S/T, 512 B/S Mar 10 12:52:35 Xcalibur /kernel: wdc0: unit 1 (atapi): , removable, accel, dma, iordis Mar 10 12:52:35 Xcalibur /kernel: wcd0: 171/1367Kb/sec, 128Kb cache, audio play, 255 volume levels, ejectable tray Mar 10 12:52:35 Xcalibur /kernel: wcd0: no disc inside, unlocked, lock protected Mar 10 12:52:35 Xcalibur /kernel: matcdc0 not found at 0x230 Mar 10 12:52:35 Xcalibur /kernel: npx0 flags 0x1 on motherboard Mar 10 12:52:35 Xcalibur /kernel: npx0: INT 16 interface Mar 10 19:05:41 Xcalibur shutdown: reboot by root: bye bye... got any info? or want more config files? just ask... > > Doug White | University of Oregon > Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant > http://gladstone.uoregon.edu/~dwhite | Computer Science Major > > > -- ************************************* * Marco Antonio Barbosa Santoyo * * Facultad de Ciencias, U.A.B.C. * * Ensenada, Baja California, Mexico * ************************************* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message