Prentice,

>From what we have determined, this is a race condition.  We have experienced 
>the same problem for months.  Some of my users are currently working with 
>Mathworks to find a solution.

--murph

Siemens Energy, Inc
Orlando, FL

-----Original Message-----
From: [email protected] [mailto:[email protected]] On 
Behalf Of Prentice Bisbal
Sent: Wednesday, February 08, 2012 10:37 AM
To: [email protected] Users
Subject: [gridengine users] Another MATLAB + SGE Question

So I finally have MATLAB set up and working fine with SGE. I can submit
parallel and distributed jobs from MATLAB to SGE, and then SGE does its
thing.
I have one remaining problem, and I thought I'd ask here first before
talking to Mathworks, since I have more confidence in you guys. I'm
afraid this might be very MATLAB specific, though.

When I submit a parallel job, the job executes, and appears to complete
without any issues (MATLAB prints the results), but then the running job
goes from status 'r' to 'Eqw'. Using 'qstat -j <jobid> -E explain' shows
this error:

error reason    1:          02/08/2012 10:28:58 [103808:6171]: error:
can't open output file "/work/prentice/matlab/Job1/Job1.mp

My working directory is /work/prentice/matlab, and the Job1 directory is
temporary directory used my MATLAB when the job is running.

In my MATLAB submit script, it call destroy() to kill the job after it
gets the results, and this destroy function deletes the Job1 subdir
while SGE is still running leading to this result. If I don't call
destroy(), MATLAB leaves a bunch of files and dirs in my working
directory related to Job1, Job2, etc.

Has anyone else seen this with MATLAB+SGE? I suspect I might need to
modify the destroyJobFcn.m file to not kill the jobs while they're still
running.

-- 
Prentice 

_______________________________________________
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