On Tue, Jul 10, 2012 at 3:51 PM, Reuti <[email protected]> wrote: >> Failure was that user's .bashrc were not being read. In each user's >> account, I have it sourcing a system wide shell script which sets certain >> things up, like our module environment configuration and so nothing was >> being setup. > > Yep, this is normal for unix_nehavior as shell_start_mode not to source > anything.
Joseph, To debug the difference in behavior: 1) make sure that you can always reproduce the job failure. 2) then submit jobs to a node that fails the job & to a node that does not fail the job. 3) in the job script, add logic so that if things that you expect would work fail to work, then run sleep in a loop (infinite sleep). 4) then log into the node, and in the job's spool directory, you go to the "config" file and look for: shell_path, shell_start_mode, use_login_shell - compare the values of the 2 jobs and you should be able to tell what's going on... This way, you can tell what's going on, instead of just working around things! Rayson > > -- Reuti _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
