Mageia forum

Hello

I'm new here, so thanks in advance!!!

I am trying to network Mageia 4 (as Server) to my Raspberry pi running Raspbmc (with static IP). The following is what I have been able to narrow down the issue to. I would appreciate any direction in correcting this problem, hopefully its something silly on my part!

Code: Select all

[root@Amon-Ra nmorris]# systemctl restart nfs-server.service
[root@Amon-Ra nmorris]# systemctl status nfs-server.service
nfs-server.service - NFS Server
   Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; enabled)
  Active: active (exited) since Mon 2014-04-21 12:30:08 EDT; 17s ago
  Process: 9595 ExecStopPost=/usr/sbin/exportfs -f (code=exited, status=0/SUCCESS)
  Process: 9593 ExecStop=/usr/sbin/rpc.nfsd 0 (code=exited, status=0/SUCCESS)
  Process: 9618 ExecStartPost=/usr/lib/nfs-utils/scripts/nfs-server.postconfig (code=exited, status=0/SUCCESS)
  Process: 9603 ExecStart=/usr/sbin/rpc.nfsd $RPCNFSDARGS $RPCNFSDCOUNT (code=exited, status=0/SUCCESS)
  Process: 9600 ExecStartPre=/usr/sbin/exportfs -r (code=exited, status=0/SUCCESS)
  Process: 9598 ExecStartPre=/usr/lib/nfs-utils/scripts/nfs-server.preconfig (code=exited, status=0/SUCCESS)
 Main PID: 9603 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/nfs-server.service

Apr 21 12:30:07 Amon-Ra systemd[1]: Stopping NFS Server...
Apr 21 12:30:07 Amon-Ra systemd[1]: Starting NFS Server...
Apr 21 12:30:08 Amon-Ra systemd[1]: Started NFS Server.
Apr 21 12:30:08 Amon-Ra rpc.nfsd[9603]: rpc.nfsd: unable to bind inet TCP so...)
Hint: Some lines were ellipsized, use -l to show in full.



tuxconvert wrote:[root@Amon-Ra nmorris]# systemctl status nfs-server.service

Hint: Some lines were ellipsized, use -l to show in full.

Please do what the hint tells you. Apart from that, all the Exec processes succeeded so far.

Executing systemctl with the -l switch, I obtained the following:

Code: Select all

systemctl -l status nfs-server.service
nfs-server.service - NFS Server
   Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; enabled)
   Active: active (exited) since Tue 2014-04-22 20:00:25 EDT; 48s ago
  Process: 2873 ExecStopPost=/usr/sbin/exportfs -f (code=exited, status=0/SUCCESS)
  Process: 2870 ExecStop=/usr/sbin/rpc.nfsd 0 (code=exited, status=0/SUCCESS)
  Process: 2896 ExecStartPost=/usr/lib/nfs-utils/scripts/nfs-server.postconfig (code=exited, status=0/SUCCESS)
  Process: 2881 ExecStart=/usr/sbin/rpc.nfsd $RPCNFSDARGS $RPCNFSDCOUNT (code=exited, status=0/SUCCESS)
  Process: 2879 ExecStartPre=/usr/sbin/exportfs -r (code=exited, status=0/SUCCESS)
  Process: 2876 ExecStartPre=/usr/lib/nfs-utils/scripts/nfs-server.preconfig (code=exited, status=0/SUCCESS)
 Main PID: 2881 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/nfs-server.service


Apr 22 20:00:25 Amon-Ra rpc.nfsd[2881]: rpc.nfsd: unable to bind inet TCP socket: errno 98 (Address already in use)
Apr 22 20:00:25 Amon-Ra systemd[1]: Started NFS Server.


Also:

Code: Select all

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
    100024    1   udp  34878  status
    100024    1   tcp  56177  status
    100021    1   udp   4002  nlockmgr
    100021    3   udp   4002  nlockmgr
    100021    4   udp   4002  nlockmgr
    100021    1   tcp   4002  nlockmgr
    100021    3   tcp   4002  nlockmgr
    100021    4   tcp   4002  nlockmgr
    100005    1   udp  60129  mountd
    100011    1   udp    958  rquotad
    100011    2   udp    958  rquotad
    100005    1   tcp  38378  mountd
    100011    1   tcp    958  rquotad
    100011    2   tcp    958  rquotad
    100005    2   udp  48493  mountd
    100005    2   tcp  53508  mountd
    100005    3   udp  52299  mountd
    100005    3   tcp  35120  mountd


From the above -- rpc.nfsd: unable to bind inet TCP socket: errno 98 (Address already in use). I'm not sure what address is already in use, so any suggestions on how to further investigate will be appreciated.

what does netstat -tunlp |grep 111 give you

regards peter

Rechecked my configuration settings and router ip address range; what ever the solution is to this problem still eludes me.

Wintpe the following is what was obtained from the following command:

Code: Select all

netstat -tunlp | grep 111
tcp        0      0 0.0.0.0:111                 0.0.0.0:*                   LISTEN      1422/rpcbind       
tcp        0      0 :::111                      :::*                        LISTEN      1422/rpcbind       
udp        0      0 0.0.0.0:111                 0.0.0.0:*                               1422/rpcbind       
udp        0      0 :::111                      :::*                                    1422/rpcbind   


In any event doktor5000 & wintpe, Thanks for the assistance!!!

I wonder if you have added any service to this system, that is not out of the box, and its stolen one of the NFS ports.

111 was the one that usually causes firewall issues with NFS, so it was the one i selected to check.

but you should go through them all and find out if there is a non NFS related binary grabbing the port.

I personally don't use mageia as a server and prefer centos or redhat 6.5 for this.

I can understand that you may prefer mageia if you feel you know it better, but really the difference between centos 6.5 and mageia 1 is
minimal.

anyhow that does not help with fixing your problem, perhaps posting a full netstat -tunlp may help someone who uses it the way you intend do a comparison with their system, and point out the problem.

regards peter

Maybe it would be more helpful to actually export some share and show an error when mounting from the client.
The systemd log excerpt in addition to the netstat output makes me suggest that NFS is running correctly,
and the error in the log only came from starting it when it was already running and still bound to port 111.

yes that is a possibility.

i have not tried a systemd system with NFS server yet, so would not have envisaged such a situation.

regards peter

I decided to restart NFS setup and check each step executed:

1. urpme nfs-utils
2. rpcinfo -p

Code: Select all

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
    100003    3   udp   2049  nfs
    100003    3   tcp   2049  nfs
    100005    1   udp   2049  mountd
    100005    3   udp   2049  mountd
    100005    1   tcp   2049  mountd
    100005    3   tcp   2049  mountd


I think that the nfs listing has something to do with the unfs3 service that is running, otherwise no other nfs service is available.

In anyevent, I will continue investigating and execute your suggestion doktor5000.

Thanks guys!!!

I was able to get the Mageia Server and the RPi working. All in all, I disable the unfs3 service, reinstalled nfs-server and restarted service. Also, I noticed during T/S that my router would intermittently display/detect the correct Server name instead of UNKNOWN in the ip table list.

For the router, I enable SMB/netbios and all was good.

Thanks to wintpe and doktor5000 for your assistance.

Please mark the thread accordingly by editing the topic of the first post and prefix it by [SOLVED], thanks