I running below script from controlM and job is reporting as failure everyday so i tried to change the if exitstatus=1 (send only email) but not to end as a job is failed. can you let me know where i have to change this script to make the script not to fail but instead send email and complete successfully
====
Moderator's Comments:
Please use code tags when posting data and code samples!
Hi,
I am using gmake to compile a c program with a makefile. The make file runs ld. I get the following error
jsh1035c:/users/egate453/admegate/kapil/samples $ gmake -e -f GNUmakefile queue_c
gmake -f ./GNUmakefile queue_c in_objdir=1 build_root=/users/egate453/admegate/kapil/samples... (2 Replies)
Forgive me, I do not know much about RAID so I'm going to be
as detailed as possible.
This morning, our server's alarm was going. I found that one
of our drives have failed. (we have 3)
It is an Adaptec ATA RAID 2400A controller
I'm purchasing a new SCSI drive today. My questions:
... (2 Replies)
I'm trying to change the user Id that the script is running under. I tried the sudo comand but the job was submitted under ControlM and it seems that controlM is not allowing the user id to change. I have included the job output below. The sudo comand was suppose to set the user id to "DWSOLAP"... (3 Replies)
Usually when su rejects an attempt to switch user it responds with "Sorry" but with a certain username on some unix servers the response is "Killed". I'm guessing the su accepted the username/password but refused to spawn child shell with the specified username. What's causing this and what has to... (8 Replies)
Dear Members,
I have a file which contains ControlM characters in it.
I need a command by the means of which i should be able to identify if a file has controlM characters.
How can this be achieved.
Thanks
Sandeep (4 Replies)
Hello,
Sometimes when i execute my shell that makes sftp it gives me this error:
Couldn't close file: Failure.
What does it mean?, how can i make sure it will do ok?.
Bye (2 Replies)
I am configuring Samba on one of my vmware.when i put smbclient -L local its showing error message : NT_STATUS_LOGON failure.I found that when i remove "Encrypted password entry from smb.conf" it works.
pls help me
---------- Post updated at 08:39 PM ---------- Previous update was at 07:11 PM... (0 Replies)
Hello,
i have a system with 6 sata3 seagate st3000dm01 disks running on stable Debian with software raid mdadm. i have md0 for root and md1 for swap and md2 for the files. i now want to add one more disk = sdh4 for md2 but i got this errors:
The new disk is connected to an 4 port sata... (7 Replies)
Discussion started by: Sunghost
7 Replies
LEARN ABOUT DEBIAN
pegasus-exitcode
PEGASUS-EXITCODE(1)PEGASUS-EXITCODE(1)NAME
pegasus-exitcode - Checks the stdout/stderr files of a workflow job for any indication that an error occurred in the job. This script is
intended to be invoked automatically by DAGMan as the POST script of a job.
SYNOPSIS
pegasus-exitcode [-h][-t n][-r rv][-n] job.out
DESCRIPTION
pegasus-exitcode is a utility that examines the STDOUT of a job to determine if the job failed, and renames the STDOUT and STDERR files of
a job to preserve them in case the job is retried.
Pegasus uses pegasus-exitcode as the DAGMan postscript for all jobs submitted via Globus GRAM. This tool exists as a workaround to a known
problem with Globus where the exitcodes of GRAM jobs are not returned. This is a problem because Pegasus uses the exitcode of a job to
determine if the job failed or not.
In order to get around the exitcode problem, Pegasus wraps all GRAM jobs with Kickstart, which records the exitcode of the job in an XML
invocation record, which it writes to the job's STDOUT. The STDOUT is transferred from the execution host back to the submit host when the
job terminates. After the job terminates, DAGMan runs the job's postscript, which Pegasus sets to be pegasus-exitcode. pegasus-exitcode
looks at the invocation record generated by kickstart to see if the job succeeded or failed. If the invocation record indicates a failure,
then pegasus-exitcode returns a non-zero result, which indicates to DAGMan that the job has failed. If the invocation record indicates that
the job succeeded, then pegasus-exitcode returns 0, which tells DAGMan that the job succeeded.
pegasus-exitcode performs several checks to determine whether a job failed or not. These checks include:
1. Is STDOUT empty? If it is empty, then the job failed.
2. Are there any <status> tags with a non-zero value? If there are, then the job failed. Note that, if this is a clustered job, there
could be multiple <status> tags, one for each task. If any of them are non-zero, then the job failed.
3. Is there at least one <status> tag with a zero value? There must be at least one successful invocation or the job has failed.
In addition, pegasus-exitcode allows the caller to specify the exitcode returned by Condor using the --return argument. This can be passed
to pegasus-exitcode in a DAGMan post script by using the $RETURN variable. If this value is non-zero, then pegasus-exitcode returns a
non-zero result before performing any other checks. For GRAM jobs, the value of $RETURN will always be 0 regardless of whether the job
failed or not.
Also, pegasus-exitcode allows the caller to specify the number of successful tasks it should see using the --tasks argument. If
pegasus-exitcode does not see N successful tasks, where N is set by --tasks, then it will return a non-zero result. The default value is 1.
This can be used to detect failures in clustered jobs where, for any number of reasons, invocation records do not get generated for all the
tasks in the clustered job.
In addition to checking the success/failure of a job, pegasus-exitcode also renames the STDOUT and STDERR files of the job so that if the
job is retried, the STDOUT and STDERR of the previous run are not lost. It does this by appending a sequence number to the end of the
files. For example, if the STDOUT file is called "job.out", then the first time the job is run pegasus-exitcode will rename the file
"job.out.000". If the job is run again, then pegasus-exitcode sees that "job.out.000" already exists and renames the file "job.out.001". It
will continue to rename the file by incrementing the sequence number every time the job is executed.
OPTIONS -h, --help
Prints a usage summary with all the available command-line options.
-t n, --tasks n
Number of tasks expected. If less than n tasks succeeded, then pegasus-exitcode will fail with a non-zero return value. This is used in
cases where we may not get a Kickstart invocation record for some tasks. Normally Seqexec will detect failed Kickstart invocations and
fail accordingly.
-r rv, --return rv
Return value reported by DAGMan. This can be specified in the DAG using the $RETURN variable. If this is non-zero, then
pegasus-exitcode immediately fails with a non-zero return value itself.
-n, --no-rename
Don't rename job.out and job.err to .out.XXX and .err.XXX. This option is used primarily for testing.
AUTHORS
Gideon Juve <juve@usc.edu>
Pegasus Team http://pegasus.isi.edu
05/24/2012 PEGASUS-EXITCODE(1)