Sponsored Content
Full Discussion: Autosys Email Alarms
Top Forums UNIX for Dummies Questions & Answers Autosys Email Alarms Post 302107410 by BOFH on Friday 16th of February 2007 01:12:18 PM
Old 02-16-2007
You could scan the logs periodically and when a failure is generated (assuming it's logged of course), you can shoot off an e-mail then. What system is the app running on?

Carl
 

10 More Discussions You Might Find Interesting

1. Solaris

Alarms/Alerts

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

alarms

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

Documentation and books on Autosys Job Control Tool from Autosys

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

Sun Solaris 9 Traps Contain Multiple Alarms

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

lp serverlist alarms in messages

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

Autosys: How to change a machine name in Autosys JIL.

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

Hardware Alarms on HP-ux Solarisx86

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

Strange power supply units alarms!!!

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

Ftpd alarms

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

Sudden Service Busy Alarms

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
syslog.conf(4)							   File Formats 						    syslog.conf(4)

NAME
syslog.conf - configuration file for syslogd system log daemon SYNOPSIS
/etc/syslog.conf DESCRIPTION
The file /etc/syslog.conf contains information used by the system log daemon, syslogd(1M), to forward a system message to appropriate log files and/or users. syslogd preprocesses this file through m4(1) to obtain the correct information for certain log files, defining LOGHOST if the address of "loghost" is the same as one of the addresses of the host that is running syslogd. A configuration entry is composed of two TAB-separated fields: selector action The selector field contains a semicolon-separated list of priority specifications of the form: facility.level [ ; facility.level ] where facility is a system facility, or comma-separated list of facilities, and level is an indication of the severity of the condition being logged. Recognized values for facility include: user Messages generated by user processes. This is the default priority for messages from programs or facilities not listed in this file. kern Messages generated by the kernel. mail The mail system. daemon System daemons, such as in.ftpd(1M) auth The authorization system: login(1), su(1M), getty(1M), among others. lpr The line printer spooling system: lpr(1B), lpc(1B), among others. news Designated for the USENET network news system. uucp Designated for the UUCP system; it does not currently use the syslog mechanism. cron Designated for cron/at messages generated by systems that do logging through syslog. The current version of the Solaris Operating Environment does not use this facility for logging. audit Designated for audit messages generated by systems that audit by means of syslog. local0-7 Designated for local use. mark For timestamp messages produced internally by syslogd. * An asterisk indicates all facilities except for the mark facility. Recognized values for level are (in descending order of severity): emerg For panic conditions that would normally be broadcast to all users. alert For conditions that should be corrected immediately, such as a corrupted system database. crit For warnings about critical conditions, such as hard device errors. err For other errors. warning For warning messages. notice For conditions that are not error conditions, but may require special handling. A configuration entry with a level value of notice must appear on a separate line. info Informational messages. debug For messages that are normally used only when debugging a program. none Do not send messages from the indicated facility to the selected file. For example, a selector of *.debug;mail.none sends all messages except mail messages to the selected file. For a given facility and level, syslogd matches all messages for that level and all higher levels. For example, an entry that specifies a level of crit also logs messages at the alert and emerg levels. The action field indicates where to forward the message. Values for this field can have one of four forms: o A filename, beginning with a leading slash, which indicates that messages specified by the selector are to be written to the specified file. The file is opened in append mode if it exists. If the file does not exist, logging silently fails for this action. o The name of a remote host, prefixed with an @, as with: @server, which indicates that messages specified by the selector are to be forwarded to the syslogd on the named host. The hostname "loghost" is treated, in the default syslog.conf, as the hostname given to the machine that logs syslogd messages. Every machine is "loghost" by default, per the hosts database. It is also possible to specify one machine on a network to be "loghost" by, literally, naming the machine "loghost". If the local machine is designated to be "loghost", then syslogd messages are written to the appropriate files. Otherwise, they are sent to the machine "loghost" on the net- work. o A comma-separated list of usernames, which indicates that messages specified by the selector are to be written to the named users if they are logged in. o An asterisk, which indicates that messages specified by the selector are to be written to all logged-in users. Blank lines are ignored. Lines for which the first nonwhite character is a '#' are treated as comments. EXAMPLES
Example 1: A Sample Configuration File With the following configuration file: *.notice /var/log/notice mail.info /var/log/notice *.crit /var/log/critical kern,mark.debug /dev/console kern.err @server *.emerg * *.alert root,operator *.alert;auth.warning /var/log/auth syslogd(1M) logs all mail system messages except debug messages and all notice (or higher) messages into a file named /var/log/notice. It logs all critical messages into /var/log/critical, and all kernel messages and 20-minute marks onto the system console. Kernel messages of err (error) severity or higher are forwarded to the machine named server. Emergency messages are forwarded to all users. The users root and operator are informed of any alert messages. All messages from the authorization system of warning level or higher are logged in the file /var/log/auth. FILES
/var/log/notice log of all mail system messages (except debug messages) and all messages of notice level or higher /var/log/critical log of all critical messages /var/log/auth log of all messages from the authorization system of warning level or higher ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Interface Stability |Stable | +-----------------------------+-----------------------------+ SEE ALSO
at(1), crontab(1), logger(1), login(1), lp(1), lpc(1B), lpr(1B), m4(1), cron(1M), getty(1M), in.ftpd(1M), su(1M), syslogd(1M), syslog(3C), hosts(4), attributes(5) SunOS 5.10 28 Jul 2004 syslog.conf(4)
All times are GMT -4. The time now is 03:14 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy