Bug#918088: Acknowledgement (autofs-ldap: automount dies with SIGABRT after libkrb5-3 upgrade - "(k5_mutex_lock: Assertion `r == 0' failed.)")

2019-01-05 Thread Greg Hudson
On Fri, 4 Jan 2019 19:24:52 -0500 Greg Hudson wrote: > krb5_mcc_start_seq_get() is in the traceback, so the memory cache change > is a clear candidate for the bug. I can't find anything wrong with the > code, though. From the stack trace, there appears to be a memory ccache > on the list with an

Bug#918088: Acknowledgement (autofs-ldap: automount dies with SIGABRT after libkrb5-3 upgrade - "(k5_mutex_lock: Assertion `r == 0' failed.)")

2019-01-05 Thread Adrian Bunk
On Fri, Jan 04, 2019 at 09:00:01PM -0500, Sam Hartman wrote: > > "Adrian" == Adrian Bunk writes: > > latest upgrade of libkrb5-3 (1.16.1-1 -> 1.16.2-1) > >> automount starts but dies immediately after accessing a > >> automounter point. > >> > >> Automount is configured to au

Bug#918088: Acknowledgement (autofs-ldap: automount dies with SIGABRT after libkrb5-3 upgrade - "(k5_mutex_lock: Assertion `r == 0' failed.)")

2019-01-05 Thread Andreas Maus
Hi Sam. On Sat Jan 05, 2019 at 08:12:16AM -0500, Sam Hartman wrote: > I'd value the autofs configuration much more than the directory setup > instructions. You want it? You get it! ;) autofs.conf: root@dagon:~# cat /etc/autofs.conf # Managed by ansible [autofs] browse_mode = False entry_object_

Bug#918088: Acknowledgement (autofs-ldap: automount dies with SIGABRT after libkrb5-3 upgrade - "(k5_mutex_lock: Assertion `r == 0' failed.)")

2019-01-05 Thread Sam Hartman
I'd value the autofs configuration much more than the directory setup instructions. I have no desire to go install centos7 to debug a Debian bug:-) and have some familiarity with setting up LDAP. What I don't have is familiarity configuring autofs.

Bug#918088: Acknowledgement (autofs-ldap: automount dies with SIGABRT after libkrb5-3 upgrade - "(k5_mutex_lock: Assertion `r == 0' failed.)")

2019-01-05 Thread Andreas Maus
On Fri Jan 04, 2019 at 21:00:01PM -0500, Sam Hartman wrote: > > "Adrian" == Adrian Bunk writes: > > latest upgrade of libkrb5-3 (1.16.1-1 -> 1.16.2-1) > >> automount starts but dies immediately after accessing a > >> automounter point. > >> > >> Automount is configured to aut

Bug#918088: Acknowledgement (autofs-ldap: automount dies with SIGABRT after libkrb5-3 upgrade - "(k5_mutex_lock: Assertion `r == 0' failed.)")

2019-01-04 Thread Sam Hartman
> "Adrian" == Adrian Bunk writes: latest upgrade of libkrb5-3 (1.16.1-1 -> 1.16.2-1) >> automount starts but dies immediately after accessing a >> automounter point. >> >> Automount is configured to authenticate via GSSAPI using system >> keytab. After the GSSAPI authent

Bug#918088: Acknowledgement (autofs-ldap: automount dies with SIGABRT after libkrb5-3 upgrade - "(k5_mutex_lock: Assertion `r == 0' failed.)")

2019-01-04 Thread Greg Hudson
On Fri, 04 Jan 2019 15:54:01 -0500 Sam Hartman wrote: > There are no thread support changes between 1.16.1 and 1.16.2. > There is one ccache related change which I'll include below related to > memory ccaches. > Do you know what type of credential cache is being used here? krb5_mcc_start_seq_get

Bug#918088: Acknowledgement (autofs-ldap: automount dies with SIGABRT after libkrb5-3 upgrade - "(k5_mutex_lock: Assertion `r == 0' failed.)")

2019-01-04 Thread Sam Hartman
So what's happening here is that a k5_mutex_lock is getting an invalid argument error calling a series of wrappers that basically all boil down to pthread_mutex_lock. So, basically somehow pthread_mutex_lock is getting passed a bad mutex. This appears to be happening in the credentials cache cod

Bug#918088: Acknowledgement (autofs-ldap: automount dies with SIGABRT after libkrb5-3 upgrade - "(k5_mutex_lock: Assertion `r == 0' failed.)")

2019-01-04 Thread Adrian Bunk
Control: reassign -1 libkrb5-3 1.16.2-1 Control: affects -1 autofs-ldap > After the latest upgrade of libkrb5-3 (1.16.1-1 -> 1.16.2-1) automount > starts but dies immediately after accessing a automounter point. > > Automount is configured to authenticate via GSSAPI using system keytab. > After t

Bug#918088: Acknowledgement (autofs-ldap: automount dies with SIGABRT after libkrb5-3 upgrade - "(k5_mutex_lock: Assertion `r == 0' failed.)")

2019-01-03 Thread Andreas Maus
Maybe the backtrace with libkrb5-dbg installed may provider more clues: root@dagon:~# gdb /usr/sbin/automount /core GNU gdb (Debian 8.2-1) 8.2 Copyright (C) 2018 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you