Date: Mon, 25 Jun 2001 09:06:05 -0500 (CDT) From: Jason Nugent <malhavoc@stomped.com> To: <freebsd-questions@freebsd.org> Subject: An update on my NFS issue Message-ID: <Pine.BSF.4.33.0106250824120.96765-100000@smithers.stomped.com>
next in thread | raw e-mail | index | archive | help
Greetings, folks, I'm still fiddling with getting NFS working under my new kernel. I figured I'd give you an update regarding what I've attempted and what's been happening to this point, just in case any of you are losing sleep over this ;) 1. When I last left off, I was getting gethostbyname(titan) errors when NFS tried to mount it's partitions. These were showing up in /var/log/messages, and seemed to be generated by rpc.umntall: Jun 24 09:14:25 web1 /kernel: rpc.umntall: Jun 24 09:14:25 web1 /kernel: gethostbyname(titan) failed To see if it was a DNS issue, I put a line in my /etc/hosts file telling FreeBSD where to find titan, my NFS server. Upon reboot, a different error occurred (progress!). This time, a portmap error appeared directly in console at start up, complaining that RPC was unable to send. Being curious if this was an RPC error, I edited my rc.conf file and set: rpc_statd_enable="NO" to see if it was being caused by rpc.statd. The error still occurred on boot. Then, I decided to see if it was being caused by IPFW. Perhaps my kernel and userland were out of sync and my rules weren't being read properly. I set firewall_enable to "NO" and rebooted. Same error. My kernel has IPFW set to default to "accept", and it seemed to be working. Just as an aside, I added nfs_client_enable="NO" to my rc.conf file. To my surprise, my NFS paritions ended up being mounted under my working kernel, but there were no nfsiod processes running. Is that a feature of having nfs: entries in /etc/fstab? Now, if I rebooted using my old kernel (kernel.works.just.great), life is good. Even with the new binaries from the make installworld and new config files from mergemaster, everything works just fine. NFS works, IPFW works, and portmap doesn't complain about anything. To me, it -sounds- like it's a kernel issue, because the config files and system binaries do indeed function correctly under the older working kernel. I'm at a loss to discover why, however, because a diff on my two kernel config files returns nothing except for the odd comment that I've placed in one file but not the other. Both kernels are pretty much stock GENERIC configs, with maxusers bumped up and IPFW support added, and a few of the ISA devices that I really don't need removed. Any comments? Thanks, Jason ---------------------- Jason Nugent Aka MalHavoc Server Programmer and Administrator S T O M P E D . C O M For PGP public key: http://malhavoc.stomped.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.33.0106250824120.96765-100000>