9 More Discussions You Might Find Interesting
1. Infrastructure Monitoring
We have a dual Nagios server setup. One is setup for internal server monitoring on our LAN, while the second Nagios server is hosted externally and is used for external checks only such as URL and ping checks form the WAN side.
I was wondering if there is any way to setup cross dependencies... (1 Reply)
Discussion started by: eugenes18t
1 Replies
2. Infrastructure Monitoring
Hi Folks,
I have Nagios 3.0.6 which is monitoring 400+ servers in my environment and is administered by multiple administrators. I want to get notified if somebody enable or disable any notification of any of the hosts/services from GUI. Is it possible to configure?
If so, how? (0 Replies)
Discussion started by: SiddhV
0 Replies
3. Shell Programming and Scripting
I have an Ubuntu machine that I'd like to update automatically. I've written an expect script to run the aptitude package manager and update my packages. Essentially it does:
aptitude update && aptitude upgrade while answering "yes" at the appropriate time.
It works quite nicely when run... (4 Replies)
Discussion started by: CluelessPerson
4 Replies
4. Infrastructure Monitoring
What are the chances of getting a Nagios forum? The community is really lacking for a good place to work issues in Nagios. There just aren't any good places to go that I've found.
Thanks,
Docster (27 Replies)
Discussion started by: Docster
27 Replies
5. Infrastructure Monitoring
Hi,
Installed it and all seems okay except when I try to actually use it. :-(
Visiting my nagios url, it says
Logs and conf's follow:
nagios.log is:
# cat /usr/local/nagios/var/nagios.log | tail -5
Successfully shutdown... (PID=3613)
Nagios 3.2.2 starting... (PID=4645)... (7 Replies)
Discussion started by: smcracraft
7 Replies
6. Shell Programming and Scripting
Hello! I am currently attempting to build a very, very, basic program that attempts to act like a calendar for a "server." Using this program I need to have the client program connect to the server program, have the client wait for the server to respond through a socket, then exit and the server... (2 Replies)
Discussion started by: Entelexia
2 Replies
7. UNIX for Advanced & Expert Users
Hi,
I have over 5 gb of data in a files structure in which month folders are in year folders, day folders are in month folders, and individual climate stations are in each day. I am trying to extract precipitation measured at 5 minute intervals for a duration of 15 years, but the script never... (2 Replies)
Discussion started by: mlw63@me.com
2 Replies
8. Programming
Hi,
I have encountered the following problem on Solaris 10:
I have a thread that is asleep on nanosleep (set to 24 hours).
Something that happens on another thread, causes the nanosleep to exit, even though the time has not elapsed.
The returned value is 0 (so it doesn't look like it... (1 Reply)
Discussion started by: MeMyself
1 Replies
9. Shell Programming and Scripting
I have the following korn shell script which reads the contents of an ascii file and performs an rexec command based on the line that was just read from the ascii file. The ascii file contains 6 lines, thus, the while loop should execute 6 times. The problem is that the rexec command within the... (2 Replies)
Discussion started by: sadove
2 Replies
2004-04-16
mailping
0.0.4
MAILPING-SUCCESS(1) Mailping MAILPING-SUCCESS(1)
NAME
mailping-success - Munin plugin to graph time since last mail delivery
SYNOPSIS
/usr/share/mailping/munin-plugins/mailping-success {[config] | ['']}
DESCRIPTION
mailping-success is a Munin plugin that monitors time passed since last successful email probe.
Configuration output
When passed config, it outputs Munin configuration information. If there are no circuits defined (no subdirectories in /etc/mailping), it
specifies that Munin should draw no graph either.
If configuration files /etc/mailping/circuit/warntime and /etc/mailping/circuit/failtime exist, the values in them are passed on to Munin,
for use in Nagios alert integration.
Value output
When passed an empty string '', mailping-success outputs the difference between current time and last successful probe, for each configured
circuit.
FILES
/etc/mailping/
List of circuits that exist; each subdirectory is a circuit.
/etc/mailping/circuit/warntime
If more than this many seconds have passed since last successful probe, a Nagios warning is triggered by Munin (assuming it has been
configured to do that). Default: no warnings.
/etc/mailping/circuit/failtime
If more than this many seconds have passed since last successful probe, a Nagios alert is triggered by Munin (assuming it has been
configured to do that). Default: no alerts.
/var/lib/mailping/state/circuit/success
Timestamp in seconds of the last successful probe for circuit.
ENVIRONMENT
MAILPING_CONFIGDIR
Override the location of the configuration directory. Default: /etc/mailping
MAILPING_STATEDIR
Override the location of the state directory. Circuit states are stored in the state subdirectory of this directory, in subdirectories
named after the circuit name. Default: /var/lib/mailping
SEE ALSO
mailping-latency(1), mailping-cron(1), mailping-store(1), munin-run(8), munin-node(8)
AUTHOR
Tommi Virtanen <tv@havoc.fi>
Havoc Consulting
Author.
COPYRIGHT
Copyright (C) 2004 Havoc Consulting
mailping 0. 2004-04-16 MAILPING-SUCCESS(1)
