How do I start NFS server services?

opensuse-reference/cha.nfs.html#sec.nfs.configuring-nfs-server
It says:

Start YaST and select Network Services+NFS Server

but it isn’t clear about what to do when “NFS Server” is not provided as an option.
I have “NFS Client” and “NIS Client” and nothing between them.
Yes, I can spend a lot of time meandering around the net with Google, stubbing my toes over
permission problems and NFS setup paranoia, but I would really like the Yast GUI to lead
me through the security minefield that has been placed around NFS, and I’d like it
to start automatically when I boot. Thanks!

bkorb wrote:

>
> but it isn’t clear about what to do when “NFS Server” is not provided
> as an option.

You haven’t chosen server stuff during your initial installation.

> I have “NFS Client” and “NIS Client” and nothing between them.
> Yes, I can spend a lot of time meandering around the net with Google,
> stubbing my toes over
> permission problems and NFS setup paranoia, but I would really like the
> Yast GUI

Then install it.

Vahis

http://waxborg.servepics.com
openSUSE 11.4 (x86_64) 2.6.37.6-0.20-default main host
openSUSE 12.1 (x86_64) 3.5.3-40-desktop Tumbleweed in VirtualBox
openSUSE 12.1 (i586) 3.1.10-1.16-desktop in EeePC 900

My last installation had all the server stuff in it and I tried to remember to install all the server stuff. I guess I missed some. It’d be nice if I could have upgraded instead of doing a fresh install, but I was not provided that option. At least it did keep the partitioning information. Anyway, “Then install it” could use a tiny bit of elaboration. Ah, there it is. The 25th line of “nfs” matches says “yast2-nfs-server”. The trouble is is that there are so many yast packages that it is not directly obvious what all you need.

Summary: I did choose server stuff, just not configuring the yast2-nfs-server stuff.

Well, ok, I did manage to configure nfs by hand as well as yast2 did. I am still getting rpcbind issues:

Client side:
$ showmount -e 192.168.10.2
showmount: Cannot retrieve info from host: 192.168.10.2: RPC failed:: RPC: Program unavailable
Server side:
# rpcinfo -p
   program vers proto   port  service
    100000    4   tcp    111  portmapper
    100000    3   tcp    111  portmapper
    100000    2   tcp    111  portmapper
    100000    4   udp    111  portmapper
    100000    3   udp    111  portmapper
    100000    2   udp    111  portmapper
    100005    1   udp  32988  mountd
    100005    1   tcp  48931  mountd
    100005    2   udp  40157  mountd
    100005    2   tcp  41450  mountd
    100005    3   udp  60847  mountd
    100005    3   tcp  44878  mountd
    100024    1   udp  57209  status
    100024    1   tcp  43921  status
    100003    2   tcp   2049  nfs
    100003    3   tcp   2049  nfs
    100003    4   tcp   2049  nfs
    100227    2   tcp   2049  nfs_acl
    100227    3   tcp   2049  nfs_acl
    100003    2   udp   2049  nfs
    100003    3   udp   2049  nfs
    100003    4   udp   2049  nfs
    100227    2   udp   2049  nfs_acl
    100227    3   udp   2049  nfs_acl
    100021    1   udp  58086  nlockmgr
    100021    3   udp  58086  nlockmgr
    100021    4   udp  58086  nlockmgr
    100021    1   tcp  50862  nlockmgr
    100021    3   tcp  50862  nlockmgr
    100021    4   tcp  50862  nlockmgr
# egrep -v '^#' /etc/hosts.allow 


lockd   : 192.168.10.0/255.255.255.0 : allow
mountd  : 192.168.10.0/255.255.255.0 : allow
rquotad : 192.168.10.0/255.255.255.0 : allow
statd   : 192.168.10.0/255.255.255.0 : allow
portmap : 192.168.10.0/255.255.255.0 : allow

The list of services was incomplete. Changing hosts.allow to:

ALL: 192… : allow

fixes the problem

== RFE for yast2-nfs-server:

Please, please, please include hosts.allow fixups. This was too hard.

YaST > Software > Software management. Type nfs in the search field and Search. Check if you have yast2-nfs-server installed. (and of cpourse you should have nfs-kernel-server).

I setup an NFS server for the first time a few weeks ago. Well, okay, I had previously setup NFS on solaris systems, but this was my first for opensuse.

I included what I thought was the NFS server stuff in my install.

I went to Yast, did not find an install module.

I opened software management is Yast, did a search for NFS, found the missing part and installed.

I closed Yast, then restarted it, so that it would see the new Yast module. And from there, setting up was reasonably straightforward.

The Yast module made the needed firewall changes and started the needed services.

I am puzzled by your “hosts.allow” problem. I did not have to do anything there.

As best I recall, the installed versions of “hosts.allow” and “hosts.deny” contain only comments. If you were restrict rpcbind there, then I think you did it to yourself with your own changes to those files.

``I think you did it to yourself with your own changes to those files’’

Something like that is entirely possible as I was trying a lot of variations. However, with both
hosts.allow and hosts.deny being empty did not work. I got the message on the
client noted above. By specifically allowing all permissions on my local lan, it worked.
The start of the problem was, indeed, not knowing that adding nfs server meant that
it would be real convenient to also have yast2-nfs-server.

I just installed 12.2 on a system and added the NFS server pattern during installation. I found out that yast2-nfs-server is not included iin that pattern. Which is an omission IMHO.

It has never been part of the default install. Both for NFS and NIS, the yast2 modules for the clients get installed, de server ones don’t. 100% sure about this, my network at home has been NFS/NIS based for years now.

Knurpht wrote:
> hcvv;2487392 Wrote:
>> I just installed 12.2 on a system and added the NFS server pattern
>> during installation. I found out that yast2-nfs-server is not included
>> iin that pattern. Which is an omission IMHO.
>
> It has never been part of the default install. Both for NFS and NIS,
> the yast2 modules for the clients get installed, de server ones don’t.
> 100% sure about this, my network at home has been NFS/NIS based for
> years now.

Sounds like something for bugzilla

On Sat, 15 Sep 2012 11:06:01 GMT, Knurpht
<Knurpht@no-mx.forums.opensuse.org> wrote:

>
>hcvv;2487392 Wrote:
>> I just installed 12.2 on a system and added the NFS server pattern
>> during installation. I found out that yast2-nfs-server is not included
>> iin that pattern. Which is an omission IMHO.
>
>It has never been part of the default install. Both for NFS and NIS,
>the yast2 modules for the clients get installed, de server ones don’t.
>100% sure about this, my network at home has been NFS/NIS based for
>years now.

The side issue is Yast-nfs-server is not installed with NFS server. If so
it is a serious omission

?-)

On 2012-09-17 12:34, Dave Howorth wrote:

> Sounds like something for bugzilla

At least two :slight_smile:

One for the documentation, that it should say that you might have to install the yast nfs
server module separately.


Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

On 2012-09-23 20:43, josephkk wrote:

> The side issue is Yast-nfs-server is not installed with NFS server. If so
> it is a serious omission

It works the other way: the yast nfs server module will install the extra modules needed :slight_smile:

It would be interesting that yast had a module to list all possible modules, installed or not,
and could install the rest on request.


Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

Carlos E. R. wrote:
> On 2012-09-23 20:43, josephkk wrote:
>
>> The side issue is Yast-nfs-server is not installed with NFS server. If so
>> it is a serious omission
>
> It works the other way: the yast nfs server module will install the extra modules needed :slight_smile:
>
> It would be interesting that yast had a module to list all possible modules, installed or not,
> and could install the rest on request.

It would make more sense if all yast modules were always installed but
did NOT automatically pull in the packages for the actual service. Then
if you clicked on say NFS Server in YaST it would ask “NFS Server is not
installed. Do you want to install and configure it?” and away it goes.

On 2012-09-24 11:20, Dave Howorth wrote:
> Carlos E. R. wrote:

>> It would be interesting that yast had a module to list all possible modules, installed or not,
>> and could install the rest on request.
>
> It would make more sense if all yast modules were always installed but
> did NOT automatically pull in the packages for the actual service. Then
> if you clicked on say NFS Server in YaST it would ask “NFS Server is not
> installed. Do you want to install and configure it?” and away it goes.

True, but I think they prefer not to clutter that much the yast screen.


Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

I remember YaST doing similar in other areas: asking to install things that are needed.

On 2012-09-24 17:16, hcvv wrote:

> I remember YaST doing similar in other areas: asking to install things
> that are needed.

The exception are Yast modules themselves, there is not a list in Yast of what modules you can
add and to what purpose. You have to search for them in the package manager. A pity.


Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

On Mon, 24 Sep 2012 01:23:06 GMT, “Carlos E. R.”
<robin_listas@no-mx.forums.opensuse.org> wrote:

>On 2012-09-23 20:43, josephkk wrote:
>
>> The side issue is Yast-nfs-server is not installed with NFS server. If so
>> it is a serious omission
>
>It works the other way: the yast nfs server module will install the extra modules needed :slight_smile:
>
>It would be interesting that yast had a module to list all possible modules, installed or not,
>and could install the rest on request.

Compare your other response to Dave Howorth.

?-)