Sponsored Content
Operating Systems Linux Red Hat Server health Checks pre & post Rebooting Post 302924689 by MadeInGermany on Tuesday 11th of November 2014 04:03:05 PM
Old 11-11-2014
Go for a monitoring system!
Like the free Xymon or Nagios.
In the monitoring system, you watch your critical processes, disks, DB-specific tests, ...
It will inform you if anything important is missing or wrong - always, not only after a system reboot.
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Server rebooting frequently

O/P of the uname -a Server Server 4.0 3.0 3516 Pentium IV(TM)-ISA/PCI Server is getting rebooted frequetly... I don't know what is the problem in server ... Any help why the server is getting rebooted frequetly. Can i check what is the problem like in log files (5 Replies)
Discussion started by: srikanthus2002
5 Replies

2. UNIX for Dummies Questions & Answers

health checks

Hello Anyone please help me with a health check script on HP-UX. (1 Reply)
Discussion started by: mahlathini
1 Replies

3. Infrastructure Monitoring

visual representation of server health

HI all, I want to make a webpage showing the status of services running on a server. for example email, http , etc. That way users can see that server status for themselfs. Maybe even show the status of each virtual domain running on the server. Any way to do this without buying some product? ... (4 Replies)
Discussion started by: mcraul
4 Replies

4. UNIX for Dummies Questions & Answers

Backup Tapes Health checks

Hi all gurus Is there any command to perform the tapes health checks? thanks in adv jiajin (1 Reply)
Discussion started by: lijiajin
1 Replies

5. Solaris

sun server health check

do anybody has a procedure for daily weekley monthly health check for SUN server with solaris OS?? (5 Replies)
Discussion started by: mm00123
5 Replies

6. AIX

Pre-checks

AIX Guys!!! What pre-checks would you do on a 5.3 server before TL/SP/APAR installation? Bala (2 Replies)
Discussion started by: balaji_prk
2 Replies

7. Solaris

Monitor server's health

Dear all, There wasn't any monitoring on our server except on the filesystem. Therefore, I was wondering anything i should do on a daily basis to check on the server's status, health, hardware, or any other thing as a disaster prevention? Also, what command i should use to do that? ... (2 Replies)
Discussion started by: beginningDBA
2 Replies

8. Red Hat

Server rebooting unexpectedly

hi, I have been working on Solaris am very new to linux. My concern is as it goes....our server is getting rebooted automatically and I am not able to understand anything from the var log messages. Could anybody help me out in troubleshooting the issue. 2.6.18-128.el5 #1 x86_64 GNU/Linux is... (1 Reply)
Discussion started by: EmbedUX
1 Replies

9. Shell Programming and Scripting

Network connectivity Pre checks

Hello All, We are running multiple codes in prod all having different sources of databases in other servers. Many times due to network issue connectivity and DB issue the jobs got failed and to recover them become very brainstorming . I planning to create one script that can pre check if all the... (0 Replies)
Discussion started by: looney
0 Replies
SA-CHECK_SPAMD.RAW(1)					User Contributed Perl Documentation				     SA-CHECK_SPAMD.RAW(1)

NAME
sa-check_spamd - spamd monitoring script for use with Nagios, etc. SYNOPSIS
sa-check_spamd [options] Options: -c secs, --critical=secs Critical ping response threshold -h, -?, --help Print usage message -H hostname, --hostname=hostname Hostname of spamd service to ping -p port, --port=port Port of spamd service to ping --socketpath=path Connect to given UNIX domain socket -t secs, --timeout=secs Max time to wait for a ping response -v, --verbose Verbose debug output -V, --version Output version info -w secs, --warning=secs Warning ping response threshold DESCRIPTION
The purpose of this program is to provide a tool to monitor the status of "spamd" server processes. spamd is the daemonized version of the spamassassin executable, both provided in the SpamAssassin distribution. This program is designed for use, as a plugin, with the Nagios service monitoring software available from http://nagios.org. It might be compatible with other service monitoring packages. It is also useful as a command line utility or as a component of a custom shell script. OPTIONS
Options of the long form can be shortened as long as the remain unambiguous (i.e. --host can be used instead of --hostname). -c secs, --critical=secs Critical ping response threshold in seconds. If a spamd ping response takes longer than the value specified (in seconds) the program will exit with a value of 2 to indicate the critical status. This value must be at least as long as the value specified for warning and less than the value specified for timeout. -h, -?, --help Prints this usage message and exits. -H hostname, --hostname=hostname The hostname, or IP address, of the spamd service to ping. By default the hostname localhost is used. If --socketpath is set this value will be ignored. -p port, --port=port The port of the spamd service to ping. By default port 783 (the spamd default port number) is used. If --socketpath is set this value will be ignored. --socketpath=path Connect to given UNIX domain socket. Use instead of a hostname and TCP port. When set, any hostname and TCP port specified will be ignored. -t secs, --timeout=secs The maximum time to wait for a ping response. Once exceeded the program will exit with a value of 2 to indicate the critical status. The default timeout value is 45 seconds. The timeout must be no less than 1 second. This value must be greater than the values specified for both the critical and warning values. -v, --verbose Display verbose debug output on STDOUT. -V, --version Display version info on STDOUT. -w secs, --warning=secs Warning ping response threshold in seconds. If a spamd ping response takes longer than the value specified (in seconds), and does not exceed the critical threshold value, the program will exit with a value of 1 to indicate the warning staus. This value must be no longer than the value specified for critical and less than the value specified for timeout. EXIT CODES
The program will indicate the status of the spamd process being monitored by exiting with one of these values: 0 OK: A spamd ping response was received within all threshold times. 1 WARNING: A spamd ping response exceeded the warning threshold but not the critical threshold. 2 CRITICAL: A spamd ping response exceeded either the critical threshold or the timeout value. 3 UNKNOWN: An error, probably caused by a missing dependency or an invalid configuration parameter being supplied, occurred in the sa-check_spamd program. SEE ALSO
spamc(1) spamd(1) spamassassin(1) PREREQUISITES
"Mail::SpamAssassin" version 3.1.1 or higher (3.1.6 or higher recommended) AUTHOR
Daryl C. W. O'Shea, DOS Technologies <spamassassin@dostech.ca> LICENSE
sa-check_spamd is distributed under the Apache License, Version 2.0, as described in the file "LICENSE" included with the Apache SpamAssassin distribution and available at http://www.apache.org/licenses/LICENSE-2.0 perl v5.14.2 2014-02-14 SA-CHECK_SPAMD.RAW(1)
All times are GMT -4. The time now is 12:15 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy