On Saturday 21 July 2012 06:55:06 Erik Christiansen did opine: > On 20.07.12 10:51, Gene Heskett wrote: > > On Friday 20 July 2012 10:18:49 Erik Christiansen did opine: > > > Would it help if we again posted some advice on how to most easily > > > change the uids on one host to match another? > > > > While that could I suppose be useful when the distro's involved are > > mix-n- match, I fail to see the utility of it when I am uid:gid 1000 > > on all 4 machines, all installed from our own 10.04-4 LTS install cd. > > That's fair, since you've already done all we were suggesting. So that > source of trouble has been eliminated. > > > Much more useful would be some real examples that all I'd need to > > translate would be to my hostnames or even hardcoded addresses. To > > my knowledge, there does not seem to be a way to make these services > > startup like a babbling idiot and tell us what they are doing, or why > > they can't do it. That would be 1000's of times more useful. > > True. When it's failing, what do the logfiles say? ISTR that it's one of > the first places you usually look, admittedly. The nfs-kernel-server > package unsurprisingly logs stuff in /var/log/kern.log,
I didn't know that, thank you. > and seems to be > reasonably talkative, even when things are going well. > Not so much, but maybe a clue from "service nfs-kernel-server restart": Jul 21 06:53:30 coyote kernel: [69826.321565] nfsd: last server has exited, flushing export cache Jul 21 06:53:31 coyote kernel: [69827.534764] svc: failed to register lockdv1 RPC service (errno 97). Jul 21 06:53:31 coyote kernel: [69827.535528] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory Jul 21 06:53:31 coyote kernel: [69827.535545] NFSD: starting 90-second grace period What is this lockdv1 RPC service? > Without a hint from the logs, we're reduced to shooting in the dark, or > at least through a growing cloud of BP smoke of our own making. > > > ATM, my /etc/exports file contains 1 non-commented line: > > /home/gene/ coyote.coyote.den(rw,sync,no_subtree_check) > > How does your DNS respond to that hostname, if you try a > "dig coyote.coyote.den", or if not, does at least > "ping coyote.coyote.den " pick up the right IP address? And this is nuking futz: root@coyote:/etc/init.d# dig coyote.coyote.den ; <<>> DiG 9.7.0-P1 <<>> coyote.coyote.den ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58240 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 0 ;; QUESTION SECTION: ;coyote.coyote.den. IN A ;; ANSWER SECTION: coyote.coyote.den. 60 IN A 8.15.7.122 coyote.coyote.den. 60 IN A 63.251.179.29 ;; AUTHORITY SECTION: coyote.coyote.den. 65535 IN NS WSC2.JOMAX.NET. coyote.coyote.den. 65535 IN NS WSC1.JOMAX.NET. ;; Query time: 113 msec ;; SERVER: 192.168.71.1#53(192.168.71.1) ;; WHEN: Sat Jul 21 07:00:29 2012 ;; MSG SIZE rcvd: 123 Totally AFU! root@coyote:/etc/init.d# ping -c3 coyote.coyote.den PING coyote.coyote.den (192.168.71.3) 56(84) bytes of data. 64 bytes from coyote.coyote.den (192.168.71.3): icmp_seq=1 ttl=64 time=0.022 ms 64 bytes from coyote.coyote.den (192.168.71.3): icmp_seq=2 ttl=64 time=0.016 ms 64 bytes from coyote.coyote.den (192.168.71.3): icmp_seq=3 ttl=64 time=0.025 ms In fact my local address is 192.168.71.3, and the router says my wan address is 204.111.65.217 and since I'm on a cable modem, that hasn't changed in 2+ years. My hosts file: 127.0.0.1 localhost 192.168.71.3 coyote.coyote.den coyote 192.168.71.1 router.coyote.den router 192.168.71.4 shop.coyote.den shop 192.168.71.5 lathe.coyote.den lathe 192.168.71.6 lappy.coyote.den lappy # The following lines are desirable for IPv6 capable hosts ::1 localhost ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters ff02::3 ip6-allhosts And resolv.conf: nameserver 192.168.71.1 domain coyote.coyote.den search hosts,dns Where the router is the gateway, which fwds the dns requests to one of the shentel servers, 209.55.24.10 or 209.55.27.13 > (i.e. are we certain that the problem is in NFS?) > Just for comparison, I've gotten away with nothing more than lines like > this in /etc/exports: /export/share 192.168.1.0/24(rw) > > > On all machines with the FQDN of that machine edited in. > > > > Similarly, the only active line in /etc/auto.master on all machines > > is: /net -hosts > > I've never tried autofs. In this case, it seems to be another potential > source of gremlins. Your aversion to editing /etc/fstab is noted, but if > we append a line to nfs mount a remote filesystem, it > (a) shouldn't interfere with preceding mounts, IIRC, and > (b) can be tested before shutting down, by invoking the mount command > just with either the filesystem or mountpoint as argument. That will > cause its /etc/fstab entry to be used for mounting, and prove the > pudding. > > Once that works, then editing finger-fumbles have been tested, and a > reboot need not be feared. (Later, autofs mounting could be tried, if > desired, once NFS is known to work.) > > ... > > > When I was running pclos on this box, with its 2.6.38.8 kernel, this > > all worked flawlessly except for the uid:gid problems when copying > > files so I always had to become root and fix that. > > Ah ... so the other boxes are unchanged, and the problem ought to be on > "this box". It's still a puzzle, without some logfile or cage-kicking > clues. See above, what did I miss, and whoinhell has contaminated the online dns database by registering my name? Boggles the mind. Just for grins root@coyote:/etc/init.d# ping -c3 shop.coyote.den PING shop.coyote.den (192.168.71.4) 56(84) bytes of data. 64 bytes from shop.coyote.den (192.168.71.4): icmp_seq=1 ttl=64 time=0.142 ms 64 bytes from shop.coyote.den (192.168.71.4): icmp_seq=2 ttl=64 time=0.130 ms 64 bytes from shop.coyote.den (192.168.71.4): icmp_seq=3 ttl=64 time=0.145 ms --- shop.coyote.den ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1998ms rtt min/avg/max/mdev = 0.130/0.139/0.145/0.006 ms root@coyote:/etc/init.d# ping -c3 lathe.coyote.den PING lathe.coyote.den (192.168.71.5) 56(84) bytes of data. 64 bytes from lathe.coyote.den (192.168.71.5): icmp_seq=1 ttl=64 time=0.146 ms 64 bytes from lathe.coyote.den (192.168.71.5): icmp_seq=2 ttl=64 time=0.130 ms 64 bytes from lathe.coyote.den (192.168.71.5): icmp_seq=3 ttl=64 time=0.125 ms --- lathe.coyote.den ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1998ms rtt min/avg/max/mdev = 0.125/0.133/0.146/0.016 ms root@coyote:/etc/init.d# ping -c3 lappy.coyote.den PING lappy.coyote.den (192.168.71.6) 56(84) bytes of data. >From coyote.coyote.den (192.168.71.3) icmp_seq=1 Destination Host Unreachable >From coyote.coyote.den (192.168.71.3) icmp_seq=2 Destination Host Unreachable >From coyote.coyote.den (192.168.71.3) icmp_seq=3 Destination Host Unreachable And those are all correct. > > So how do I go about making autofs and nfs-kernel-server get all > > mouthy so I can see where it fails? Right now it all comes back 'OK' > > but doesn't actually connect anyplace but on lathe.coyote.den, which > > does create a /net/lathe subdirectory, but its empty. The /net > > directories are empty after many restarts of those 2 services in > > /etc/init.d on the other 2 boxes, this one and shop.coyote.den. > > Lappy hasn't been out of the case locally in a month or more and ATM > > is not on my priority list until I need it. > > Oh, not much is mounting at all? (I'd incorrectly recalled that it only > gummed up after some time.) All the more reason for testing nfs without > autofs. An IP-address-netmask pair, as worked for me, might also be > worth trying. > > If you can post what happens when the abovementioned sticks are poked > into the cage, we'll hopefully be a step closer to identifying the > gremlins. > > Erik I do not have a local to this machine dns server (adns, dnsmasq, etc) installed, and just installed dnswalk to see what it says: root@coyote:/var# dnswalk -adilrfFm coyote.coyote.den. Checking coyote.coyote.den. BAD: SOA record not found for coyote.coyote.den. !BAD: coyote.coyote.den. has NO authoritative nameservers! !BAD: All zone transfer attempts of coyote.coyote.den. failed! !0 failures, 0 warnings, 3 errors. And of coarse there is no /var/named directory. I figured the hosts files should handle the local stuff & if its not in the hosts file, send it to the gateway, my router, which is a Buffalo Hi-Power running genuine dd-wrt. So despite the dig results, I should be covered. Humm, "hostname" returns the alias! root@coyote:/var# hostname coyote Should it not be returning the FQDN? So there are 3 head scratchers above. I just ran hostname and domainname in 'set' mode, they now return correct answers, but restarting nfs-kernel-server and autofs still returns the same results, total failure. Thanks Erik Cheers, Gene -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) My web page: <http://coyoteden.dyndns-free.com:85/gene> is up! Obey all traffic laws. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
