nfs problems: can't find request slot
I have a shared /home directory under two machines: a box called strago, running OpenBSD 2.7, and a box called shadow, running woody. /home is an entire harddisk on strago, mounted on shadow through NFS. The line I use in fstab to mount /home is: strago:/home /home nfs rsize=8192,wsize=8192,timeo=14,intr Lately, the nfs connection to strago has been dying, for unknown reasons, causing shadow to crash hard. (No ctrl-alt-del, Magic SysRq Key, or any of that will work, nor can I telnet/ssh in from another host and reboot from there.) This has been happening more and more frequently, to the point that it has now occurred 5 times today. Sometimes, if I can tell that the NFS connection has died, I can quickly umount /home as root and remount it again, at which point everything ends up working fine, with no crashes or anything. The error messages I get (as logged in /var/log/messages) are as follows: Nov 11 19:12:46 shadow kernel: nfs: server strago not responding, still trying Nov 11 19:13:01 shadow kernel: nfs: task 4940 can't get a request slot Nov 11 19:13:02 shadow kernel: nfs: task 4954 can't get a request slot Nov 11 19:13:09 shadow kernel: nfs: task 4955 can't get a request slot Nov 11 19:14:47 shadow kernel: nfs: task 4956 can't get a request slot It's not a (physical) connection problem between the two machines (at least as far as I can tell) ... status LEDs on both NICs still blink, and the connection will work fine after the Debian box has been rebooted or if I can quickly umount remount /home. On the OpenBSD end, I was running nfsd with the options -tun 4 (which means serve tcp and udp clients, with 4 servers. By advisory of the OpedBSD mailing list, I pumped the # of servers up to 16, but the problems persist. The machine isn't being used to export NFS to anywhere else, so 16 servers should be more than enough for my needs (right?) Anyone have any ideas on what's going wrong, and what I can try to fix it? Thanks a lot, folks. - Colin McMillen
Re: What is SIOCSIFFLAGS, and when will he be back?
I have a Linksys LNE100TX, also tulip driver, and get the same error if I reboot from Windows into Linux. Problem is fixed if I start Linux from a cold boot as opposed to restarting from windows. Have you tried this? - Colin McMillen On Sun, Jul 16, 2000 at 03:36:24PM -0700, Raymond L. Zarling wrote: Linux has stopped talking to my ethernet card (Kingston KNE100TX, tulip driver). The probem seems to be in ifconfig, which reports: SIOCSIFFLAGS: Resource temporarily unavailable I run a dual boot system, and it works fine from Windoze 98. It used to run, some weeks ago, in Linux too, but I neglected Linux for a few weeks, and when I tried it now again--this! I honestly don't remember changing anything in the interim; I certainly haven't opened the computer case. Since I don't know what SIOCSIFFLAGS are, I'm completely stumped about where to look next. Short of clearing the disk and reinstalling everything, but that's one of the things I was hoping Linux would save me from. As shown below, the tulip driver doesn't seem to be complaining, and ifconfig has all the right IP addresses and routes. Any ideas what's going on here? Thanks! --Ray [EMAIL PROTECTED] ** dmesg ** Linux version 2.2.12 ([EMAIL PROTECTED]) (gcc version 2.7.2.3) #2 Thu Aug 26 11:46:26 PDT 1999 ... tulip.c:v0.91g 7/16/99 [EMAIL PROTECTED] eth0: Digital DS21143 Tulip rev 65 at 0x6100, 00:C0:F0:3B:F7:91, IRQ 0. eth0: EEPROM default media type Autosense. eth0: Index #0 - Media MII (#11) described by a 21142 MII PHY (3) block. eth0: MII transceiver #1 config 3000 status 7829 advertising 01e1. ** ifconfig -a ** eth0 Link encap:Ethernet HWaddr 00:C0:F0:3B:F7:91 inet addr:192.168.1.13 Bcast:192.168.1.255 Mask:255.255.255.0 BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 Base address:0x6100 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:3924 Metric:1 RX packets:8 errors:0 dropped:0 overruns:0 frame:0 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 ** lsmod ** Module Size Used by nls_cp437 3548 1 (autoclean) tulip 29060 0 (unused) serial 18412 1 parport 6600 0 (unused) vfat8972 1 umsdos 22768 0 (unused) -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null -- 1. Start Also Sprach Zarathustra by Richard Strauss on your CD player. 2. At the climax of the Sunrise section -- just before the cymbal crash on the C-major chord -- try to ping the first machine by IP address. 3. If it works... congratulations! Your intranet is now up and running. - From _The Linux Network_, Fred Butzen Christopher Hilton
Problems with fetchmail.. can anyone help?
I am trying to get my mail from a remote server rather than through Netscape Mail. I have the fetchmail package installed, but it can't seem to get mail from my server. Can someone point out what I am doing wrong? (The username and mail server are correct, by the way)... [EMAIL PROTECTED] ~] fetchmail -u mcmi0037 mcmi0037.email.umn.edu Enter password for [EMAIL PROTECTED]: fetchmail: No mail for mcmi0037 at mcmi0037.email.umn.edu [EMAIL PROTECTED] ~] fetchmail -u mcmi0037 mcmi0037.email.umn.edu Enter password for [EMAIL PROTECTED]: fetchmail: No mail for mcmi0037 at mcmi0037.email.umn.edu [EMAIL PROTECTED] ~] fetchmail -u mcmi0037 mcmi0037.email.umn.edu Enter password for [EMAIL PROTECTED]: 1 message for mcmi0037 at mcmi0037.email.umn.edu (645 octets). reading message 1 of 1 (638 header octets) fetchmail: SMTP listener doesn't like recipient address [EMAIL PROTECTED]' fetchmail: can't even send to shadow! fetchmail: SMTP transaction error while fetching from mcmi0037.email.umn.edu fetchmail: Query status=10 Thanks in advance for any help... Colin McMillen -- Debian GNU/Linux 2.1: 1 day, 13 hours, 35 minutes without a reboot... The revolution will be complete when the operating system is perfect. (www.debian.org, www.enlightenment.org, www.opensource.org)
Re: New Gateway computer.. can I install Debian on it?
Okay, I found out that the latest 2.3 kernels have preliminary ATA/66 support, and I'm willing to give it a shot. Now I'd like someone to help me make my own custom bootdisk... should I just download the source, compile the kernel locally, and copy the image over to a standard Debian slink bootdisk? And, if so, how do do I make the new kernel NOT install itself on my hard drive? (I will copy /boot and vmlinuz first, of course, but i'd like it if i could configure it to install straght to the bootdisk, of course...) Any tips from anyone? Colin McMillen Alec Smith wrote: My guess is that she's got one of the Promise Ultra ATA/66 controllers which the kernel (2.0.36) on the boot disks has no clue about. Currently Ultra ATA/66 support is under development, so I'd expect it very soon in 2.2/2.3 kernel versions. As a work-around, you may try connecting her HD to the motherboard EIDE controller, then enabling the drive in the BIOS. Be sure to use a standard IDE cable as the Ultra ATA/66 wire is a different design. It is my understanding that you can plug an ATA/66 drive into an ATA/33 socket (motherboard) with no side effects other than the drive acting a little slower. Alec -- Debian GNU/Linux 2.1: 2 hours, 0 minutes without a reboot... The revolution will be complete when the operating system is perfect. (www.debian.org, www.enlightenment.org, www.opensource.org)
New Gateway computer.. can I install Debian on it?
An acquaintance of mine has a new Gateway P3-450 computer with a 12 GB hard drive. She wants to use about half that space for Linux, and I recommended to her that she get slink, because I use it myself and am fairly familiar with it. However, when I tried to install from the slink CD's, I got an error about Could not find a valid disk to install to. It seems that slink (and also RedHat 5.2) can't detect her hard drive! I investigated further (it's not a partitioning problem, BTW.. fips worked fine, and i even tried downloading a windows program to make ext2 filesystems and rebooting again, with no luck..) I eventually found out that in her BIOS, under Primary Master, is listed [None]. I can change [None] to [Auto] but that doesn't help. The only device on there at all is Secondary master, which is her DVD-ROM drive (which debian can read perfectly fine.) Any ideas on what I can/should do to get the Debian install program to recognize her hard drive and start installation? Your help is much appreciated thanks! Colin McMillen -- Debian GNU/Linux 2.1: 5 hours, 34 minutes without a reboot... The revolution will be complete when the operating system is perfect. (www.debian.org, www.enlightenment.org, www.opensource.org)
