#2002 cc_residual_is_used might not work correctly with dircache
Closed: Fixed None Opened 9 years ago by jhrozek.

We have a check to see if ccache is already used or not. But after some recent changes, I see errors in the logs:

[sssd[be[AD.EXAMPLE.COM]]] [cc_residual_is_used] (0x1000): User [1983201109]
is still active, reusing ccache [/run/user/1983201109].
[sssd[be[AD.EXAMPLE.COM]]] [cc_residual_is_used] (0x0200): Cache file
[/run/user/1983201109/primary] does not exist, it will be recreated
  This path cannot exist, I think SSSD should be checking for
  /run/user/1983201109/krb5cc/primary instead

[sssd[be[AD.EXAMPLE.COM]]] [check_for_valid_tgt] (0x0020): krb5_cc_retrieve_cred failed.

Seems like we were still assuming a patch to a file, so we're truncating the last part with dirname()

Logins are still working and existing ccaches are reused, so it might just be a false warning.

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.10.1
rhbz: => 0

Fields changed

patch: 0 => 1
status: new => assigned

Fields changed

cc: => tibbs

resolution: => fixed
status: assigned => closed

Metadata Update from @jhrozek:
- Issue assigned to lslebodn
- Issue set to the milestone: SSSD 1.10.1

5 years ago

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/3044

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.