🛈 Aktuell gibt es im Wiki ca. 750 Artikel, die nur für Xenial getestet sind. Dies entspricht ca. 10 % aller Wikiartikel. Damit diese im nächsten Frühjahr nicht alle archiviert werden müssen, ist eure Mithilfe gefragt!
Setting up an nfs server on a laptop running Fedora-20, I get the following perplexing results: # systemctl start nfs.service # systemctl enable nfs.service Failed to issue method call: No such file or directory Sure enough, as promised, nfs works up to the next reboot, then it stops working. Check your mounts, then restart the NFS server. – Thomas May 17 '19 at 7:16 That was the problem for some reason I forgot to add that the raid-array to auto-mount at boot. – swemattias May 18 '19 at 9:24.
NFS Server startet wohl nicht.
Antworten |
29. November 2017 18:14 Hallo, ich bekomme nachfolgende Fehlermeldungen: Hat jemand eine ahnung was das zu bedeuten hat ? ByeMarcus |
29. November 2017 18:43 In einer VM startete der nfs-server ohne Probleme automatisch. Hier mit einem: werden die Freigaben geladen. Wie kann ich den nsf-server automatisch am besten starten ? |
29. November 2017 18:59 Jetzt bekomme ich folgende Fehlermeldung |
29. November 2017 19:13 Nach dem Booten, startet jetzt der Server automatisch, warum auch immer.Die Freigaben werden gemountet, aber ein reload des Servers geht immer noch nicht.Ist jetzt aber erstmal nicht so wichtig. ByeMarcus |
29. November 2017 22:25 Was sagen die Logs? |
30. November 2017 07:01 |
30. November 2017 19:14 |
30. November 2017 19:55 Danke. Der zweite Log ist sehr lang. Den Poste ich mal am Wochenende nach einem frischen Neustart. |
30. November 2017 20:02 (zuletzt bearbeitet: 30. November 2017 20:03) Nach systemctl status nfs-server.service: Contoh program dengan visual foxpro 9.0. Das Ende von journalctl -xe |
30. November 2017 20:10 Folgendes fällt auf:systemctl status nfs-server.service: Zeile 12: z.I: |
30. November 2017 20:22 Was ist /export/marcus genau, also welches Dateisystem? mfg Stefan |
30. November 2017 20:46 /home/Marcus ist verschlüsselt. Das war bisher aber nie ein Problem für Ubuntu 17.04 und früher. |
30. November 2017 20:50 So, und was genau ist /home? Weil bind Mounts sind ja für NFSv4 der Standard, und wie sieht überhaupt deine /etc/exports aus? mfg Stefan |
30. November 2017 21:03 Was meinst du mit was ist /home ? |
30. November 2017 21:07 Ist /home ein extra Dateisystem? Läuft auf /home eine Verschlüsselung? Nach dem Restart vom NFS Server ging es ja, oder? mfg Stefan |
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines
Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#43647 - [nfs-utils] nfs-server fails to start
Opened by Gene (GeneC) - Saturday, 31 January 2015, 21:43 GMT
Last edited by Andreas Radke (AndyRTR) - Saturday, 18 April 2015, 07:38 GMT
| DetailsDescription: nfs-server fails to start Additional info: Similar problems noted last year here: https://lists.archlinux.org/pipermail/arch-general/2014-June/036617.html Today after reboot nfs-server was not running: 2 units fail to start rpc-statd.service nfs-server.service. ------------------------------------- rpc-statd: systemctl status rpc-statd rpc.statd[736]: Version 1.3.2 starting rpc.statd[736]: Flags: TI-RPC rpc.statd[736]: Running as root. chown /var/lib/nfs to choose different user rpc.statd[736]: failed to create RPC listeners, exiting systemd[1]: rpc-statd.service: control process exited, code=exited status=1 systemd[1]: Failed to start NFS status monitor for NFSv2/3 locking. systemd[1]: Unit rpc-statd.service entered failed state. systemd[1]: rpc-statd.service failed. ------------------------------------- I am unable to start this by hand either - continues to fail same way. I had seen this once a month or so back - but was able to start it by hand after machine was up. ------------------------------------- nfs-server: systemctl-status nfs-server ● nfs-server.service - NFS server and services Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Sat 2015-01-31 16:05:32 EST; 5min ago Process: 743 ExecStart=/usr/sbin/rpc.nfsd $RPCNFSDARGS (code=exited, status=1/FAILURE) Process: 741 ExecStartPre=/usr/sbin/exportfs -r (code=exited, status=0/SUCCESS) Main PID: 743 (code=exited, status=1/FAILURE) rpc.nfsd[743]: rpc.nfsd: writing fd to kernel failed: errno 111 (Connection refused) rpc.nfsd[743]: rpc.nfsd: unable to set any sockets for nfsd systemd[1]: nfs-server.service: main process exited, code=exited, status=1/FAILURE systemd[1]: Failed to start NFS server and services. systemd[1]: Unit nfs-server.service entered failed state. systemd[1]: nfs-server.service failed. ------------------------------------- Machine is fully updated from testing repo. I did try kernel 3.19.rc6 but it does not help. Going over the bug from June 2014 I tried these: systemctl restart proc-fs-nfsd.mount systemctl restart rpcbind systemctl restart nfs-mountd.service systemctl restart rpc-statd.service systemctl restart nfs-idmapd.service systemctl restart rpc-svcgssd.service systemctl restart rpc-statd-notify.service systemctl restart nfs-mountd systemctl restart rpc-gssd.service rpc-svcgssd.service rpc-statd still does not start but now . it failes with rpc-statd.service start operation timed out. Terminating. Trying to start nfs-server - it too 'times out' After 5 mins i tried again: systemctl start nfs-server which now starts .. rpc-statd is still not running. And the server is once again serving NFS. * package version(s) nfs-utils 1.3.2-1 linux 3.18.5-1 rpcbind 0.2.2-1 * config and/or log files etc. Steps to reproduce: |
Danke.
Der zweite Log ist sehr lang. Den Poste ich mal am Wochenende nach einem frischen Neustart.
Nach
systemctl status nfs-server.service:
Contoh program dengan visual foxpro 9.0. Das Ende von journalctl -xe
Folgendes fällt auf:systemctl status nfs-server.service: Zeile 12:
z.I:
Was ist /export/marcus genau, also welches Dateisystem?
mfg Stefan
/home/Marcus ist verschlüsselt. Das war bisher aber nie ein Problem für Ubuntu 17.04 und früher.
So, und was genau ist /home? Weil bind Mounts sind ja für NFSv4 der Standard, und wie sieht überhaupt deine /etc/exports aus?
mfg Stefan
Was meinst du mit was ist /home ?
Ist /home ein extra Dateisystem? Läuft auf /home eine Verschlüsselung? Nach dem Restart vom NFS Server ging es ja, oder?
mfg Stefan
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines
Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#43647 - [nfs-utils] nfs-server fails to start
Opened by Gene (GeneC) - Saturday, 31 January 2015, 21:43 GMT
Last edited by Andreas Radke (AndyRTR) - Saturday, 18 April 2015, 07:38 GMT
| DetailsDescription: nfs-server fails to start Additional info: Similar problems noted last year here: https://lists.archlinux.org/pipermail/arch-general/2014-June/036617.html Today after reboot nfs-server was not running: 2 units fail to start rpc-statd.service nfs-server.service. ------------------------------------- rpc-statd: systemctl status rpc-statd rpc.statd[736]: Version 1.3.2 starting rpc.statd[736]: Flags: TI-RPC rpc.statd[736]: Running as root. chown /var/lib/nfs to choose different user rpc.statd[736]: failed to create RPC listeners, exiting systemd[1]: rpc-statd.service: control process exited, code=exited status=1 systemd[1]: Failed to start NFS status monitor for NFSv2/3 locking. systemd[1]: Unit rpc-statd.service entered failed state. systemd[1]: rpc-statd.service failed. ------------------------------------- I am unable to start this by hand either - continues to fail same way. I had seen this once a month or so back - but was able to start it by hand after machine was up. ------------------------------------- nfs-server: systemctl-status nfs-server ● nfs-server.service - NFS server and services Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Sat 2015-01-31 16:05:32 EST; 5min ago Process: 743 ExecStart=/usr/sbin/rpc.nfsd $RPCNFSDARGS (code=exited, status=1/FAILURE) Process: 741 ExecStartPre=/usr/sbin/exportfs -r (code=exited, status=0/SUCCESS) Main PID: 743 (code=exited, status=1/FAILURE) rpc.nfsd[743]: rpc.nfsd: writing fd to kernel failed: errno 111 (Connection refused) rpc.nfsd[743]: rpc.nfsd: unable to set any sockets for nfsd systemd[1]: nfs-server.service: main process exited, code=exited, status=1/FAILURE systemd[1]: Failed to start NFS server and services. systemd[1]: Unit nfs-server.service entered failed state. systemd[1]: nfs-server.service failed. ------------------------------------- Machine is fully updated from testing repo. I did try kernel 3.19.rc6 but it does not help. Going over the bug from June 2014 I tried these: systemctl restart proc-fs-nfsd.mount systemctl restart rpcbind systemctl restart nfs-mountd.service systemctl restart rpc-statd.service systemctl restart nfs-idmapd.service systemctl restart rpc-svcgssd.service systemctl restart rpc-statd-notify.service systemctl restart nfs-mountd systemctl restart rpc-gssd.service rpc-svcgssd.service rpc-statd still does not start but now . it failes with rpc-statd.service start operation timed out. Terminating. Trying to start nfs-server - it too 'times out' After 5 mins i tried again: systemctl start nfs-server which now starts .. rpc-statd is still not running. And the server is once again serving NFS. * package version(s) nfs-utils 1.3.2-1 linux 3.18.5-1 rpcbind 0.2.2-1 * config and/or log files etc. Steps to reproduce: |
Saturday, 18 April 2015, 07:38 GMT
Reason for closing: Fixed
Job For Nfs-server.service Canceled. Ubuntu
|
