Bug 11097 - NFS does not works since Core 100
Summary: NFS does not works since Core 100
Status: CLOSED DUPLICATE of bug 11098
Alias: None
Product: IPFire
Classification: Unclassified
Component: nfs-utils (show other bugs)
Version: 2
Hardware: unspecified Unspecified
: - Unknown - Minor Usability
Assignee: Assigned to nobody - feel free to grab it and work on it
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-17 12:46 UTC by lars.seidler
Modified: 2016-04-24 21:40 UTC (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description lars.seidler 2016-04-17 12:46:37 UTC
Hallo,

ich setze seit vielen Monaten erfolgreich den NFS-Server auf der ipFire ein. Seit dem gestrigen Update auf Core100 funktioniert der NFS-Server nicht mehr. Es ist kein Zugriff auf die NFS-Freigaben möglich, obwohl an der Konfiguration nichts geändert wurde.

Versuche ich, auf der ipFire den NFS-Server mit

Code: Select all
/etc/init.d/nfs-server restart


neu zu starten, kommen folgende Fehlermeldungen:

Code: Select all
[root@ipfire init.d]# ./nfs-server restart
Stopping NFS statd...                                                                                                                               [  OK  ]
Stopping NFS nfsd...                                                                                                                                [ FAIL ]
Stopping NFS mountd...                                                                                                                              [  OK  ]
Refreshing NFS Exported Filesystems...                                                                                                              [  OK  ]
Unmounting NFS Virtual Filesystem...                                                                                                                [  OK  ]
Removing the rpc.statd pid file if it exists
Starting NFS mountd...                                                                                                                              [  OK  ]
Starting NFS nfsd...                                                                                                                                [  OK  ]
Starting NFS statd...                                                                                                                               [  OK  ]
Mounting nfsd virtual filesystem...
mount: none is already mounted or /proc/fs/nfsd busy
       none is already mounted on /var/log/rrd                                                                                                      [ FAIL ]


Hat jemand eine Idee, wie ich das NFS wieder zum Laufen bekomme?

Auf der Zielmaschine erscheint beim Mouten folgende Fehlermeldung:

Code: Select all
mount.nfs: access denied by server while mounting 192.168.2.1:/mnt/harddisk


Das Logfile der ipFire schreibt folgende Fehlermeldungen:

Code: Select all
12:56:38   kernel:    nfsd: last server has exited, flushing export cache
12:57:53   kernel:    svc: failed to register lockdv1 RPC service (errno 97).
12:57:53   kernel:    NFSD: the nfsdcld client tracking upcall will be removed in 3.10. Please transit ion to using nfsdcltrack.
12:57:53   kernel:    NFSD: starting 90-second grace period (net c0d99640)
12:59:53   kernel:    NFSD: Unable to end grace period: -110
13:01:38   kernel:    nfsd: last server has exited, flushing export cache
13:01:41   kernel:    svc: failed to register lockdv1 RPC service (errno 97).
13:01:41   kernel:    NFSD: the nfsdcld client tracking upcall will be removed in 3.10. Please transit ion to using nfsdcltrack.
13:01:41   kernel:    NFSD: starting 90-second grace period (net c0d99640)
13:03:41   kernel:    NFSD: Unable to end grace period: -110


Vielen Dank!
Comment 1 Jonatan Schlag 2016-04-17 14:05:21 UTC
Please post this in English, again, otherwise the bug report will deleted.

Regards Jonatan
Comment 2 Michael Tremer 2016-04-17 14:16:50 UTC

*** This bug has been marked as a duplicate of bug 10788 ***
Comment 3 lars.seidler 2016-04-17 16:44:09 UTC
Hello,

since Upgrade to Core 100 nfs-server isn't working anymore. 
If I try to start it with

/etc/init.d/nfs-server restart
the following error occurs:

[root@ipfire init.d]# ./nfs-server restart
 Stopping NFS statd...                                                       
 [  OK  ]
 Stopping NFS nfsd...                                                        
 [ FAIL ]
 Stopping NFS mountd...                                                      
 [  OK  ]
 Refreshing NFS Exported Filesystems...                                      
 [  OK  ]
 Unmounting NFS Virtual Filesystem...                                        
 [  OK  ]
 Removing the rpc.statd pid file if it exists
 Starting NFS mountd...                                                      
 [  OK  ]
 Starting NFS nfsd...                                                        
 [  OK  ]
 Starting NFS statd...                                                       
 [  OK  ]
 Mounting nfsd virtual filesystem...
 mount: none is already mounted or /proc/fs/nfsd busy
        none is already mounted on /var/log/rrd                              
 [ FAIL ]
 
 
On the target machine, the following error occurs: 


 mount.nfs: access denied by server while mounting 192.168.2.1:/mnt/harddisk
 
 
The logfile at the ipFire contains: 
 12:56:38   kernel:    nfsd: last server has exited, flushing export cache
 12:57:53   kernel:    svc: failed to register lockdv1 RPC service (errno 97).
 12:57:53   kernel:    NFSD: the nfsdcld client tracking upcall will be
 removed in 3.10. Please transit ion to using nfsdcltrack.
 12:57:53   kernel:    NFSD: starting 90-second grace period (net c0d99640)
 12:59:53   kernel:    NFSD: Unable to end grace period: -110
 13:01:38   kernel:    nfsd: last server has exited, flushing export cache
 13:01:41   kernel:    svc: failed to register lockdv1 RPC service (errno 97).
 13:01:41   kernel:    NFSD: the nfsdcld client tracking upcall will be
removed in 3.10. Please transit ion to using nfsdcltrack.
 13:01:41   kernel:    NFSD: starting 90-second grace period (net c0d99640)
 13:03:41   kernel:    NFSD: Unable to end grace period: -110
Comment 4 dini 2016-04-17 17:43:27 UTC
Hello,

I have the same problem since upgrade from 99 to 100.
Comment 5 dini 2016-04-17 17:49:35 UTC
(In reply to dini from comment #4)
> Hello,
> 
> I have the same problem since upgrade from 99 to 100.

When i restart the nfs server
i got this on /var/log/messages

Apr 17 17:39:48 ipfire dhcpd: DHCPREQUEST for 172.16.0.78 from 00:0a:f5:d9:80:d4 () via blue0
Apr 17 17:39:48 ipfire dhcpd: DHCPACK on 172.16.0.78 to 00:0a:f5:d9:80:d4 () via blue0
Apr 17 17:39:49 ipfire dnsmasq[3072]: reading /var/state/dhcp/dhcpd.leases
Apr 17 17:40:50 ipfire kernel: nfsd: last server has exited, flushing export cache
Apr 17 17:40:51 ipfire rpc.mountd[26960]: Caught signal 15, un-registering and exiting.
Apr 17 17:40:53 ipfire rpc.mountd[25100]: Kernel does not have pseudo root support.
Apr 17 17:40:53 ipfire rpc.mountd[25100]: NFS v4 mounts will be disabled unless fsid=0
Apr 17 17:40:53 ipfire rpc.mountd[25100]: is specfied in /etc/exports file.
Apr 17 17:40:53 ipfire rpc.mountd[25101]: Version 1.2.7 starting
Apr 17 17:40:53 ipfire kernel: svc: failed to register lockdv1 RPC service (errno 97).
Apr 17 17:40:53 ipfire kernel: NFSD: the nfsdcld client tracking upcall will be removed in 3.10. Please transition to using nfsdcltrack.
Apr 17 17:40:53 ipfire kernel: NFSD: starting 90-second grace period (net c0d99640)
Apr 17 17:40:53 ipfire rpc.statd[25127]: Version 1.2.7 starting
Apr 17 17:40:53 ipfire sm-notify[25128]: Version 1.2.7 starting
Apr 17 17:40:53 ipfire sm-notify[25128]: Already notifying clients; Exiting!
Apr 17 17:40:53 ipfire rpc.statd[25127]: Running as root.  chown /var/lib/nfs to choose different user
Comment 6 Jonatan Schlag 2016-04-17 18:52:18 UTC
Hi,
this bug report is closed.
Please report everything in the new bug report
https://bugzilla.ipfire.org/show_bug.cgi?id=11098

Thanks.

Regards Jonatan
Comment 7 Arne.F 2016-04-24 21:40:52 UTC

*** This bug has been marked as a duplicate of bug 11098 ***