kinit problem

[orris]

Anyone run into the error
kinit: Unable to make ‘Initial default ccache’ the new system default cache

And has anyone solved it?

After a few days/weeks of running flawlessly we run into this without fail….

Regards

[orris]

Sorry, out to lunch for the last several days…

Here’s more info

I’ve set up a cluster and want people to log into the head node and then spawn processes on the compute nodes as needed either through Xgrid or ssh or mpich2. I’d like to have the users kinit on there own machines and log into the head node with a forwardable ticket. The first time through the ticket is ok and the credential cache is set to something like API:krb5cc_ I haven’t a clue where this tmp file is located. Looked for it to no avail. But, when a user attempts to ssh into the compute nodes on the other side of the head node’s firewall they are asked for a password, instead of being properly authenticated. If at this point one goes back to the head node and asks to kinit the error

kinit: Unable to make ‘Initial default ccache’ the new system default cache

is returned and the previous forwardable tickets are destroyed. This seems to be a problem with the forwarding of tickets since a workaround I’ve found is to not ask for the initial ticket and to authenticate to the head node via ssh and not kerberos. After successfully logging into the head node one can then kinit and the initial default ccache works and is forwardable to the compute nodes.

It also works if you unsetenv KRB5CCNAME before kinit’ing on the head node! Indicating a problem with passing of the credential cache name.

Any clues?

Regards

[Author]

Posts