Okie... I have been a linux user/admin type for years. Until recently, I pretty much used Red Hat exclusively, but I have also played around with Debian and Slackware (I actually started out on slackware back in the 1.x kernel days). Now I have been using SLES 8 a LOT at work, and I have run into an issue I was hoping someone could shed some light on. THe problem is setting up NFS exports. Now, If I install a server using UL1.0 and the latest SP (SP3), why cant I manually edit /etc/exports? Heres the problem. I first installed UL1.0/SLES8 cleanly on a server. THen I did the whole SP thing and updated all the pertinant RPMs. Next, I had approximately 10 directories to export under NFS. SO, I edited /etc/exports using VI. AFter starting the NFS server, I went to the various client machines, and attempted to mount the various exports. No luck. I could mount one export on one client, but after that, I could not mount anything else via nfs on any other client. All I got were various RPC errors (usually RPC timeout errors). I fought with this for half a day, and finally reformatted, reinstalled, and reupdated. Then I did the same thing, BUT this time I never touched /etc/exports by hand. I did everything through YaST2. Set up all the exports, started the server, etc. This time, I could mount and unmount to my hearts content from all client machines. So, out of curiosity, I unmounted all the client machines, then on the server, re-edited /etc/exports to add three more export directories, and restarted the nfs server with YaST. Once again, the clients all puked when trying to mount the nfs exports. Same RPC errors. SO, reformat, reinstall, reupdate, and do it again with YaST2, and viola, it all worked again. WHy is this? I cant very well reccommend SuSE as a viable OS in a server environment if I cant do my editing by hand. I have no desire to use YaST2 to set up multiple exports on multiple servers. This one thing makes it all but useless to me. So, there is the question. Why is it that I can not get NFS to work UNLESS I use ONLY YaST to set up the exports? How do I get around this? How do I go and write a server setup script to automate the setting up of exports? I have a script that does just this, and under Red Hat of any version, it just works. All I do is run my script, and all my export dirs are created, mounted, and /etc/exports is configured, and NFS server is started, with no issues. Someone please help!! Cheers Jeff -- Jeffrey Lane, RHCE Yet another IT Ronin ... . ...- . -. - .... .-. . . -.. . Amateur Radio Call Whisky Four Kill Devil Hills From the heart of North Carolina at 50,000 milliwatts of pure power
On Tuesday 09 December 2003 22:43 pm, Jeffrey Lane wrote: <SNIP> Did you make sure there was a blank line at the end of the file and no spurious whitespace (like spaces at the end of lines)? I have found nfs to be really picky about that. Dylan -- Sweet moderation Heart of this nation Desert us not We are between the wars - Billy Bragg
Yes I did. But to be doubly sure, I will check again when I get back to work Thursday. Dylan wrote:
On Tuesday 09 December 2003 22:43 pm, Jeffrey Lane wrote: <SNIP>
Did you make sure there was a blank line at the end of the file and no spurious whitespace (like spaces at the end of lines)? I have found nfs to be really picky about that.
Dylan
Jeffrey Lane
AFter starting the NFS server, ...
How did you do it? IMHO, there are 2 NFS server services running on my machine (SuSE 8.2): # chkconfig | grep nfs nfs on (this is an NFS client service) nfslock on nfsserver on rpcinfo then reports: # rpcinfo -p localhost program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100024 1 udp 32768 status 100024 1 tcp 32768 status 100021 1 udp 32769 nlockmgr 100021 3 udp 32769 nlockmgr 100021 4 udp 32769 nlockmgr 100003 2 udp 2049 nfs 100003 3 udp 2049 nfs 100005 1 udp 32770 mountd 100005 1 tcp 32769 mountd 100005 2 udp 32770 mountd 100005 2 tcp 32769 mountd 100005 3 udp 32770 mountd 100005 3 tcp 32769 mountd I think you didn't activate all services and therefore you got those RPC timeouts. -- A.M.
participants (3)
-
Alexandr Malusek
-
Dylan
-
Jeffrey Lane