10 More Discussions You Might Find Interesting
1. Red Hat
on the HP box , when we try to kickstart , the Linux gets installed on external LUN (Storage) .. so we end up unmapping the LUN and rekick , is there a way to disable the kickstart to ignore the external LUN incase we net boot it again (1 Reply)
Discussion started by: skamal4u
1 Replies
2. Red Hat
RHEL 5.4
I'm trying to use %include statements in my kickstarts, and am running into some problems.
In %pre, I can %include /mnt/source/isolinux/setup-questions and that works just fine. One of the things it does is echo out several variables to /tmp/vars In %post --nochroot, I copy... (2 Replies)
Discussion started by: jnojr
2 Replies
3. Red Hat
What are the packages that you need for a kickstart minimum install with a gui? I commented out the packages I don't think I need. Am I right?
%packages
@admin-tools
@base
@core
#@editors
#@fonts
@gnome-desktop
#@games
#@graphical-internet
#@graphics
@hardware-support
@input-methods... (0 Replies)
Discussion started by: cokedude
0 Replies
4. Red Hat
Hey all,
I'm not sure if this possible but I had tested it out manually during the installation (placed a sleep in the pre-installation) and it worked. I'm trying to have a pexpect script to log into the mysql and input a new row for the pre-installation, which will end up displaying on a web... (1 Reply)
Discussion started by: karljbaker
1 Replies
5. Linux
Hello everyone,
I have problem while configuring kickstart server .i have performed some steps but still i am unable to configure kickstart server on CentOS 5.4.
I have performed following steps:-
yum install system-config-kickstart
mkdir /kickstart
mount /dev/cdrom /media
cd /media... (2 Replies)
Discussion started by: karan chauhan
2 Replies
6. UNIX for Advanced & Expert Users
How do I configure kickstart server to install workstation using centos image and other workstation using redhat enterprise image.
I configured my kickstart server to auto install centos 5.3 and it working fine.
However I would like to configure kickstart server, so that workstation with... (1 Reply)
Discussion started by: hassan1
1 Replies
7. Red Hat
Hello,
I am pretty new to using Linux and learning as I go, my setup is extremly simple, I have 1 virtual machine running on my laptop running (ubuntu 10.04), I've created a kickstart (Red Hat) file with the ksconfig.
So I know have a config file for my Redhat.iso and my VM machine.
What's... (1 Reply)
Discussion started by: NelsonC
1 Replies
8. Red Hat
Hi,
I am trying to install RHEL5.3 using kickstart method. Copied the rhel.iso file from DVD to http location. ks.cfg and rhel.iso files are available on a WINDOWS2008 Server (via HTTP). In ks.cfg file, provided the media path as url --url=http://xx.xx.xx.xx/RHEL53. System understanding the... (3 Replies)
Discussion started by: uday123
3 Replies
9. UNIX for Advanced & Expert Users
Hi,
I was able to set up a kickstart to install Red Hat Enterprise thought a network.
I'm trying to enable a NTP time server in the post section of the kickstart file and also enable/disable a few services using chkconfig.
I can't seam to get it to work, can anyone help ? I don't beleive i... (2 Replies)
Discussion started by: Georgesaa
2 Replies
10. Linux
Would anyone know how to set a NIC to 100 Full Duplex from within a kickstart bootdisk? I just added the Tigon3 module to the bootnet.img - it loads fine but auto-negotiates to 100 Half Duplex for some reason - are there any parameters I can pass on the boot disk to force it 100 Full
appreciate... (2 Replies)
Discussion started by: silvaman
2 Replies
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)