All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sachin Prabhu <sachin.prabhu@gmail.com>
To: Steve French <smfrench@gmail.com>
Cc: CIFS <linux-cifs@vger.kernel.org>
Subject: Re: cifs.upcall debugging
Date: Thu, 29 Sep 2022 23:13:07 +0100	[thread overview]
Message-ID: <CAKbxtwS4K+9mmAwgCxzDOwDK=pW_mXeGO252VvfwnHpGcEynOA@mail.gmail.com> (raw)
In-Reply-To: <CAH2r5muXa4pn4EYcW6quTgn1o++o6DYxAckpT9=CsRmcPKGL7w@mail.gmail.com>

Hello Steve,

Good to hear from you. I will consider what parts should be added to
the wiki. It has been so long since I've debugged this part, that I
need to refresh my memory before I can give you a good answer.

get_tgt_time: unable to get principal

The strace for the cifs.upcall helper is available at
http://sprabhu.blogspot.com/2014/12/debugging-calls-to-cifsupcall.html
The debug logging for the cifs.upcall is pretty good and if you can
see the debug output, you can get a pretty good idea. If not, the
strace will show where it fails in obtaining the tgt and usually
contains the debug messages from the cifs.upcall.

Sachin Prabhu

On Thu, 29 Sept 2022 at 05:43, Steve French <smfrench@gmail.com> wrote:
>
> This had should useful things about cifs.upcall (and an earlier one
> about debugging cifs.upcall problems e.g. with krb5 mounts returning
> errors)
>
> http://sprabhu.blogspot.com/2019/06/howto-cifs-kerberos-mount.html
>
> Shouldn't some of the cifs.upcall debugging info mentioned in an
> earlier blog post be also added to wiki.samba.org ? e.g.
>
> http://wiki.samba.org/index.php/LinuxCIFS_troubleshooting
>
> Any suggestions on how to debug cases where klist shows the principal
> but cifs.upcall can't find it - see log entry:
>
> get_tgt_time: unable to get principal
>
> --
> Thanks,
>
> Steve

      reply	other threads:[~2022-09-29 22:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-29  4:42 cifs.upcall debugging Steve French
2022-09-29 22:13 ` Sachin Prabhu [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='CAKbxtwS4K+9mmAwgCxzDOwDK=pW_mXeGO252VvfwnHpGcEynOA@mail.gmail.com' \
    --to=sachin.prabhu@gmail.com \
    --cc=linux-cifs@vger.kernel.org \
    --cc=smfrench@gmail.com \
    /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.