Greetings, all. Im running on the
latest files from CVS. Im trying to setup a test environment where
one server (named branch-1) will alert a master server (mainmonitor)
in the event of a problem. I can get the branch-1 server to recognize a
problem and send an alert to the master server,
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of David Nolan
Sent: Thursday, July 13, 2006 7:06 AM
To: mon@linux.kernel.org
Subject: Re: Problem getting traps to work correctly
--On Wednesday, July 12, 2006 16:30:08 -0500 Tim Carr
[EMAIL PROTECTED]
wrote
, it will only log this for that same event:
trapalert Store13-2 DRBD_Status 1152819578 /opt/mon/alert.d/mail.alert
([EMAIL PROTECTED]) DRBD_Not_Running
Thanks,
Tim
-Original Message-
From: David Nolan [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 13, 2006 2:32 PM
To: Tim Carr; mon
That did the trick. Thanks for your help.
Thanks,
Tim
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David
Nolan
Sent: Thursday, July 13, 2006 5:03 PM
To: Tim Carr
Cc: mon@linux.kernel.org
Subject: Re: Problem getting traps to work correctly
On 7/13
Has anyone got something like this going...
-
Were going to have an
environment where weve got lots of servers out in the field (i.e., at over
a thousand locations, two servers per locations) that are running mon to watch
both themselves and their local standby server. If something
Has anyone run into a problem where mon, in all its outputs
(monshow, monfailures, mon.cgi) is returning anything generated by a config
file (i.e., the description) or a monitoring output (i.e., tcp.monitor), with a
20 instead of a space?
For example, if my config file has a description
Thanks, folks - that cleared up the problem.
Tim
-Original Message-
From: Jim Trocki [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 27, 2006 8:05 AM
To: Tim Carr
Cc: Ed Ravin; mon@linux.kernel.org
Subject: RE: Getting 20 instead of spaces
On Wed, 26 Jul 2006, Tim Carr wrote
Hi, folks.
Were going to be running mon on over 1,000 servers (each
one is monitoring things at a remote site). Each of these servers/sites
are reporting in (via the redistribute command) to a
Corporate/main monitoring server so we can be aware of a failure out in the
remote site. This
: Thursday, August 24, 2006 9:15 AM
To: David Nolan
Cc: mon@linux.kernel.org
Subject: Re: Question on Redistribute
On Thu, 24 Aug 2006, David Nolan wrote:
--On Thursday, August 24, 2006 08:21:16 -0500 Tim Carr
[EMAIL PROTECTED]
The problem is that we're going to need to turn the monitoring
to catch
any of the specific service outage traps that would be received.
That would drop us down to 2400 traps/minute (64kb / sec) + any outages
traps.
Make sense?
Thanks,
Tim
-Original Message-
From: David Nolan [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 24, 2006 2:40 PM
To: Tim Carr
Heres more information on the
problem. We can tell that mon is automatically passing its standard option
to the alert as a getopts call within the alert that looks for -s
and a data field returns what the service name is that failed. So in the
example below, the alert, instead of taking -s
Any good reference on the web interface? (the
one from the site, mon.lycos.com is dead).
I believe the most commonly used interface is mon.cgi, maintained by
Ryan Clark, available at http://moncgi.sourceforge.net/
Ryan also has a website at http://www.ryanclark.org. He started working
on a
12 matches
Mail list logo
