<div dir="ltr">Attached is a log for maxWalltime set to 7 minutes beyond which the job does not get submitted because of the 1 hour walltime limit of Cetus. --Ketan</div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Mar 3, 2015 at 10:15 PM, Ketan Maheshwari <span dir="ltr"><<a href="mailto:ketan@mcs.anl.gov" target="_blank">ketan@mcs.anl.gov</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">When I check queue with qstat, I see the job is submitted for 40 minutes. When I try to increase <span style="font-size:12.8000001907349px">maxWallTime the workflow does not get submitted because on Cetus maximum allowed walltime is 60 minutes. --Ketan</span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Mar 3, 2015 at 10:03 PM, Hategan-Marandiuc, Philip M. <span dir="ltr"><<a href="mailto:hategan@mcs.anl.gov" target="_blank">hategan@mcs.anl.gov</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
Looks like almost exactly 5 minutes to me:<br>
<br>
2015-03-04 01:45:43,943+0000 INFO Execute TASK_STATUS_CHANGE<br>
taskid=urn:R-3-0-2-1425432781969 status=2<br>
workerid=0304-3301040-000000:000000<br>
2015-03-04 01:50:44,676+0000 INFO Execute TASK_STATUS_CHANGE<br>
taskid=urn:R-3-0-2-1425432781969 status=5 Walltime exceeded<br>
<br>
Which is what the config file is asking for:<br>
<br>
app.bgsh {<br>
env.SUBBLOCK_SIZE: "16" # [R] line 27<br>
executable: "/home/ketan/SwiftApps/subjobs/bg.sh" # [R] line 25<br>
maxWallTime: "00:05:00" # [R] line 26<br>
}<br>
<br>
Again, the wrapper log shows the app as still running. Last line is:<br>
Progress 2015-03-04 01:45:43.971393118+0000 EXECUTE<br>
<br>
Please do me a favor and increase the walltime to one hour and let's see<br>
what happens then.<br>
<br>
If it still doesn't finish after one hour, we could try to strace it and<br>
see what is happening there.<br>
<br>
Mihael<br>
<span><br>
On Tue, 2015-03-03 at 19:53 -0600, Ketan Maheshwari wrote:<br>
> Please find the log attached. --Ketan<br>
><br>
> On Tue, Mar 3, 2015 at 7:03 PM, Hategan-Marandiuc, Philip M. <<br>
> <a href="mailto:hategan@mcs.anl.gov" target="_blank">hategan@mcs.anl.gov</a>> wrote:<br>
><br>
> > On Tue, 2015-03-03 at 15:42 -0600, Ketan Maheshwari wrote:<br>
> > > Slow network looks unlikely to be a cause:<br>
> ><br>
> > It's the only variable obvious, so I wouldn't say that.<br>
<br>
</span>I meant "only obvious variable" there.<br>
<br>
<br>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div>