This web mail archive is frozen.
This page is part of a frozen web archive of this mailing list.
You can still navigate around this archive, but know that no new mails
have been added to it since July of 2016.
Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.
On Aug 4, 2009, at 5:15 PM, Jean-Christophe Ducom wrote:
> When I try
> dqcneh001$ mpirun -np 1 -H dqcneh002 -mca plm_rsh_agent
> "/usr/kerberos/bin/rsh -F" klist
> klist: No credentials cache found (ticket cache FILE:/tmp/
> Kerberos 4 ticket cache: /tmp/tkt82784
> klist: You have no tickets cached
> The Kerberos ticket is not forwarded.
Strange. I'm afraid I don't use a kerberos-based rsh, so I don't know
what it's looking for that it's not finding. What happens under the
covers in OMPI is that we use "rsh -F" to launch the "orted" process
on the remote node. After some network back-n-forth, the orted fork/
exec's your executable (klist, in this case). Nothing too special
Do you know what klist is doing to determine that it doesn't have any
credentials? E.g., does that file /tmp/krb5cc_p3651 exist, or no? Is
there some environment variable that it passes that filename through
that we're somehow not passing down through the orted to the executable?