Re: NFS trouble
On Wed, Feb 29, 2012 at 5:44 AM, Raffaele Morelli wrote: > 2012/2/27 Tom H >> >> You have to use static ports for statd, mountd, and lockd if you're >> >> not using nfsv4. (You don't have to use the same static assignments >> >> used below.) >> >> >> >> - Set >> >> STATDOPTS="--port 4003 --outgoing-port 4004" >> >> in "/etc/default/nfs-common" >> >> >> >> - Set >> >> RPCMOUNTDOPTS="-p 4002" >> >> in "/etc/default/nfs-kernel-server" >> >> >> >> - Set >> >> options lockd nlm_udpport=4001 nlm_tcpport=4001 >> >> in "/etc/modprobe.d/lockd.conf" >> >> >> >> - Open the relevant ports with iptables >> > >> > Ok, so I guess I should ask my net admin to open all relevant ports for >> > mountd, nlockmgr and status as showed in `rpcinfo -p` OR whatever port I >> > would like to use for STATDOPTS, RPCMOUNTDOPTS and lockd. >> > Is it right? >> >> Yes, but you have to fix the port numbers by editing the files above >> because they'll be variable otherwise. > > That did it, thank you. You're welcome. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOdo=sygb4rvr67duboif3komdo13c-m3ivu6qbnpm+gtnb...@mail.gmail.com
Re: NFS trouble
2012/2/27 Tom H > >> You have to use static ports for statd, mountd, and lockd if you're > >> not using nfsv4. (You don't have to use the same static assignments > >> used below.) > >> > >> - Set > >> STATDOPTS="--port 4003 --outgoing-port 4004" > >> in "/etc/default/nfs-common" > >> > >> - Set > >> RPCMOUNTDOPTS="-p 4002" > >> in "/etc/default/nfs-kernel-server" > >> > >> - Set > >> options lockd nlm_udpport=4001 nlm_tcpport=4001 > >> in "/etc/modprobe.d/lockd.conf" > >> > >> - Open the relevant ports with iptables > > > > Ok, so I guess I should ask my net admin to open all relevant ports for > > mountd, nlockmgr and status as showed in `rpcinfo -p` OR whatever port I > > would like to use for STATDOPTS, RPCMOUNTDOPTS and lockd. > > Is it right? > > > Yes, but you have to fix the port numbers by editing the files above > because they'll be variable otherwise. > > That did it, thank you. regards -r -- *L'unica speranza di catarsi, ammesso che ne esista una, resta affidata all'istinto di ribellione, alla rivolta non isterilita in progetti, alla protesta violenta e viscerale.*
Re: NFS trouble
On Mon, Feb 27, 2012 at 9:29 AM, Raffaele Morelli wrote: > 2012/2/27 Tom H >> >> On Mon, Feb 27, 2012 at 5:45 AM, Raffaele Morelli >> wrote: >> > >> > I am setting up (tryin at least) a nfs mount on a remote machine, >> > there's a >> > firewall in between so I asked the net administrator to open ports 111 >> > and >> > 2049 on the server. >> > >> > /etc/exports on the server is >> > /home/username/ CLIENT_IP(ro,sync) >> > >> > mount command is >> > mount -v -t nfs REMOTE_IP:/home/username/ /local/mount/point >> > >> > I got this error: >> > >> > mount.nfs: timeout set for Mon Feb 27 11:28:00 2012 >> > mount.nfs: trying text-based options 'vers=4,addr=REMOTE_IP, >> > clientaddr=CLIENT_IP' >> > mount.nfs: mount(2): No such file or directory >> > mount.nfs: trying text-based options 'addr=remote_ip_addr' >> > mount.nfs: prog 13, trying vers=3, prot=6 >> > mount.nfs: trying REMOTE_IP prog 13 vers 3 prot TCP port 2049 >> > mount.nfs: prog 15, trying vers=3, prot=17 >> > mount.nfs: trying REMOTE_IP prog 15 vers 3 prot UDP port 34449 >> > mount.nfs: portmap query retrying: RPC: Timed out >> > mount.nfs: prog 15, trying vers=3, prot=6 >> > mount.nfs: trying REMOTE_IP prog 15 vers 3 prot TCP port 58566 >> > >> > showmount -e REMOTE_IP fails with >> > rpc mount export: RPC: Timed out >> > >> > - server is running debian squeeze with nfs-kernel-server from wheezy >> > - client is running debian wheezy >> > >> > any idea? >> >> (untested on wheezy but ok on squeeze) >> >> You have to use static ports for statd, mountd, and lockd if you're >> not using nfsv4. (You don't have to use the same static assignments >> used below.) >> >> - Set >> STATDOPTS="--port 4003 --outgoing-port 4004" >> in "/etc/default/nfs-common" >> >> - Set >> RPCMOUNTDOPTS="-p 4002" >> in "/etc/default/nfs-kernel-server" >> >> - Set >> options lockd nlm_udpport=4001 nlm_tcpport=4001 >> in "/etc/modprobe.d/lockd.conf" >> >> - Open the relevant ports with iptables > > Ok, so I guess I should ask my net admin to open all relevant ports for > mountd, nlockmgr and status as showed in `rpcinfo -p` OR whatever port I > would like to use for STATDOPTS, RPCMOUNTDOPTS and lockd. > Is it right? Yes, but you have to fix the port numbers by editing the files above because they'll be variable otherwise. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOdo=szrq+9xzc0+o2ou0k+4ttwbkygtjdcvjfaw7w0gcoa...@mail.gmail.com
Re: NFS trouble
2012/2/27 Tom H > On Mon, Feb 27, 2012 at 5:45 AM, Raffaele Morelli > wrote: > > > > I am setting up (tryin at least) a nfs mount on a remote machine, > there's a > > firewall in between so I asked the net administrator to open ports 111 > and > > 2049 on the server. > > > > /etc/exports on the server is > > /home/username/ CLIENT_IP(ro,sync) > > > > mount command is > > mount -v -t nfs REMOTE_IP:/home/username/ /local/mount/point > > > > I got this error: > > > > mount.nfs: timeout set for Mon Feb 27 11:28:00 2012 > > mount.nfs: trying text-based options 'vers=4,addr=REMOTE_IP, > > clientaddr=CLIENT_IP' > > mount.nfs: mount(2): No such file or directory > > mount.nfs: trying text-based options 'addr=remote_ip_addr' > > mount.nfs: prog 13, trying vers=3, prot=6 > > mount.nfs: trying REMOTE_IP prog 13 vers 3 prot TCP port 2049 > > mount.nfs: prog 15, trying vers=3, prot=17 > > mount.nfs: trying REMOTE_IP prog 15 vers 3 prot UDP port 34449 > > mount.nfs: portmap query retrying: RPC: Timed out > > mount.nfs: prog 15, trying vers=3, prot=6 > > mount.nfs: trying REMOTE_IP prog 15 vers 3 prot TCP port 58566 > > > > showmount -e REMOTE_IP fails with > > rpc mount export: RPC: Timed out > > > > - server is running debian squeeze with nfs-kernel-server from wheezy > > - client is running debian wheezy > > > > any idea? > > (untested on wheezy but ok on squeeze) > > You have to use static ports for statd, mountd, and lockd if you're > not using nfsv4. (You don't have to use the same static assignments > used below.) > > - Set > STATDOPTS="--port 4003 --outgoing-port 4004" > in "/etc/default/nfs-common" > > - Set > RPCMOUNTDOPTS="-p 4002" > in "/etc/default/nfs-kernel-server" > > - Set > options lockd nlm_udpport=4001 nlm_tcpport=4001 > in "/etc/modprobe.d/lockd.conf" > > - Open the relevant ports with iptables > Ok, so I guess I should ask my net admin to open all relevant ports for mountd, nlockmgr and status as showed in `rpcinfo -p` OR whatever port I would like to use for STATDOPTS, RPCMOUNTDOPTS and lockd. Is it right? regards -r
Re: NFS trouble
On Mon, Feb 27, 2012 at 5:45 AM, Raffaele Morelli wrote: > > I am setting up (tryin at least) a nfs mount on a remote machine, there's a > firewall in between so I asked the net administrator to open ports 111 and > 2049 on the server. > > /etc/exports on the server is > /home/username/ CLIENT_IP(ro,sync) > > mount command is > mount -v -t nfs REMOTE_IP:/home/username/ /local/mount/point > > I got this error: > > mount.nfs: timeout set for Mon Feb 27 11:28:00 2012 > mount.nfs: trying text-based options 'vers=4,addr=REMOTE_IP, > clientaddr=CLIENT_IP' > mount.nfs: mount(2): No such file or directory > mount.nfs: trying text-based options 'addr=remote_ip_addr' > mount.nfs: prog 13, trying vers=3, prot=6 > mount.nfs: trying REMOTE_IP prog 13 vers 3 prot TCP port 2049 > mount.nfs: prog 15, trying vers=3, prot=17 > mount.nfs: trying REMOTE_IP prog 15 vers 3 prot UDP port 34449 > mount.nfs: portmap query retrying: RPC: Timed out > mount.nfs: prog 15, trying vers=3, prot=6 > mount.nfs: trying REMOTE_IP prog 15 vers 3 prot TCP port 58566 > > showmount -e REMOTE_IP fails with > rpc mount export: RPC: Timed out > > - server is running debian squeeze with nfs-kernel-server from wheezy > - client is running debian wheezy > > any idea? (untested on wheezy but ok on squeeze) You have to use static ports for statd, mountd, and lockd if you're not using nfsv4. (You don't have to use the same static assignments used below.) - Set STATDOPTS="--port 4003 --outgoing-port 4004" in "/etc/default/nfs-common" - Set RPCMOUNTDOPTS="-p 4002" in "/etc/default/nfs-kernel-server" - Set options lockd nlm_udpport=4001 nlm_tcpport=4001 in "/etc/modprobe.d/lockd.conf" - Open the relevant ports with iptables -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOdo=syjw0geumppsa_gclo_fou+mdn6jbyv7dnuv5x-a3+...@mail.gmail.com
NFS trouble
Hi, I am setting up (tryin at least) a nfs mount on a remote machine, there's a firewall in between so I asked the net administrator to open ports 111 and 2049 on the server. /etc/exports on the server is /home/username/ CLIENT_IP(ro,sync) mount command is mount -v -t nfs REMOTE_IP:/home/username/ /local/mount/point I got this error: mount.nfs: timeout set for Mon Feb 27 11:28:00 2012 mount.nfs: trying text-based options 'vers=4,addr=REMOTE_IP,clientaddr=CLIENT_IP' mount.nfs: mount(2): No such file or directory mount.nfs: trying text-based options 'addr=remote_ip_addr' mount.nfs: prog 13, trying vers=3, prot=6 mount.nfs: trying REMOTE_IP prog 13 vers 3 prot TCP port 2049 mount.nfs: prog 15, trying vers=3, prot=17 mount.nfs: trying REMOTE_IP prog 15 vers 3 prot UDP port 34449 mount.nfs: portmap query retrying: RPC: Timed out mount.nfs: prog 15, trying vers=3, prot=6 mount.nfs: trying REMOTE_IP prog 15 vers 3 prot TCP port 58566 showmount -e REMOTE_IP fails with rpc mount export: RPC: Timed out - server is running debian squeeze with nfs-kernel-server from wheezy - client is running debian wheezy any idea? regards -r
NFS trouble
Hi, I am setting up (tryin at least) a nfs mount on a remote machine, there's a firewall in between so I asked the net administrator to open ports 111 and 2049 on the server. /etc/exports on the server is /home/username/ CLIENT_IP(ro,sync) mount command is mount -v -t nfs REMOTE_IP:/home/username/ /local/mount/point I got this error: mount.nfs: timeout set for Mon Feb 27 11:28:00 2012 mount.nfs: trying text-based options 'vers=4,addr=REMOTE_IP, clientaddr=CLIENT_IP' mount.nfs: mount(2): No such file or directory mount.nfs: trying text-based options 'addr=remote_ip_addr' mount.nfs: prog 13, trying vers=3, prot=6 mount.nfs: trying REMOTE_IP prog 13 vers 3 prot TCP port 2049 mount.nfs: prog 15, trying vers=3, prot=17 mount.nfs: trying REMOTE_IP prog 15 vers 3 prot UDP port 34449 mount.nfs: portmap query retrying: RPC: Timed out mount.nfs: prog 15, trying vers=3, prot=6 mount.nfs: trying REMOTE_IP prog 15 vers 3 prot TCP port 58566 showmount -e REMOTE_IP fails with rpc mount export: RPC: Timed out - server is running debian squeeze with nfs-kernel-server from wheezy - client is running debian wheezy any idea? regards
linux nfs trouble
I have a linux client that is mounting filesystems off of an ibm f50 running aix4.3.2. The linux client can read from the aix box just fine, but when it writes anything onto the nfs mounted drives, the writes are painfully slow (68Kb/sec) on a 100Mb ethernet network. I have read that this is due to the aix machine caching the writes and not sending back the acks, and so the linux machine times out. The linux machine is Debian hamm, running a 2.0.36 kernel. I tried a pre 2.2 kernel, but that did not fix the problem. Does anyone know if what I read is actually causing the problem, but more importantly, is there a solution to this problem? All the other machines on our network have no trouble writing to the nfs server. Thanks, Cam -- Cam Schaus [EMAIL PROTECTED]
Re: NFS trouble
> >My 2 cents' worth on this one is that my (new) system had full NFS >capability until I installed the netstd package, at which point I got the >above message. > >Poking around showed that /etc/init.d/netstd__nfs had all 5 of the _start_ >lines commented out. I am a Unix dumbkov but uncommenting the nsfd and >mountd lines got things going again. This may not be the way to fix it. > >HTH > >Lindsay That is precisely what my problem was also None of the daemons were started 'cause they were all commented out Paul
Re: NFS trouble
On Wed, 21 Aug 1996, Scott J. Geertgens wrote: > > > >> I keep getting the following message when trying to NFS mount any of the > > >> exported filesystems. > > >> > > >> mount clntupd_create: RPC: Program not registered > > >> > > > > > >Check that on the nfs server that mountd is running. This one is usually > > >NOT started from inetd but instead is started from one of the rc files > > > > >I realize this is most likely the correct answer, but I will add > another solution just for the sake of completeness. At one point I _did_ > have all the correct daemons running (nfsd, mountd), and still came up > with this error. It turned out that I had fiddled around with > /etc/hosts.allow and /etc/hosts.deny too much and shut off nearly > everything. This generates the same error as not having mountd running. > Wonderfully descriptive :) My 2 cents' worth on this one is that my (new) system had full NFS capability until I installed the netstd package, at which point I got the above message. Poking around showed that /etc/init.d/netstd__nfs had all 5 of the _start_ lines commented out. I am a Unix dumbkov but uncommenting the nsfd and mountd lines got things going again. This may not be the way to fix it. HTH Lindsay
Re: NFS trouble
> >> I keep getting the following message when trying to NFS mount any of the > >> exported filesystems. > >> > >>mount clntupd_create: RPC: Program not registered > >> > > > >Check that on the nfs server that mountd is running. This one is usually > >NOT started from inetd but instead is started from one of the rc files > > I realize this is most likely the correct answer, but I will add another solution just for the sake of completeness. At one point I _did_ have all the correct daemons running (nfsd, mountd), and still came up with this error. It turned out that I had fiddled around with /etc/hosts.allow and /etc/hosts.deny too much and shut off nearly everything. This generates the same error as not having mountd running. Wonderfully descriptive :) SJG
Re: NFS trouble
Sherwood, >> I keep getting the following message when trying to NFS mount any of the >> exported filesystems. >> >> mount clntupd_create: RPC: Program not registered >> > >Check that on the nfs server that mountd is running. This one is usually >NOT started from inetd but instead is started from one of the rc files > Thanks! I think you're right! Just got your repsonse, and looked, and no mountd...There are four nfsiod's running, but no mountd. Also, I tried the old Debian 0.93R6 last nite, and it still works with that system, so this is probably it. Thanks alot for your answer! Paul PS: My distribution came from I-Connect; the CD was cut on Jun 16. Your suggestion led me to the problem; thanks again. I found all the lines that execute the daemons commented out in the script in /init.d. The script was there, and being called on entry to runlevel 2 by the link S25netstd_nfs, but all the daemons were not executed by init because they were all commented out!
NFS trouble
Debian guru's, Here I am again in need of some assistance with this new release. I've been using NFS over a SLIP link to my laptop to access resources on the Debian box (like the CDROM, etc) with the R6 distribution for several months. Now, with 1.1 my laptop and another machine both using MiniLinux I keep getting the following message when trying to NFS mount any of the exported filesystems. mount clntupd_create: RPC: Program not registered What's going on here? I've checked the /etc/rpc file, and they're almost identical on the two machines. Have I forgotten to move something from the old R6 system to the new one, or is there something else I need to be doing to have this work? I've copied the /etc/hosts.allow, hosts.deny and so on from the R6 system. To make matters worse, it DOES NOT ALWAYS NOT WORK! I understand this may not be (or is it probably not) strictly a Deb1.1 issue, but was hoping to here something from the collective wisdom here that might help. Thanks Paul
