Hi,

> Am 05.01.2018 um 09:02 schrieb [email protected]:
> 
> Hi,
>  
> We have recently upgraded one submit host from RHEL6.7 to RHEL7.2.
> Most of our grid execution servers are RHEL6.7, with a few RHEL6.3 servers. 
> When we run any jobs by using ā€œ-Vā€ option to export environment variables, it 
> does not work and the job fails.

In case it's still relevant: can you put an:

echo $PATH

in the job script. Usually the coreutils applications's programs are at a 
default location and should be found. I wonder whether these location changed 
between different RHEL releases. Otherwise it could really happen that -V does 
work, but distribute wrong paths (similar to submitting to a Linux node from an 
AIX machine with a different directory layout). What is your setting of:

shell_start_mode

in the queue definition.

-- Reuti


>  As an example examine a simple job: 
>  
> <code>
> #!/bin/bash
>  
> date
> echo "Sleeping now"
> sleep $1
>  
> </code>
>  
> When we run this job without exporting environment variables, it works fine. 
> But exporting environment variables causes errors as shown below:
>  
> <BASE_PATH>/job_scripts/2666843: line 3: date: command not found
> <BASE_PATH>/job_scripts/2666843: line 5: sleep: command not found
>  
> Of course, this issue is persistent in interactive jobs also, which causes 
> applications not working properly.
>  
> Is there any way to circumvent this issue?
>  
> Thanks and regards,
> Srinivas.
> The information contained in this electronic message and any attachments to 
> this message are intended for the exclusive use of the addressee(s) and may 
> contain proprietary, confidential or privileged information. If you are not 
> the intended recipient, you should not disseminate, distribute or copy this 
> e-mail. Please notify the sender immediately and destroy all copies of this 
> message and any attachments. WARNING: Computer viruses can be transmitted via 
> email. The recipient should check this email and any attachments for the 
> presence of viruses. The company accepts no liability for any damage caused 
> by any virus transmitted by this email. www.wipro.com 
> ______________________________________________________________________
> This email has been scanned by the Symantec Email Security.cloud service.
> For more information please visit http://www.symanteccloud.com
> ______________________________________________________________________
> _______________________________________________
> users mailing list
> [email protected]
> https://gridengine.org/mailman/listinfo/users


_______________________________________________
users mailing list
[email protected]
https://gridengine.org/mailman/listinfo/users

Reply via email to