11-19-2010
Not an Ad
Sorry guys, but I'm not posting an advertisement. Mikeo probably was and I don't know anyone here yet. I'm a UNIX/Linux admin and I've been really busy since my last post. And, I'm on vacation for 10 days starting Monday, so I may not reply for awhile after today. But, I'm real. I'll send a copy of my photo ID. You can call me or my boss. I work at Johns Manville in the world headquarters in Denver, CO.
I've never had any experience with Nagios until about a month ago. My boss asked me to set it up and I have done so, except for some issues for which I just can't find any answers. I signed up here because I was looking for Nagios support and hoped there would be some here, and this looked like a good, busy forum site for UNIX/Linux. I haven't posted on anything else yet, because I'm pulling my hair out over a couple of Nagios issues. However, I'm sure I might be able to lend some expertise to some of your other forums as time allows.
I like Pludi's idea of combining all types of monitoring software if there isn't a large enough crowd for Nagios.
So, it looks like you have quite a few knowledgeable people on here and I would like to find the ones who know Nagios. Since Nagios is very popular, I thought it might be nice to add a spot for Nagios.
Thanks,
Docster
6 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi all
I'm trying to get nagios up and running on FreeBSD 4.10
I installed the ports and just have to configure it
documentation supplied by nagios on how to configure the net-mgmt is not working for me. I tried everything possible but just can't seem to configure it.
Anybody have an... (1 Reply)
Discussion started by: stunner
1 Replies
2. 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
3. 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
4. What is on Your Mind?
Just a quick update; to speed up the forums, I have disabled the forum statistics on the home page for non registered users.
No changes for registered users. (0 Replies)
Discussion started by: Neo
0 Replies
5. AIX
Hello All,
I am new to Nagios. I have a requirement to monitor AIX 7.1 using Nagios xi, could any one guide me steps to go in right direction.
I know Nagios doesn't have precompiled agent and plugin for aix 7.1.
Appreciate your help (2 Replies)
Discussion started by: bsivavani
2 Replies
6. What is on Your Mind?
For mobile users, I have just added a "first beta" Advanced Forum Statistics to the home page on mobile using CSS overflow:auto; so you can swipe if you need to see more. Google Search Console mobile usability says this page is "mobile friendly" so perhaps this will be useful for some of our... (12 Replies)
Discussion started by: Neo
12 Replies
LEARN ABOUT DEBIAN
mailping-success
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)