linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: hce <webmail.hce@gmail.com>
To: linux-nfs@vger.kernel.org
Subject: Re: shutting down socket
Date: Fri, 6 Aug 2010 16:29:03 +1000	[thread overview]
Message-ID: <AANLkTiny1SXAzZSenaGwjdkWwE3Fs7eXXBtsB=RcD7kY@mail.gmail.com> (raw)
In-Reply-To: <AANLkTik_awWoER22GmhYeJw2cN4GoJe1Gj7SCVetMzte@mail.gmail.com>

Hi,

I am running kernel 2.6.18. I searched from Internet and found
different views regarding to the error of "rpc-srv/tcp: nfsd: got
error -32 when sending 36 bytes - shutting down socket". Some say it
could be kernel bug (I am running kernel 2.6.18) and some said it
could be distribution package bug (I am running CentOS 5).

One view was that error could be caused by insufficient nfsd
resources. In normal operation, I have following statistics. Does that
implies it needs to increase number of nfsd?

th 8 2311379 141.373 7.943 8.199 0.000 10.755 10.693 10.615 96.889 0.000 946.537

Thank you.

Kind regards





On Wed, Aug 4, 2010 at 2:31 PM, hce <webmail.hce@gmail.com> wrote:
> Hi,
>
> I am running a networking application on CentOS 5, it got a SIGTERM
> and the application terminated. I looked at dmesg file and found
> following an error:
>
> rpc-srv/tcp: nfsd: got error -32 when sending 36 bytes - shutting down socket
>
> Could that error result a SIGTERM? If yes, what could possibly cause
> the nfsd error to shut down the socket?
>
> Thank you.
>
> hce
>

      reply	other threads:[~2010-08-06  6:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-04  4:31 shutting down socket hce
2010-08-06  6:29 ` hce [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='AANLkTiny1SXAzZSenaGwjdkWwE3Fs7eXXBtsB=RcD7kY@mail.gmail.com' \
    --to=webmail.hce@gmail.com \
    --cc=linux-nfs@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).