[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] DAGman stopped working with 6.8.x
- Date: Wed, 17 Jan 2007 07:37:07 +0000
- From: Mark Calleja <M.Calleja@xxxxxxxxxxxxxxx>
- Subject: Re: [Condor-users] DAGman stopped working with 6.8.x
I would second that.
Stuart Anderson wrote:
Would it be sufficient, and is it backwards compatable, for you to
distribute a 6.8.4 pre-release for condor_submit_dag that we can use on
On Tue, Jan 16, 2007 at 11:34:34AM -0600, R. Kent Wenger wrote:
On Tue, 16 Jan 2007, Mark Calleja wrote:
I'm also now seeing the behavior reported at:
I'm getting this with 6.8.3 under linux (32 bit). Did anyone ever fathom
out what's going wrong?
Yes, we just recently figured this out. The problem is that the
OnExitRemove expression generated for DAGMan jobs got changed to something
more sophisticated, and on Windows, especially, it sometimes shows up as
The workaround is to run condor_submit_dag with the -no_submit flag, and
then edit the .condor.sub file to fix the OnExitRemove, and condor_submit
the .condor.sub file.
The OnExitRemove expression generated by condor_submit_dag is:
( ExitSignal == 11 || (ExitCode >=0 && ExitCode <= 2))
You should change this to:
( ExitSignal =?= 11 || (ExitCode =!= UNDEFINED && ExitCode >=0 &&
ExitCode <= 2))
This should be fixed in 6.8.4.
Condor-users mailing list
To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
You can also unsubscribe by visiting
The archives can be found at either