Came otu of the blue, one day workinga dn gone the next, although I do wonder if it was the last round of updates that may have caused it go boom, anyway get this through An error occured while loading nfs://192.168.0.1/nfs/: Connection to host An RPC error occurred. is broken Using kernel based NFS server: rcnfsserver restart Shutting down kernel based NFS server done Starting kernel based NFS server done Takes awhile to start. Oh I know there is a userspace NFS server, just seems to take more effort to get going and involves more services. Nov 1 00:15:01 barn rpc.mountd: authenticated mount request from 192.168.0.3:738 for /nfs (/nfs) Seems to notice the mount request... Not seeing anything obvious right now. Matt
On 01 Nov 2002 00:28:56 -0800 Matthew Johnson <matthew@psychohorse.com> wrote:
Came otu of the blue, one day workinga dn gone the next, although I do wonder if it was the last round of updates that may have caused it go boom, anyway get this through An error occured while loading nfs://192.168.0.1/nfs/: Connection to host An RPC error occurred. is broken Using kernel based NFS server:
rcnfsserver restart Shutting down kernel based NFS server done Starting kernel based NFS server done
Try rcnfsserver stop then rcportmap restart then rcnfsserver start You may need to do it on both machines. -- use Perl; #powerful programmable prestidigitation
On Fri, 2002-11-01 at 04:29, zentara wrote:
On 01 Nov 2002 00:28:56 -0800 Matthew Johnson <matthew@psychohorse.com> wrote:
Came otu of the blue, one day workinga dn gone the next, although I do wonder if it was the last round of updates that may have caused it go boom, anyway get this through An error occured while loading nfs://192.168.0.1/nfs/: Connection to host An RPC error occurred. is broken Using kernel based NFS server:
rcnfsserver restart Shutting down kernel based NFS server done Starting kernel based NFS server done
Try rcnfsserver stop then rcportmap restart then rcnfsserver start
You may need to do it on both machines.
Thanks, tried that and still cannot mount an NFS volume, this was working for about two weeks, then stopped working after using YOU on my server (early last week). Anyone else with 8.1 using NFS shares with an updated server? Matt
->> Try rcnfsserver stop ->> then rcportmap restart ->> then rcnfsserver start ->> ->> You may need to do it on both machines. -> ->Thanks, tried that and still cannot mount an NFS volume, this was ->working for about two weeks, then stopped working after using YOU on my ->server (early last week). -> ->Anyone else with 8.1 using NFS shares with an updated server? -> Can you be sure if it is a server problem or the client? Do you have multiple machines that you can test with? - herman
On Fri, 2002-11-01 at 08:35, Herman L. Knief wrote:
->> Try rcnfsserver stop ->> then rcportmap restart ->> then rcnfsserver start ->> ->> You may need to do it on both machines. -> ->Thanks, tried that and still cannot mount an NFS volume, this was ->working for about two weeks, then stopped working after using YOU on my ->server (early last week). -> ->Anyone else with 8.1 using NFS shares with an updated server? ->
Can you be sure if it is a server problem or the client? Do you have multiple machines that you can test with?
- herman
Yes and it fails on another client (whic happened to have been installed via NFS...). Says it cannot mount media. Very strange... Matt
On 01 Nov 2002 08:46:49 -0800 Matthew Johnson <matthew@psychohorse.com> wrote:
->Thanks, tried that and still cannot mount an NFS volume, this was ->working for about two weeks, then stopped working after using YOU on my ->server (early last week).
Yes and it fails on another client (whic happened to have been installed via NFS...). Says it cannot mount media.
Well maybe you have to adjust the permissions on the export directory and maybe the dvd device. Try making everything 777, and see what happens. If it works, then you know it's a permissions problem. SuSEconfig likes to adjust permissions evertime it runs, so maybe it adjusted the directories listed in /etc/exports so now an nfs user can't access them. Maybe remove the entry for dvd from /etc/fstab and mount it manually on your exported directory. -- use Perl; #powerful programmable prestidigitation
Hi You can also try this in /etc/exports: <path> *(rw,no_root_squash) Jaska. On Friday 01 November 2002 19:51, zentara wrote:
On 01 Nov 2002 08:46:49 -0800
Matthew Johnson <matthew@psychohorse.com> wrote:
->Thanks, tried that and still cannot mount an NFS volume, this was ->working for about two weeks, then stopped working after using YOU on my ->server (early last week).
Yes and it fails on another client (whic happened to have been installed via NFS...). Says it cannot mount media.
Well maybe you have to adjust the permissions on the export directory and maybe the dvd device.
Try making everything 777, and see what happens. If it works, then you know it's a permissions problem.
SuSEconfig likes to adjust permissions evertime it runs, so maybe it adjusted the directories listed in /etc/exports so now an nfs user can't access them.
Maybe remove the entry for dvd from /etc/fstab and mount it manually on your exported directory.
I'm missing something obvious, and the logs just ain't helping like they "normally" After a mount failure I get this in my logs: Nov 1 19:52:56 barn rpc.mountd: authenticated mount request from 192.168.0.3:697 for /nfs (/nfs) Nov 1 19:53:24 barn rpc.mountd: authenticated mount request from 192.168.0.3:697 for /nfs (/nfs) Nov 1 19:53:50 barn rpc.mountd: authenticated mount request from 192.168.0.3:697 for /nfs (/nfs I did change /nfs directory to 777, still no luck. Wonder if portmap is being a bugger? Anyway, I had already set /etc/hosts.allow to ALL:ALL and then tweaked my /etc/hosts.allow to nfsd : 192.168.0.0/255.255.255.0 : ALLOW portmap : 192.168.0.0/255.255.255.0 : ALLOW # rpc.mountd : 192.168.0.0/255.255.255.0 : ALLOW mountd : 192.168.0.0/255.255.255.0 : ALLOW Would SuSEfirewall2 cause any issues either? Noticed it was updated recently, around the time that the system gave these issues, but cannot see anything there other than high ports that could cause this directly... Any other ideas? Matt On Fri, 2002-11-01 at 08:35, Herman L. Knief wrote:
->> Try rcnfsserver stop ->> then rcportmap restart ->> then rcnfsserver start ->> ->> You may need to do it on both machines. -> ->Thanks, tried that and still cannot mount an NFS volume, this was ->working for about two weeks, then stopped working after using YOU on my ->server (early last week). -> ->Anyone else with 8.1 using NFS shares with an updated server? ->
Can you be sure if it is a server problem or the client? Do you have multiple machines that you can test with?
- herman
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Hi Check that You don't have recursive exports (ie. the same path can be accessed from 2 exports). This halted my system... I tried to export both "/" and "/home/public", and it made NFS non-working.. removed the /home/public, and immediatly started working again. Jaska. On Friday 01 November 2002 18:23, Matthew Johnson wrote:
On Fri, 2002-11-01 at 04:29, zentara wrote:
On 01 Nov 2002 00:28:56 -0800
Matthew Johnson <matthew@psychohorse.com> wrote:
Came otu of the blue, one day workinga dn gone the next, although I do wonder if it was the last round of updates that may have caused it go boom, anyway get this through An error occured while loading nfs://192.168.0.1/nfs/: Connection to host An RPC error occurred. is broken Using kernel based NFS server:
rcnfsserver restart Shutting down kernel based NFS server done Starting kernel based NFS server done
Try rcnfsserver stop then rcportmap restart then rcnfsserver start
You may need to do it on both machines.
Thanks, tried that and still cannot mount an NFS volume, this was working for about two weeks, then stopped working after using YOU on my server (early last week).
Anyone else with 8.1 using NFS shares with an updated server?
Matt
On Fri, 2002-11-01 at 09:25, jaakko tamminen wrote:
Hi
Check that You don't have recursive exports (ie. the same path can be accessed from 2 exports).
This halted my system... I tried to export both "/" and "/home/public", and it made NFS non-working.. removed the /home/public, and immediatly started working again.
Jaska.
Just one, called /nfs which contains the contents of the DVD. Its not like I'm being denied as it does authenticate. Unless soemthing in fstab is preventing it from being exported...? Not sure yet... Matt
Op vrijdag 1 november 2002 17:35, schreef Matthew Johnson:
On Fri, 2002-11-01 at 09:25, jaakko tamminen wrote:
Hi
Check that You don't have recursive exports (ie. the same path can be accessed from 2 exports).
This halted my system... I tried to export both "/" and "/home/public", and it made NFS non-working.. removed the /home/public, and immediatly started working again.
Jaska.
Just one, called /nfs which contains the contents of the DVD. Its not like I'm being denied as it does authenticate. Unless soemthing in fstab is preventing it from being exported...? Not sure yet...
Hi Matt, you're not the only one. I have the same (or at least similar problem) and Prabu Subroto reports the same issue too... OTOH I have another computer running as nfs succesfully, but that was set up with SuSE-7.2 (and is now running 7.3). I use SuSE-7.3, - nfs-utils-0.3.1-87 Tue 27 Nov 2001 11:02:18 $ rpm -qa --last | grep rpc nothing, humm.. $ rpm -qf /usr/sbin/rpcinfo glibc-2.2.4-77 No that is interesting. Wasn't this package updated lately, let's see: rpm -qa --last | grep glibc glibc-2.2.4-77 Fri 04 Oct 2002 09:26:39 Would this be the guilty one? How much time does take to time out? Is it exactly 300 sec (5 min)? This can be checked in /var/log/messages. In my case the file system is mounted after these 300 seconds, but that is far too long of course. I exactly wouldn't mind, but the NFS install process comes back with a "-1" as result.... Did you check the files in the directory: /var/lib/nfs/? What is the result of the command: "rpcinfo -p <ip address/name server> " Does it show something similar to this: program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100024 1 udp 877 status 100024 1 tcp 879 status 100003 2 udp 2049 nfs 100003 3 udp 2049 nfs 100021 1 udp 1024 nlockmgr 100021 3 udp 1024 nlockmgr 100021 4 udp 1024 nlockmgr 100005 1 udp 1026 mountd 100005 1 tcp 1024 mountd 100005 2 udp 1026 mountd 100005 2 tcp 1024 mountd 100005 3 udp 1026 mountd 100005 3 tcp 1024 mountd -- Richard
On Fri, 2002-11-01 at 23:11, Richard Bos wrote:
Op vrijdag 1 november 2002 17:35, schreef Matthew Johnson:
On Fri, 2002-11-01 at 09:25, jaakko tamminen wrote:
Hi
Check that You don't have recursive exports (ie. the same path can be accessed from 2 exports).
This halted my system... I tried to export both "/" and "/home/public", and it made NFS non-working.. removed the /home/public, and immediatly started working again.
Jaska.
Just one, called /nfs which contains the contents of the DVD. Its not like I'm being denied as it does authenticate. Unless soemthing in fstab is preventing it from being exported...? Not sure yet...
Hi Matt,
you're not the only one. I have the same (or at least similar problem) and Prabu Subroto reports the same issue too... OTOH I have another computer running as nfs succesfully, but that was set up with SuSE-7.2 (and is now running 7.3). I use SuSE-7.3, - nfs-utils-0.3.1-87 Tue 27 Nov 2001 11:02:18
$ rpm -qa --last | grep rpc nothing, humm.. $ rpm -qf /usr/sbin/rpcinfo glibc-2.2.4-77
No that is interesting. Wasn't this package updated lately, let's see: rpm -qa --last | grep glibc glibc-2.2.4-77 Fri 04 Oct 2002 09:26:39
Would this be the guilty one?
Same command: glibc-2.2.5-164 Fri 25 Oct 2002 04:13:40
How much time does take to time out? Is it exactly 300 sec (5 min)? This can be checked in /var/log/messages. In my case the file system is mounted after these 300 seconds, but that is far too long of course.
Yes about 5 minutes...
I exactly wouldn't mind, but the NFS install process comes back with a "-1" as result....
Did you check the files in the directory: /var/lib/nfs/?
What is the result of the command: "rpcinfo -p <ip address/name server> " Does it show something similar to this: program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100024 1 udp 877 status 100024 1 tcp 879 status 100003 2 udp 2049 nfs 100003 3 udp 2049 nfs 100021 1 udp 1024 nlockmgr 100021 3 udp 1024 nlockmgr 100021 4 udp 1024 nlockmgr 100005 1 udp 1026 mountd 100005 1 tcp 1024 mountd 100005 2 udp 1026 mountd 100005 2 tcp 1024 mountd 100005 3 udp 1026 mountd 100005 3 tcp 1024 mountd
this is what I get: program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100024 1 udp 1742 status 100024 1 tcp 1488 status 100003 2 udp 2049 nfs 100003 3 udp 2049 nfs 100003 2 tcp 2049 nfs 100003 3 tcp 2049 nfs 100005 1 udp 1927 mountd 100005 1 tcp 1495 mountd 100005 2 udp 1927 mountd 100005 2 tcp 1495 mountd 100005 3 udp 1927 mountd 100005 3 tcp 1495 mountd 100021 1 udp 1928 nlockmgr 100021 3 udp 1928 nlockmgr 100021 4 udp 1928 nlockmgr 100021 1 tcp 1496 nlockmgr 100021 3 tcp 1496 nlockmgr 100021 4 tcp 1496 nlockmgr
-- Richard
Well used vsftp as a work around. Damn annoying... Matt
participants (5)
-
Herman L. Knief -
jaakko tamminen -
Matthew Johnson -
Richard Bos -
zentara