Job For Nfs Server.service Canceled.

  1. Job For Nfs-server.service Canceled Fedora
  2. Job For Nfs-server.service Canceled. Ubuntu
  3. Job For Nfs-server.service Canceled
Please read this before reporting a bug:
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!
Job For Nfs Server.service Canceled.Tasklist

Job For Nfs-server.service Canceled Fedora

Job

FS#43647 - [nfs-utils] nfs-server fails to start

Client for nfs service

I'm trying to get nfs working on an Ubuntu 16.04.2 LTS. I get the following error: I've already tried reinstalling nfs-common, nfs-kernel-server and other packages following instructions provided in. Jul 20 08:52:09 Ubuntu-mate systemd1: Job nfs-server.service/start failed with result 'dependency'. Jul 20 08:52:09 Ubuntu-mate systemd1: Unit proc-fs-nfsd.mount entered failed state. Jul 20 08:52:09 Ubuntu-mate systemd1: nfs-idmapd.service: control process exited, code=exited status=1 Jul 20 08:52:09 Ubuntu-mate systemd1: Unit nfs. Systemd1: Unit nfs-server.service entered failed state. Systemd1: 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. As far as i can see there must be some sort of connection limits for the nfs server or something i have exhausted all ideas and resources trying to figure this out. After googling for a few days now i cant seam to find any settings or limitations of the nfs server itself so how can i add the other 5 nodes to my cluster.

Job For Nfs-server.service Canceled. Ubuntu

Attached to Project: Arch Linux
Opened by Gene (GeneC) - Saturday, 31 January 2015, 21:43 GMT
Last edited by Andreas Radke (AndyRTR) - Saturday, 18 April 2015, 07:38 GMT
Task TypeBug Report
Category Packages: Testing
Status Closed
Assigned ToTobias Powalowski (tpowa)
Architecturex86_64
SeverityHigh
PriorityNormal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete
Votes6
  • Alexandre de Verteuil (a_neutrino) (2015-02-23)
  • Michael (Zeth) (2015-02-17)
  • Markus N. (Markus.N) (2015-02-17)
  • Jason S. Wagner (jswagner) (2015-02-16)
  • Mike Cloaked (mcloaked) (2015-01-31)
  • Gene (GeneC) (2015-01-31)
Private No

Details

Description: 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:
Client for nfs service

Job For Nfs-server.service Canceled

Closed by Andreas Radke (AndyRTR)
Saturday, 18 April 2015, 07:38 GMT
Reason for closing: Fixed
Duplicate tasks of this task (0)