Percona Auth Pam crashing MySQL

[Derek Rasmussen]

The last two weeks on Monday mornings, Percona has restarted itself with the below stack trace and appears to be due to the percona auth pam plugin. Any help with this would be appreciated.

Server: Debian Jessie
uname -a
Linux sdsdb3 3.16.0-4-amd64 #1 SMP Debian 3.16.43-2+deb8u2 (2017-06-26) x86_64 GNU/Linux

dpkg -l | grep percona
ii percona-release 0.1-4.jessie
ii percona-server-client-5.7 5.7.18-16-1.jessie
ii percona-server-common-5.7 5.7.18-16-1.jessie
ii percona-server-server-5.7 5.7.18-16-1.jessie

14:02:17 UTC - mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.
Please help us make Percona Server better by reporting any
bugs at http://bugs.percona.com/

key_buffer_size=8388608
read_buffer_size=2097152
max_used_connections=1370
max_threads=5001
thread_count=419
connection_count=419
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 51278596 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7f3d3efa2140
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 7f440b163e80 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x2c)[0xe8daac]
/usr/sbin/mysqld(handle_fatal_signal+0x479)[0x79a349]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f792051c890]
/usr/lib/mysql/plugin/auth_pam.so(auth_pam_talk_perform+0xe9)[0x7f44115f95a9]
/usr/lib/mysql/plugin/auth_pam.so(+0x17f9)[0x7f44115f87f9]
/lib/x86_64-linux-gnu/security/pam_krb5.so(+0x6c6c)[0x7f42c80bdc6c]
/usr/lib/x86_64-linux-gnu/libkrb5.so.3(krb5_get_init_creds_password+0x574)[0x7f42c7e2d744]
/lib/x86_64-linux-gnu/security/pam_krb5.so(+0x4467)[0x7f42c80bb467]
/lib/x86_64-linux-gnu/security/pam_krb5.so(+0x493b)[0x7f42c80bb93b]
/lib/x86_64-linux-gnu/security/pam_krb5.so(pam_sm_authenticate+0x27)[0x7f42c80bdeb7]
/lib/x86_64-linux-gnu/libpam.so.0(+0x2fcf)[0x7f44113e9fcf]
/lib/x86_64-linux-gnu/libpam.so.0(pam_authenticate+0x2d)[0x7f44113e985d]
/usr/lib/mysql/plugin/auth_pam.so(authenticate_user_with_pam_server+0xcd)[0x7f44115f898d]
/usr/sbin/mysqld[0x7a1026]
/usr/sbin/mysqld(_Z16acl_authenticateP3THD19enum_server_commandb+0xb5d)[0x7a4bbd]
/usr/sbin/mysqld[0xc254c4]
/usr/sbin/mysqld(_Z22thd_prepare_connectionP3THDb+0x5a)[0xc26e9a]
/usr/sbin/mysqld(handle_connection+0x281)[0xd2f891]
/usr/sbin/mysqld(pfs_spawn_thread+0x1b4)[0xeaa254]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7f7920515064]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f791e55562d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): Connection ID (thread ID): 3874004
Status: NOT_KILLED

[Shahriyar Rzayev (rzayev-sehriyar)]

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3757