Re: [newbie] nfs problems
Hi, Axalon, upon 'mount -a'. weaver's /var/log/messages has errors like Jan 1 16:43:01 weaver portmap[935]: connect from 192.168.1.12 to getport(mountd): request from unauthorized host You'll get this message if there is no entry for the pc in /etc/hosts I was thinking this myself, but there are entries for the other machines in /etc/hosts, their names as well as their IP addresses. I also tried their IP addresses in /etc/exports. Still no go. I'll try updating the bios next. Thanks, Hidong Jan 1 16:43:01 weaver portmap[936]: connect from 192.168.1.12 to getport(mountd): request from unauthorized host Jan 1 16:43:44 weaver portmap[941]: connect from 192.168.1.13 to getport(mountd): request from unauthorized host Jan 1 16:43:44 weaver portmap[942]: connect from 192.168.1.13 to getport(mountd): request from unauthorized host which correspond to when I try to mount weaver's partitions on ripley or jonesy, or do a 'df' on ripley or jonesy. When I do a 'df' on weaver, all of the nfs mounted partitions show up, but 'df' on ripley and jonesy show all nfs partitions except weaver's. It seems like weaver is not recognizing ripley or jonesy. But I can telnet, ping, ftp, rlogin between all three computers just fine. Is there some nfs permission file that needs to be set? weaver's motherboard is an asus vx-97 with an award bios that dates from 1995. I don't think this is a y2k problem since everything else seems to be working fine. How do I get my nfs back? Thanks, Hidong -- MandrakeSoft http://www.mandrakesoft.com/ --Axalon
[newbie] nfs problems
Hi, I'm having a problem with nfs. I have a network of three Mandrake 6.1 machines all running 2.2.13-7mdk. The machines are weaver, ripley, and jonesy. Things were working fine before y2k. I shut the machines down before midnight, and turned them on again this morning (1/1). weaver is no longer exporting its nfs partition to ripley and jonesy. I've been trying to start nfs manually on all three machines with the sequence: 1. /etc/rc.d/init.d/inet stop 2. /etc/rc.d/init.d/portmap stop 3. /etc/rc.d/init.d/nfs stop 4. /etc/rc.d/init.d/inet start 5. /etc/rc.d/init.d/portmap start 6. /etc/rc.d/init.d/nfs start 7. exportfs 8. mount -a This sequence shows no errors on weaver, but on ripley and jonesy, this sequence shows the error mount: RPC: Program not registered upon 'mount -a'. weaver's /var/log/messages has errors like Jan 1 16:43:01 weaver portmap[935]: connect from 192.168.1.12 to getport(mountd): request from unauthorized host Jan 1 16:43:01 weaver portmap[936]: connect from 192.168.1.12 to getport(mountd): request from unauthorized host Jan 1 16:43:44 weaver portmap[941]: connect from 192.168.1.13 to getport(mountd): request from unauthorized host Jan 1 16:43:44 weaver portmap[942]: connect from 192.168.1.13 to getport(mountd): request from unauthorized host which correspond to when I try to mount weaver's partitions on ripley or jonesy, or do a 'df' on ripley or jonesy. When I do a 'df' on weaver, all of the nfs mounted partitions show up, but 'df' on ripley and jonesy show all nfs partitions except weaver's. It seems like weaver is not recognizing ripley or jonesy. But I can telnet, ping, ftp, rlogin between all three computers just fine. Is there some nfs permission file that needs to be set? weaver's motherboard is an asus vx-97 with an award bios that dates from 1995. I don't think this is a y2k problem since everything else seems to be working fine. How do I get my nfs back? Thanks, Hidong
[newbie] nfs problems with 6.1
Hi, I'm having great difficulties trying to get nfs working under Mandrake 6.1. I keep getting an nfssvc not implemented error. After some searching, I found out that I need to apply an nfs patch or get a knfsd-compatible kernel source. Does the appropriate kernel source come with the Mandrake 6.1 Power Pack? Which one of the six CDs would have it? I have to believe that Mandrake supplies the kernel source with its distribution so that people can recompile their kernels. Thanks, Hidong
Re: [newbie] nfs problems part 2
Eeep, you cut to much message i lost the problem :( On Mon, 13 Sep 1999, Hidong Kim wrote: Hi, Axalon, I did 'rpcinfo -p' on the broken box. It returns: program vers proto port 102 tcp111 rpcbind 102 udp111 rpcbind 151 udp635 mountd 152 udp635 mountd 151 tcp635 mountd 152 tcp635 mountd 132 udp 2049 nfs 132 tcp 2049 nfs If this is a server it's missing, 102 tcp111 portmapper 102 udp111 portmapper 1000211 udp 1024 nlockmgr 1000213 udp 1024 nlockmgr 1000211 tcp 1024 nlockmgr 1000213 tcp 1024 nlockmgr 1000241 udp857 status 1000241 tcp859 status 1000111 udp867 rquotad 1000112 udp867 rquotad /etc/rc.d/init.d/nfs status, ? On the two machines which seem to be working OK, 'rpcinfo -p' returns: program vers proto port 102 tcp111 rpcbind 102 udp111 rpcbind 1000211 udp 1024 nlockmgr 1000213 udp 1024 nlockmgr 1000211 tcp 1024 nlockmgr 1000213 tcp 1024 nlockmgr These two machines are mounting all remote partitions, including the ones on the broken box. Any suggestions? Thanks, Hidong Axalon Bloodstone wrote: rpcinfo -p broke_boxs_ip, says? -- MandrakeSoft http://www.mandrakesoft.com/ --Axalon -- MandrakeSoft http://www.mandrakesoft.com/ --Axalon
Re: [newbie] nfs problems part 2
On Tue, 14 Sep 1999, Hidong Kim wrote: Hi, Axalon, Thanks for the reply. Here was my original posting: start here Hi, I have a network of three Linux machines, all running kernel 2.2.9. I want to nfs mount their drives. On one of the machines, when I do a 'mount -a' to mount the partitions from the other two machines, I get this error: mount: RPC: Program not registered mount: RPC: Program not registered mount: RPC: Program not registered mount: RPC: Program not registered I assume that I'm getting this error four times since there are four remote partitions I want to nfs mount. I've checked that portmap and inetd are running on all machines. I've done 'usr/sbin/exportfs' on the other two machines so that the problem machine should be able to see the partitions on the other two machines. On the other two machines, I can see the partitions on the problem machine. There doesn't seem to be anything wrong with the network connection. I can ping, telnet, and rlogin between all three machines. Also, the problem machine is the gateway for this network, and I can get out to the Internet fine on all three machines. Why am I not able to nfs mount remote partitions on this one problem machine? Thanks, Hidong P.S. I tried rebooting my machine to see if that would solve the "mount program not registered" issue. when the machine was shutting down, I noticed an error message saying: rpc.nfsd forgot to set AF_INET in udp sendmsg. Fix it! Would this be causing the problems I'm seeing? And how do I fix it? end here The three Linux machines are called weaver, ripley, and jonesy. Weaver is the one having problems. None of the three is a server. However, weaver is the gateway for the three machines, and weaver also has a printer which can be accessed by all three machines. 'rpcinfo -p' on weaver returns: program vers proto port 102 tcp111 rpcbind 102 udp111 rpcbind 151 udp635 mountd 152 udp635 mountd 151 tcp635 mountd 152 tcp635 mountd 132 udp 2049 nfs 132 tcp 2049 nfs 'rpcinfo -p' on ripley and jonesy returns: program vers proto port 102 tcp111 rpcbind 102 udp111 rpcbind 1000211 udp 1024 nlockmgr 1000213 udp 1024 nlockmgr 1000211 tcp 1024 nlockmgr 1000213 tcp 1024 nlockmgr I would expect that 'rpcinfo -p' should return the same information for all three machines. Any suggestions? Thanks, Hidong check weaver's '/etc/rc.d/init.d/nfs status' But i can't see why haveing the nfs server running is giveing you problems (I use nfs here alot and haven't had problems sense mariner), unless it's doing something strange to the lock daemon -- MandrakeSoft http://www.mandrakesoft.com/ --Axalon
Re: [newbie] nfs problems part 2 (fixed)
Hi, Axalon, The problem's fixed. I went to check weaver's /etc/rc.d/init.d/nfs like you suggested, and I realized that this file was missing. I had been starting the nfs services with '/usr/sbin/rpc.mountd' and '/usr/sbin/rpc.nfsd'. So I copied the /etc/rc.d/init.d/nfs from one of the other machines to weaver, killed all nfs services on all three machines, and then restarted the services using the scripts in /etc/rc.d/init.d. Now everything's working. Thanks! Hidong Axalon Bloodstone wrote: On Tue, 14 Sep 1999, Hidong Kim wrote: Hi, Axalon, Thanks for the reply. Here was my original posting: start here Hi, I have a network of three Linux machines, all running kernel 2.2.9. I want to nfs mount their drives. On one of the machines, when I do a 'mount -a' to mount the partitions from the other two machines, I get this error: mount: RPC: Program not registered mount: RPC: Program not registered mount: RPC: Program not registered mount: RPC: Program not registered I assume that I'm getting this error four times since there are four remote partitions I want to nfs mount. I've checked that portmap and inetd are running on all machines. I've done 'usr/sbin/exportfs' on the other two machines so that the problem machine should be able to see the partitions on the other two machines. On the other two machines, I can see the partitions on the problem machine. There doesn't seem to be anything wrong with the network connection. I can ping, telnet, and rlogin between all three machines. Also, the problem machine is the gateway for this network, and I can get out to the Internet fine on all three machines. Why am I not able to nfs mount remote partitions on this one problem machine? Thanks, Hidong P.S. I tried rebooting my machine to see if that would solve the "mount program not registered" issue. when the machine was shutting down, I noticed an error message saying: rpc.nfsd forgot to set AF_INET in udp sendmsg. Fix it! Would this be causing the problems I'm seeing? And how do I fix it? end here The three Linux machines are called weaver, ripley, and jonesy. Weaver is the one having problems. None of the three is a server. However, weaver is the gateway for the three machines, and weaver also has a printer which can be accessed by all three machines. 'rpcinfo -p' on weaver returns: program vers proto port 102 tcp111 rpcbind 102 udp111 rpcbind 151 udp635 mountd 152 udp635 mountd 151 tcp635 mountd 152 tcp635 mountd 132 udp 2049 nfs 132 tcp 2049 nfs 'rpcinfo -p' on ripley and jonesy returns: program vers proto port 102 tcp111 rpcbind 102 udp111 rpcbind 1000211 udp 1024 nlockmgr 1000213 udp 1024 nlockmgr 1000211 tcp 1024 nlockmgr 1000213 tcp 1024 nlockmgr I would expect that 'rpcinfo -p' should return the same information for all three machines. Any suggestions? Thanks, Hidong check weaver's '/etc/rc.d/init.d/nfs status' But i can't see why haveing the nfs server running is giveing you problems (I use nfs here alot and haven't had problems sense mariner), unless it's doing something strange to the lock daemon -- MandrakeSoft http://www.mandrakesoft.com/ --Axalon
Re: [newbie] nfs problems part 2
Hidong Kim wrote: Hi, I tried rebooting my machine to see if that would solve the "mount program not registered" issue. when the machine was shutting down, I noticed an error message saying: rpc.nfsd forgot to set AF_INET in udp sendmsg. Fix it! Would this be causing the problems I'm seeing? And how do I fix it? Thanks, Hidong Hi, I still haven't figured out why one of the machines on my three Linux machine network is not able to nfs mount the partitions on the two other machines. I'm still getting the error: mount: RPC: Program not registered when I try to 'mount -a' on this problem machine. When I do a 'ps aux' on the problem machine, I notice that '(portmap)' and '(inetd)' are listed, in parentheses. On the other two machines which have no problem mounting remote partitions, when I do 'ps aux', I see that 'portmap' and 'inetd' are listed, no parentheses. Would this have any bearing on the problem machine's inability to mount remote partitions? Thanks, Hidong
Re: [newbie] nfs problems part 2
On Mon, 13 Sep 1999, Hidong Kim wrote: Hidong Kim wrote: Hi, I tried rebooting my machine to see if that would solve the "mount program not registered" issue. when the machine was shutting down, I noticed an error message saying: rpc.nfsd forgot to set AF_INET in udp sendmsg. Fix it! Would this be causing the problems I'm seeing? And how do I fix it? Thanks, Hidong Hi, I still haven't figured out why one of the machines on my three Linux machine network is not able to nfs mount the partitions on the two other machines. I'm still getting the error: mount: RPC: Program not registered when I try to 'mount -a' on this problem machine. When I do a 'ps aux' on the problem machine, I notice that '(portmap)' and '(inetd)' are listed, in parentheses. On the other two machines which have no problem mounting remote partitions, when I do 'ps aux', I see that 'portmap' and 'inetd' are listed, no parentheses. Would this have any bearing on the problem machine's inability to mount remote partitions? Thanks, Hidong rpcinfo -p broke_boxs_ip, says? -- MandrakeSoft http://www.mandrakesoft.com/ --Axalon
Re: [newbie] nfs problems part 2
Hi, Axalon, I did 'rpcinfo -p' on the broken box. It returns: program vers proto port 102 tcp111 rpcbind 102 udp111 rpcbind 151 udp635 mountd 152 udp635 mountd 151 tcp635 mountd 152 tcp635 mountd 132 udp 2049 nfs 132 tcp 2049 nfs On the two machines which seem to be working OK, 'rpcinfo -p' returns: program vers proto port 102 tcp111 rpcbind 102 udp111 rpcbind 1000211 udp 1024 nlockmgr 1000213 udp 1024 nlockmgr 1000211 tcp 1024 nlockmgr 1000213 tcp 1024 nlockmgr These two machines are mounting all remote partitions, including the ones on the broken box. Any suggestions? Thanks, Hidong Axalon Bloodstone wrote: rpcinfo -p broke_boxs_ip, says? -- MandrakeSoft http://www.mandrakesoft.com/ --Axalon
Re: [newbie] nfs problems part 2
On Sun, 12 Sep 1999, you wrote: Hi, I tried rebooting my machine to see if that would solve the "mount program not registered" issue. when the machine was shutting down, I noticed an error message saying: rpc.nfsd forgot to set AF_INET in udp sendmsg. Fix it! Would this be causing the problems I'm seeing? And how do I fix it? Thanks, Are you using NFS? If not, turn it off in System Services (the only way I know to get there is to run "setup" as root and choose system services.) Also, I'd turn off anything else that you have running that you don't use. John
[newbie] nfs problems part 2
Hi, I tried rebooting my machine to see if that would solve the "mount program not registered" issue. when the machine was shutting down, I noticed an error message saying: rpc.nfsd forgot to set AF_INET in udp sendmsg. Fix it! Would this be causing the problems I'm seeing? And how do I fix it? Thanks, Hidong
Re: [newbie] nfs problems
[EMAIL PROTECTED] wrote: On Sat, May 08, 1999 at 03:05:57PM -0700, Hidong Kim wrote: Hi, I have a network of three Linux machines named weaver, ripley, and jonesy. I have them networked, and their disks were all nfs mounted. But then today, all of the sudden, weaver is not seeing ripley's disks, and jonesy is not seeing weaver's disks. ripley is seeing all of the nfs mounted disks. I tried to re-export and re-mount all three machines. When I try 'mount -a' on weaver, I get the error twice: "mount: RPC: Program not registered". I was using these computers last night and everything seemed fine. I didn't change any configuration files since then. I can still ping, telnet, and ftp between all three machines. What could be wrong? Thanks, Check to make sure portmap and the RPC daemons are still running on all three machines. -- Steve Philp [EMAIL PROTECTED] Hi, Thanks for the reply. I'm still having problems. I checked that portmap and the rpc daemons are running all all three of my machines. When I do 'usr/sbin/rpcinfo -p', I get: program vers proto port 102 tcp111 rpcbind 102 udp111 rpcbind 151 udp635 mountd 152 udp635 mountd 151 tcp635 mountd 152 tcp635 mountd 132 udp 2049 nfs 132 tcp 2049 nfs 1000211 udp 1024 nlockmgr 1000213 udp 1024 nlockmgr 1000211 tcp 1024 nlockmgr 1000213 tcp 1024 nlockmgr (By the way, what is nlockmgr?) I also see the daemons running when I do a 'ps aux'. The problem appears to be in the exporting by one of the machines, ripley. ripley can see the nfs-mounted partitions on my two other machines, but the two other machines don't see the nfs-mounted partitions on ripley. When I try 'mount -a' on the other two machines, I get: mount: RPC: Program not registered mount: RPC: Program not registered I'm, assuming I get this error twice for each of the two partitions I'm trying to export from ripley. I'm running /usr/sbin/exportfs from ripley before I try to mount on the other two machines, but I can't get it to work. This is really weird since I haven't changed anything since the nfs network seemed to be fine two nights ago. I had also installed samba a few days ago, before I saw this nfs problem. Could this be related to samba at all? I uninstalled samba to check. It didn't seem to affect the nfs problems I'm seeing. Thanks again, Hidong
Re: [newbie] nfs problems
On Sat, May 08, 1999 at 03:05:57PM -0700, Hidong Kim wrote: Hi, I have a network of three Linux machines named weaver, ripley, and jonesy. I have them networked, and their disks were all nfs mounted. But then today, all of the sudden, weaver is not seeing ripley's disks, and jonesy is not seeing weaver's disks. ripley is seeing all of the nfs mounted disks. I tried to re-export and re-mount all three machines. When I try 'mount -a' on weaver, I get the error twice: "mount: RPC: Program not registered". I was using these computers last night and everything seemed fine. I didn't change any configuration files since then. I can still ping, telnet, and ftp between all three machines. What could be wrong? Thanks, Check to make sure portmap and the RPC daemons are still running on all three machines. -- Steve Philp [EMAIL PROTECTED]
