maria-discuss team mailing list archive
Mailing list archive
Re: MariaDB unable to read the /etc/krb5.keytab
I enabled the TRACE log. But that doesn't produce any logs for this issue.
Any other ideas?
On Fri, Jul 21, 2017 at 4:17 PM, Vladislav Vaintroub <vvaintroub@xxxxxxxxx>
> Those errors come from GSSAPI/Kerberos APIs, they are not originated
> directly by the server.
> You can use environment variable KRB5_TRACE as described in
> https://web.mit.edu/kerberos/krb5-latest/doc/admin/troubleshoot.html to
> see more output. Set it before you start up the server.
> You can also use strace maybe, or a look for usual suspects (does mysql
> user have read access to keytab, does the keytab exist). You can also use
> private keytab if this is more convenient for you.
> On Sat, Jul 22, 2017 at 1:05 AM, Ali, Saqib <docbook.xml@xxxxxxxxx> wrote:
>> I am trying to setup MariaDB 10 with GSSAPI support.
>> I following the instructions here: https://mariadb.com/kb/en/mari
>> However, whenever I try to start Maria DB I get the following
>> [Warning] mysqld: GSSAPI plugin : default principal
>> 'mariadb/hostname.tld@REALM' not found in keytab
>> [ERROR] mysqld: Server GSSAPI error (major 851968, minor 2529639093
>> <(252)%20963-9093>) : gss_acquire_cred failed -Unspecified GSS failure.
>> Minor code may provide more information. Keytab FILE:/etc/krb5.keytab is
>> nonexistent or empty.
>> [ERROR] Plugin 'gssapi' init function returned error.
>> Mailing list: https://launchpad.net/~maria-discuss
>> Post to : maria-discuss@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~maria-discuss
>> More help : https://help.launchpad.net/ListHelp