k5_mutex_lock: Received error 22 (Invalid argument)

[Benjamin Kaduk]

Hello,

I do not believe this is a known issue.
The place that generates that diagnostic assert()s on failure, so hopefully
you have one or more core dumps available.  The backtrace from the dump
(ideally with line numbers in libkrb5support, but even without) would be a
great place to start.

Thanks,

Ben

On Sat, Oct 31, 2020 at 02:19:21AM +0000, moore moore wrote:
> Hello,
> I have a system using krb5-1.17 in a linux pthread multi threaded application acting as a proxy for many (1000s) clients using constrained delegation to webservices.TGT, TGS and AP are all working fine.
> Under high thread concurrency it would appear ( ~ 200 threads ) and generally around ticket expiry/renewal, the following errors occur.
> k5_mutex_lock: Received error 22 (Invalid argument)proxy_app: ../../../include/k5-thread.h:376: k5_mutex_lock: Assertion `r == 0' failed.k5_mutex_lock: Received error 22 (Invalid argument)k5_mutex_lock: Received error 22 (Invalid argument)k5_mutex_lock: Received error 22 (Invalid argument)proxy_app: ../../../include/k5-thread.h:376: k5_mutex_lock: Assertion `r == 0' failed.proxy_app: ../../../include/k5-thread.h:376: k5_mutex_lock: Assertion `r == 0' failed.
> Is this a known issue? if not, I would be happy to try troubleshoot, patch and test with your guidance, suggestion.
> Thank you.
> _______________________________________________
> krbdev mailing list             krbdev at mit.edu
> https://mailman.mit.edu/mailman/listinfo/krbdev