public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Tom H <tomh0665@gmail.com>
To: Gentoo User <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] [~amd64] NFS server broken again :(
Date: Mon, 27 Oct 2014 20:56:45 -0400	[thread overview]
Message-ID: <CAOdo=SzXCtdVnznSLtQYP8=7RU5+e9f=GxazZaR+EyD44ipskw@mail.gmail.com> (raw)
In-Reply-To: <m2m6v8$v8$1@ger.gmane.org>

On Mon, Oct 27, 2014 at 3:38 PM, walt <w41ter@gmail.com> wrote:
>
> Last night when I powered off my machines NFS was working perfectly.  Today
> it's broken again for the nth time:
>
> #systemctl status nfs-server
> ● nfs-server.service - NFS server and services
>    Loaded: loaded (/usr/lib64/systemd/system/nfs-server.service; enabled)
>    Active: failed (Result: exit-code) since Mon 2014-10-27 11:50:38 PDT; 25min ago
>   Process: 896 ExecStopPost=/usr/sbin/exportfs -f (code=exited, status=0/SUCCESS)
>   Process: 893 ExecStopPost=/usr/sbin/exportfs -au (code=exited, status=0/SUCCESS)
>   Process: 939 ExecStart=/usr/sbin/rpc.nfsd $RPCNFSDARGS (code=exited, status=1/FAILURE)
>   Process: 936 ExecStartPre=/usr/sbin/exportfs -r (code=exited, status=0/SUCCESS)
>  Main PID: 939 (code=exited, status=1/FAILURE)
>
> Oct 27 11:50:38 a6 rpc.nfsd[939]: rpc.nfsd: writing fd to kernel failed: errno 111 (Connection refused)
> Oct 27 11:50:38 a6 rpc.nfsd[939]: rpc.nfsd: unable to set any sockets for nfsd
> Oct 27 11:50:38 a6 systemd[1]: nfs-server.service: main process exited, code=exited, status=1/FAILURE
> Oct 27 11:50:38 a6 systemd[1]: Failed to start NFS server and services.
> Oct 27 11:50:38 a6 systemd[1]: Unit nfs-server.service entered failed state.
>
> #rpc.nfsd -d
> rpc.nfsd: Checking netconfig for visible protocols.
> rpc.nfsd: Enabling inet udp.
> rpc.nfsd: Enabling inet tcp.
> rpc.nfsd: Enabling inet6 udp.
> rpc.nfsd: Enabling inet6 tcp.
> rpc.nfsd: knfsd is currently down
> rpc.nfsd: Writing version string to kernel: -2 +3 +4
> rpc.nfsd: Creating inet TCP socket.
> rpc.nfsd: writing fd to kernel failed: errno 111 (Connection refused)
> rpc.nfsd: Creating inet6 TCP socket.
> rpc.nfsd: writing fd to kernel failed: errno 97 (Address family not supported by protocol)
> rpc.nfsd: unable to set any sockets for nfsd

Is rpcbind.service running?

Does "rpcbind -p" output the usual programs/ports/...?

Are the nfs-api-filesystems mounted? ("/var/lib/nfs/rpc_pipefs" and
"/proc/fs/nfsd")


      parent reply	other threads:[~2014-10-28  0:56 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-27 19:38 [gentoo-user] [~amd64] NFS server broken again :( walt
2014-10-27 19:56 ` Canek Peláez Valdés
2014-10-27 23:46   ` [gentoo-user] " walt
2014-10-28  1:05     ` Canek Peláez Valdés
2014-10-28  2:49     ` Tom H
2014-10-28  3:22       ` Tom H
2014-10-28 22:18         ` walt
2014-10-29  1:36           ` Tom H
2014-10-29  1:50             ` Rich Freeman
2014-10-31 17:34               ` Tom H
2014-10-31 18:27                 ` Rich Freeman
2014-10-31 23:01                   ` Tom H
2014-10-31 23:52                     ` Rich Freeman
2014-11-03  1:37                       ` Tom H
2014-11-03  3:47                         ` Rich Freeman
2014-11-01  3:18                     ` Jc García
2014-10-28  0:56 ` Tom H [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAOdo=SzXCtdVnznSLtQYP8=7RU5+e9f=GxazZaR+EyD44ipskw@mail.gmail.com' \
    --to=tomh0665@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox