On Friday 09 November 2007 06:23:44 you wrote:
> yes, I've seen this before.  It's not an MPIg issue, it's a
> Globus installation/configuration issue.
>
> Propagating env vars to the running job that are explicitly specified
> in RSL or XML Globus job description files or "permanent" env vars
> found in .* files (e.g., .soft, .cshrc) has always been a sticky
> wicket because they often (always?) require modifying the Globus
> Job Manager scripts to pass env vars/vals to the running app.
>
> My best advice to move forward in troubleshooting is to take MPIg
> out of the picture for now and run Globus jobs only with a small
> "/bin/env" program, both WS and pre-WS, specifying env vars in
> the RSL/XML and check stdout.
>

Your well-informed and quite thorough advice is much appreciated. I had seen 
vague references to environment variable troubles in various mailing list 
archives but thank you for spelling it out so explicitly and providing the 
test cases.  

However, it looks like the problem was caused by an outdated build of MPIg as 
the delegation of the credentials began working after it was upgraded to the 
latest version (although one of the 1000 tweaks I made while troubleshooting 
the problem might have made a difference). I'm still waiting on final 
confirmation that everything is working correctly but, given that these 
systems will be used for a demo at SC07 and the close proximity of that 
event, I'm pretty sure I would have heard some screaming if it wasn't fully 
functional.

Thanks again,

Michael Lambert
System Administrator
Louisiana Optical Network Initiative /
High Performance Computing @ LSU
http://www.loni.org/
http://www.hpc.lsu.edu/

Reply via email to