 |
 |
Ah, so this is an operational thing.Yes, from what I understand, eos wants to do first try ath method a (I'm not sure what it is though) and if that fails, fallback to krb5. But if using an unconfigured krb5 causes a crash then there is little we can do except to properly allow usage. I suppose we can also configure eos to not fallback to krb5 for these machines. I'll punt this to Elvin and Andreas. Andy On Thu, 14 Jul 2016, Jan Iven wrote: > You should have powers to login (from within CERN). I have opened up the directory with corefile etc > /var/spool/abrt/ccpp-2016-03-09-17:29:32-921/ (this is a repeat crash, the backtrace of the most recent one corresponds still to the "old" corefile). I confirm that the 'xrootd' user should have no powers to use the machine keytab, nor would it have a Kerberos ticket cache. I suspect that Kerberos is invoked via some fallthrough authentication sequence, after something else (unix? the machine is whitelisted in EOS) failed. > > --- > You are receiving this because you commented. > Reply to this email directly or view it on GitHub: > https://github.com/xrootd/xrootd/issues/395#issuecomment-232616575 --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/issues/395#issuecomment-232624112 ######################################################################## Use REPLY-ALL to reply to list To unsubscribe from the XROOTD-DEV list, click the following link: https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1