[torqueusers] GSSAPI branch qstat behavior

Adam Steenwyk ajamess at umich.edu
Fri Jul 20 12:47:10 MDT 2007


Hello,

In testing the GSSAPI branch (1473) on a single head node, single client,
system I have noticed what I consider strange behavior.  What happens is as
follows:

I submit a long job to the queue (100 hours) after having gotten forwardable
and renewable tickets:

[14:39:39 ajamess at ragnar ajamess]$ kinit -f -r 14d ajamess at UMICH.EDU
Password for ajamess at UMICH.EDU:
[14:39:50 ajamess at ragnar ajamess]$ aklog
[14:39:56 ajamess at ragnar ajamess]$ klist -f
Ticket cache: FILE:/tmp/krb5cc_183752_SE33Tu
Default principal: ajamess at UMICH.EDU

Valid starting     Expires            Service principal
07/20/07 14:39:50  07/21/07 14:39:48  krbtgt/UMICH.EDU at UMICH.EDU
        renew until 07/27/07 14:39:50, Flags: FRIA
07/20/07 14:39:53  07/21/07 14:39:48  afs at UMICH.EDU
        renew until 07/27/07 14:39:50, Flags: FRAT

Kerberos 4 ticket cache: /tmp/tkt183752
klist: You have no tickets cached

[14:41:01 ajamess at ragnar ajamess]$ qsub torque-afs-test-weekend.sh
313.ragnar.engin.umich.edu

This is all fine and good.  The ticket gets passed in with my job and can be
renewed correctly throughout the job's lifetime; however, if I stay logged
in without renewing for longer than the non renewable lifetime of the
ticket, qstat fails to work.

[09:29:49 ajamess at ragnar ~]$ qstat -au ajamess
pbsgss_client_establish_context.gss_init_set_context : Miscellaneous failure
pbsgss_client_establish_context.gss_init_set_context : Ticket expired
pbsgss_client_establish_context.gss_init_set_context : Miscellaneous failure
pbsgss_client_establish_context.gss_init_set_context : Ticket expired
pbsgss_client_establish_context.gss_init_set_context : Miscellaneous failure
pbsgss_client_establish_context.gss_init_set_context : Ticket expired
pbsgss_client_establish_context.gss_init_set_context : Miscellaneous failure
pbsgss_client_establish_context.gss_init_set_context : Ticket expired

Now, if I destroy my tickets and do qstat again *without afs credentials*
there is no problem.  If I get *new* tickets, there is also not a problem
*until* the tickets expire, which is when I see this behavior.

My question is: is such behavior by qstat to be expected?  Am I missing
something?

Thank you!

Adam.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.supercluster.org/pipermail/torqueusers/attachments/20070720/a1c63475/attachment.html


More information about the torqueusers mailing list