Hi,

> Am 19.05.2017 um 15:46 schrieb Mukesh Chawla <mukesh.mnni...@gmail.com>:
> 
> Hi,
> 
> Thanks a lot William and Reuti for the answers. Apparently I scheduled a
> .bat (windows bat file) job to check if it could run it and due to that the
> all.q got dropped for the queue list.
> 
> qstat -explain E gives the following output:
> 
>   - "queue all.q marked QERROR as result of job 2's failure at host
>   Mukesh-PC"

Then it's neccssary to reset the error flag:

$ qmod -cq all.q@Mukesh-PC


> Windows have provided a way to launch native windows programs using the WSL
> shell. How can I launch native windows applications using sgeexec?
> 
> My take on this is to append the windows exe path to the OGS environment
> PATH variable. I think that might fix it. It did fix it when I added the
> path to the job script and I could launch native windows through the grid
> engine exec host.
> 
> My use case is that I just want to run a windows exec host and thus I am
> trying to run it using WSL. I'll try to work my way through it. Can you
> suggest any other way that this could be done on windows. I have been
> running it on linux for a while and it works fine for all my nodes but now
> I have to add windows nodes to the cluster.

At first I would try to submit some jobs inside this ESL shell – maybe a simple 
shell script.

-- Reuti


> Best Regards,
> Mukesh
> 
> On Fri, May 19, 2017 at 6:01 PM, William Hay <w....@ucl.ac.uk> wrote:
> 
>> On Fri, May 19, 2017 at 03:34:32PM +0530, Mukesh Chawla wrote:
>>> Hi,
>>> 
>>> I am trying to run a windows exec host attached to a Unix based master
>>> using the new feature WSL(windows shell for linux)  introduced in windows
>>> 10. I have successfully set up the grid engine master and execution host
>> on
>>> it. But when I start submitting the jobs to the exec they just remain in
>>> queue.
>>> 
>>> 1. Can anybody let me know if its possible or if it has been done what
>>> could I be doing wrong?
>>> 
>>> 2. Also if WSL is not the correct way for windows then what else can I
>> use
>>> for this use case?
>>> 
>> WSL is fairly new so I doubt there is much experience running SoGE under
>> it.
>> 
>> In addition to the commands Reuti requested you run the output of the
>> following
>> cammands might be useful:
>> 
>> qstat -j <jobid>
>> qalter -w v <jobid>
>> and
>> qalter -w p <jobid>
>> 
>> against the jobid of a queued job would provide useful info.
>> 
>> William
>> 
> _______________________________________________
> SGE-discuss mailing list
> SGE-discuss@liv.ac.uk
> https://arc.liv.ac.uk/mailman/listinfo/sge-discuss
> 

_______________________________________________
SGE-discuss mailing list
SGE-discuss@liv.ac.uk
https://arc.liv.ac.uk/mailman/listinfo/sge-discuss

Reply via email to