03-14-2007
The simplest solution is to create another job that depends on the failure of the parent job. For example:
JobA - The current job you currently want to monitor
JobB - A job that is merely a shell script that emails you if JobA fails. This job depends on the failure of JobA.
10 More Discussions You Might Find Interesting
1. Solaris
Is there a imbedded command (Solaris v8 ksh) that will send an administrative alert/alarm. Or is it just triggering a mail message via shell script? If no, is there a good open-source code someone knows about?
Thanks so much in advance for any replies.
...Gozer13 (3 Replies)
Discussion started by: gozer13
3 Replies
2. Shell Programming and Scripting
Hi
I have been trying to set up alarms on my Solaris box (Sun OS 5.8)
The objective is to present the user an audible alarm every hour or so.
I have so far done this:
#!/bin/sh
val=1
while
do
printf "\a"
val=`expr $val + 1`
done
I have put this in my crontab to run hourly.... (2 Replies)
Discussion started by: run_time_error
2 Replies
3. UNIX for Advanced & Expert Users
My project uses Autosys.
I am new to this product and I don't know where to start from.
Q1. Please provide me the link where I can get Autosys documentation
Q2. Please refer a good book on Autosys. (Beginner/Intermediate Level) (0 Replies)
Discussion started by: gram77
0 Replies
4. Infrastructure Monitoring
Hi all,
I have a Sun Solaris 9 box which acts as a firewall. Sometimes if multiple actions which cause snmp traps occur very close together, a single snmp trap that is sent containing the text for multiple alarms. I would like to prevent that and have a trap sent for each action which would... (0 Replies)
Discussion started by: g0ld2k
0 Replies
5. Solaris
Hello,
I have been receiving following alarms in /var/adm/messages
dtcp: WARNING DB (db_tcp.c,363) db_alloc_connid: lp && lp->serverlist error for service 20
It seems like this message is related to LP print service. Since I am not using any print service, is there any way to switch it... (2 Replies)
Discussion started by: aalishan
2 Replies
6. UNIX for Dummies Questions & Answers
All the autosys jobs are on server-1 and server-1 has been crashed due to some reason, Now I have to run 5 autosys jobs on server-2 (failover server) which are on server 1.
How to do with Autosys command (which command needs to fired on JIL) (0 Replies)
Discussion started by: tp2115
0 Replies
7. Solaris
Hi I am trying to configure the Hardware alarms on HP server.
I have refer to "HP ProLiant Health Monitor User Guide" and installed
HPQacucli-3.5.0-solaris10-i386
HPQhealth-4.4.0-solaris10-i386
HPQhma-5.7.0-solaris10-i386
HPQilo-1.4.5-solaris10-i386
HPQsmh-5.5.0-solaris10-i386
... (2 Replies)
Discussion started by: anand87
2 Replies
8. Solaris
Hi folks,
I encountered this alarms on a solaris server:
04/21/12 23:17:55 MNP-PGW-A_bge3 mnp 231748 Power Supply Unit 0 is faulty
04/21/12 23:17:55 MNP-PGW-A_bge3 mnp 231748 Power Supply Unit 1 is faulty
04/21/12 23:18:26 MNP-PGW-A_bge3 mnp 231822 Power Supply Unit 0 is faulty:CLEAR... (0 Replies)
Discussion started by: kimurayuki
0 Replies
9. Solaris
Hi,
I am facing following alarms in var/adm/messages after an interval of 10 mins. I dont know what the impact is and how can i fix it. Can anyone help please?
Dec 4 07:50:03 hxcsvc-a01 ftpd: open_module: stat(/usr/lib/security/pam_unix_session.so.1) failed: No such file or directory
Dec ... (4 Replies)
Discussion started by: sni_engineer
4 Replies
10. Solaris
Hi,
I am getting service busy alarms on my machines which are using MongoDB every now and then. When the service busy alarm appears, I get the following errors on my mongo router logs.
Tue Apr 7 08:01:08.445 dbclient_rs nodes.ok = true hxcslc-b05:27014
Tue Apr 7 08:01:08.445 dbclient_rs... (0 Replies)
Discussion started by: sni_engineer
0 Replies
QSTAT(1) User Contributed Perl Documentation QSTAT(1)
NAME
qstat - display job/partition information in a familiar pbs format
SYNOPSIS
qstat [-f] [-a|-i|-r] [-n [-1]] [-G|-M] [-u user_list] [-? | --help] [--man] [job_id...]
qstat -Q [-f]
qstat -q
DESCRIPTION
The qstat command displays information about jobs.
OPTIONS
-a Displays all jobs in a single-line format. See the STANDARD OUTPUT section for format details.
-i Displays information about idle jobs. This includes jobs which are queued or held.
-f Displays the full information for each selected job in a multi-line format. See the STANDARD OUTPUT section for format details.
-G Display size information in gigabytes.
-M Show size information, disk or memory in mega-words. A word is considered to be 8 bytes.
-n Displays nodes allocated to a job in addition to the basic information.
-1 In combination with -n, the -1 option puts all of the nodes on the same line as the job id.
-r Displays information about running jobs. This includes jobs which are running or suspended.
-u user_list
Display job information for all jobs owned by the specified user(s). The format of user_list is: user_name[,user_name...].
-? | --help
brief help message
--man
full documentation
STANDARD OUTPUT
Displaying Job Status
If the -a, -i, -f, -r, -u, -n, -G, and -M options are not specified, the brief single-line display format is used. The following items are
displayed on a single line, in the specified order, separated by white space:
the job id
the job name
the job owner
the cpu time used
the job state
C - Job is completed after having run E - Job is exiting after having run. H - Job is held. Q - job is queued, eligible to run or
routed. R - job is running. T - job is being moved to new location. W - job is waiting for its execution time (-a option) to be
reached. S - job is suspended.
the queue that the job is in
If the -f option is specified, the multi-line display format is used. The output for each job consists of the header line: Job Id: job
identifier followed by one line per job attribute of the form: attribute_name = value
If any of the options -a, -i, -r, -u, -n, -G or -M are specified, the normal single-line display format is used. The following items are
displayed on a single line, in the specified order, separated by white space:
the job id
the job owner
the queue the job is in
the job name
the session id (if the job is running)
the number of nodes requested by the job
the number of cpus or tasks requested by the job
the amount of memory requested by the job
either the cpu time, if specified, or wall time requested by the job, (in hh:mm)
the job state
The amount of cpu time or wall time used by the job (in hh:mm)
EXIT STATUS
On success, qstat will exit with a value of zero. On failure, qstat will exit with a value greater than zero.
perl v5.14.2 2012-04-10 QSTAT(1)