account checks fail for ‘@’: user disallowed by .k5login file for ‘’
authentication fails for ‘’ (@): Permission denied (Success)
pam_krb5: pam_authenticate returning 6 (Permission denied)
innodb-write-io-threads = 64 (original value: unset)
innodb-read-io-threads = 64 (original value: unset)
innodb-use-native-aio = 0 (original value: unset)
innodb-buffer-pool-size = 250G (original value: 25G)
innodb-log-file-size = 5000M (original value: 32M)
After exhausting all options we finally just gave in a restarted this instance (not the entire server) and AD authentication was restored!
For about 15 hours.
The behavior is back and now I’m suspecting the log changes to be the culprit but can find not evidence of such a thing
Could there be a relation between innodb-buffer-pool-size or innodb-log-file-size and Percona’s auth_pam(_compat) plugin?