NFS works fine here on two different computers running 13.1 servers; tested it just earlier today in fact (if any upgrade should have done anything negatively to it); I do also run an NFS server on an old SuSE 9.1 computer, which works just as fine with 13.1 clients.
I mount manually though, but that should not have any implications on the server set-up.
Please elaborate on the set-up procedure, I have seen references to NFS problems here earlier but not experienced any myself.
One of the clients are running WinXP, sharing on an NFS network using Windows is no problem.
yeah, I have run NFS on opensuse for the last ten years. Never ran into this error before. The way I learned to setup NFS was to set my network static, setup my hosts file, and run a local DNS(with just forwarders and the default .arpa master zone.
I have a brand new install, in fact, I even re-installed because my initial network setup was sloppy. I also have a new 13.1 install that will be the client system and on that machine it produced the same error.
So, a brand new install. I set up my network, Hosts file, DNS - I setup my folders to export in the Yast NFS Server applet. upon saving the exports I get the error like the OP, “Unable to start idmapd. Check your domain setting.” But in fact, idmapd does start, I watched it start in the process viewer.
Still the Yast NFS Client cannot see any NFS server on the network, from any machine.
as well like the OP I have tried unchecking the v4 box and got the same error “Unable to stop idmapd”
I am not a sophisticated command line linux user, but I read up on manually configuring fstab, exports, idmapd and the NFS server and it seems to me that everything was in the right place. I have also looked around for a NEW NFS How To but not really found anything; I looked around in case there was really anything that new in the 13.1 setup process.
I would really appreciate any help to get this working, tell me what info you need from me to get the details you need to better understand the errors.
The way I learned to setup NFS was to set my network static, setup my hosts file, and run a local DNS(with just forwarders and the default .arpa master zone.
Aha, I have never had to go through all that, but some kind of static set-up makes things easier.
What you could try is to ignore somehow the error message, hope that the server will automatically start on a reboot and then try to mount manually:
mount 10.0.0.1: /mnt/nfs/a
Change the IP and create a directory where you wish to mount it; mount as root.
My two server machines running OS 13.1 are set up straight forwards through the YaST module ‘NFS server’, I have not added any extra parameters for security etc., they are just open for the LAN; but I do have firewalls running on them, remember to open port.
I do have nfs working - not optimally though - the nfs server is not discoverable via the “choose” button.
because I fill in my hosts file, I can simply add the alias for the NFS server and then sellect the mounts I want.
I have not tried to find out why the NFS server is not discoverable, It is a project for another day.
I think I have to work on my DNS settings which would be fodder for it’s own thread.
I think the NFS server, before 13.1 had a separate support daemon called idmapd. I believe they have now made idmapd part of the nfsserver. (No idmap package, or files can be found in 13.1, but a idmaplib does exists.) The YAST tool seams to be writing the config file correctly for the latest nfsserver. But the script has not been updated when you exit/finish, so it first tries to start the idmapd, and when that fails, exits without starting the nfsserver.
I have had the same issue with the YAST tool. Use:
I have the same problem on two 13.1 openSUSE servers with NFS. It is reported as a bug https://bugzilla.novell.com/show_bug.cgi?id=892893
I have no clue if it is worked on, I haven’t figured out bugzillas new interface yet (have a lot to learn there as well) It says “priority P5-None” or I’m reading in the wrong place?
[FONT=arial]If it returns off then it hasn’t started properly. Then run:
[/FONT]chkconfig nfs on
And that should start it and be persistent over reboots.
I had a similar problem when first setting up NFS server but that was on a dedicated server with a minimal install. The warning always pops up and can be ignored O.K with my setup, if chkconfig says it’s on then all should work.
One piece of advice I was given was:
“The first thing to try is mounting something on the server, via nfs. Not on the client.
That way you clear out configuration errors before dealing with network problems.”
This eventually led me to a dodgy switch, nothing to do with the server or client.