All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rogier Wolff <R.E.Wolff@BitWizard.nl>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: chuck.lever@oracle.com, linux-nfs@vger.kernel.org
Subject: Re: Lockd error message is unclear.
Date: Tue, 27 Apr 2021 23:10:44 +0200	[thread overview]
Message-ID: <20210427211044.vxvgieqe4ud5lh7o@BitWizard.nl> (raw)
In-Reply-To: <20210427193452.GA11361@fieldses.org>

On Tue, Apr 27, 2021 at 03:34:52PM -0400, J. Bruce Fields wrote:
> On Tue, Apr 27, 2021 at 09:03:11PM +0200, Rogier Wolff wrote:
> > 
> > Hi, 
> > 
> > Two things..... 
> > 
> > I got: 
> > 
> >    lockd: cannot monitor <client> 
> > 
> > in the logfile and the client was terrily slow/not working at all.
> > 
> > everything pointed to a lockd problem... 
> > 
> > In the end... it turns out that my rpc.statd stopped working.  I had
> > to go and download the sources to figure this out... I would firstly
> > suggest to improve the error message to give others running into this
> > more hints as to where to look.
> > 
> > The erorr message on line 169 of lockd.c could read: 
> > 
> > 	lockd: Error in the rpc to rpc.statd to monitor %s\n
> > 
> > Would it be an idea to print the res.status error code? 
> 
> I'm not sure about the wording, but including the error code sounds like
> a good idea.  (Would that have made a difference in your case?)

Not sure. Of course I was just "looking for a solution". So once I
figured out that rpc.statd was missing I went looking for how that
came about. 

But as it was the prime culprit was "lockd is misbehaving". With a
better error message you can shift the blame away from your part of
the system. :-)

> > second?) timeout in nsm_mon_unmon and the big backlog of requests that
> > result in the same call and timeout that frustrate the client... )
> 
> The -ECONNREFUSED case?
> 
> I'm not sure why it retries there.  Maybe just to allow stopping and
> starting rpc.statd (e.g. for upgrades) without failing operations?

Not sure IF it was retrying. Maybe not. But starting "google-chrome"
with 40 open tabs didn't progress to any tabs loading inside the half
hour that I was looking for why this was happening (unable to google
for a solution).... So in the meantime it was constantly spewing the
error message, rate limited to 10 per minute....

	Roger.

-- 
** R.E.Wolff@BitWizard.nl ** https://www.BitWizard.nl/ ** +31-15-2049110 **
**    Delftechpark 11 2628 XJ  Delft, The Netherlands.  KVK: 27239233    **
f equals m times a. When your f is steady, and your m is going down
your a is going up.  -- Chris Hadfield about flying up the space shuttle.

      reply	other threads:[~2021-04-27 21:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-27 19:03 Lockd error message is unclear Rogier Wolff
2021-04-27 19:34 ` J. Bruce Fields
2021-04-27 21:10   ` Rogier Wolff [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=20210427211044.vxvgieqe4ud5lh7o@BitWizard.nl \
    --to=r.e.wolff@bitwizard.nl \
    --cc=bfields@fieldses.org \
    --cc=chuck.lever@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.