# auth\_pam\_compat delayed failure? **URL:** \ **Category:** Percona Server for MySQL 5.6\ **Created:** [September 16, 2016, 9:59am UTC](https://forums.percona.com/t/auth-pam-compat-delayed-failure/5090 "2016-09-16T09:59:41Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![chawley](https://avatars.discourse-cdn.com/v4/letter/c/9de053/32.png) [@chawley](https://forums.percona.com/u/chawley)\ **Post date:** [September 16, 2016, 9:59am UTC](https://forums.percona.com/t/auth-pam-compat-delayed-failure/5090/1 "2016-09-16T09:59:41Z")
account checks fail for ‘@’: user disallowed by .k5login file for ‘’ authentication fails for ‘’ (@): Permission denied (Success) pam\_krb5[8245]: pam\_authenticate returning 6 (Permission denied) # 2016-9-13 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? ---
**Author:** ![vadimtk](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/vadimtk/32/9528_2.png) [@vadimtk](https://forums.percona.com/u/vadimtk)\ **Post date:** [September 16, 2016, 2:04pm UTC](https://forums.percona.com/t/auth-pam-compat-delayed-failure/5090/2 "2016-09-16T14:04:19Z")
There is absolutely no relation between innodb-buffer-pool-size or innodb-log-file-size and Percona’s auth\_pam(\_compat) plugin. These are completely different subsystems.