On Tue, 16 Jan 2007, Mark Calleja wrote:
I'm also now seeing the behavior reported at:
https://lists.cs.wisc.edu/archive/condor-users/2006-November/
msg00026.shtml
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
UNDEFINED.
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.
Kent Wenger
Condor Team
_______________________________________________
Condor-users mailing list
To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx
with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/condor-users
The archives can be found at either
https://lists.cs.wisc.edu/archive/condor-users/
http://www.opencondor.org/spaces/viewmailarchive.action?key=CONDOR