headers
Video Game Junkie | 20 Nov 2006 22:40
Picon

CVS 1-2-0 and syslog

I'm running a FC5 Linux box and was looking to give mon a try. I
checked out all the files and installed everything. I can start mon
fine and get failure notices, but I don't see anything getting logged.
I looked through the list archives and noticed that it should be
logging to syslog, but there are no entries there.

As a test, I have another FC5 box and installed the mon-0.99-2 rpm
from Dag. After installing all the needed perl modules via CPAN, I
started the monitor and it worked as expected. I saw all the syslog
entries. I then updated to the CVS 1-2-0 branch and started the
script. Again the monitor worked, but nothing was output into syslog.

Is this a bug or am I missing something?

Thanks
Jae
Permalink | Reply | 2 comments |
headers
Video Game Junkie | 21 Nov 2006 02:25
Picon

Re: CVS 1-2-0 and syslog

As an example. Running 0.99-2 gives me this in /var/log/messages:

Nov 20 16:29:33 SERVER mon[18164]: running as daemon
Nov 20 16:29:33 SERVER mon[18164]: mon server started
Nov 20 16:29:39 SERVER mon[18164]: failure for servers ping 1164058179
10.2.154.254
Nov 20 16:29:39 SERVER mon[18164]: calling alert mail.alert for
servers/ping (/usr/lib/mon/alert.d/mail.alert,root <at> localhost)
10.2.154.254

1.2 gives me nothing in /var/log/messages. No startup messages and
nothing to about the service failure and mail alert. Also when I first
started mon, I didn't have the ping.monitor in the mon.d directory,
the 1.2 verison did not log anything, but the 0.99 did:

Nov 20 15:58:28 SERVER mon[17674]: no monitor found while trying to
run [ping.monitor]

Thanks for your help on this, I'm new to using mon.

Jae

On 11/20/06, Chuck McIntyre wrote:
> Jae,
>
> According to the manpage, mon basically only uses syslog when there is
> an error (dependency expressions broken, something down outside of the
> alert date range, all hosts empty, etc). Unless I'm missing something
> here, I think that is all (besides traps).
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
David Nolan | 21 Nov 2006 18:27
Picon
Favicon

Re: CVS 1-2-0 and syslog


--On Monday, November 20, 2006 16:40:46 -0500 Video Game Junkie 
<vgjunkie <at> gmail.com> wrote:

> I'm running a FC5 Linux box and was looking to give mon a try. I
> checked out all the files and installed everything. I can start mon
> fine and get failure notices, but I don't see anything getting logged.
> I looked through the list archives and noticed that it should be
> logging to syslog, but there are no entries there.

Jae,

The only differences with how Mon uses syslog between 0.99.2 and the CVS 
1.2.0rc code is with how the syslog facility is chosen and how syslog is 
initialized.

Are you setting the syslog facility in your mon config, or passing it as an 
argument on the mon command line via '-O'?

-David
Permalink | Reply | 1 comment |
headers
Video Game Junkie | 22 Nov 2006 05:55
Picon

Re: CVS 1-2-0 and syslog

David,
  I didn't notice any config option for syslog. I'll try the -O flag
tomorrow when I get into work. Thanks for your help!

On 11/21/06, David Nolan <vitroth+ <at> cmu.edu> wrote:
>
>
> --On Monday, November 20, 2006 16:40:46 -0500 Video Game Junkie
> <vgjunkie <at> gmail.com> wrote:
>
> > I'm running a FC5 Linux box and was looking to give mon a try. I
> > checked out all the files and installed everything. I can start mon
> > fine and get failure notices, but I don't see anything getting logged.
> > I looked through the list archives and noticed that it should be
> > logging to syslog, but there are no entries there.
>
>
> Jae,
>
> The only differences with how Mon uses syslog between 0.99.2 and the CVS
> 1.2.0rc code is with how the syslog facility is chosen and how syslog is
> initialized.
>
> Are you setting the syslog facility in your mon config, or passing it as an
> argument on the mon command line via '-O'?
>
> -David
>
> _______________________________________________
> mon mailing list
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jeff Montagna | 29 Nov 2006 17:35
Picon

netsnmp-freespace.monitor - No log handling enabled

Anyone have an idea of why logging would suddenly be disabled?  
netsnmp-freespace.monitor was working fine yesterday then broke today.

montaj1 <at> phxics1:mon.d$ ./netsnmp-freespace.monitor sts1
No log handling enabled - turning on stderr logging
truncating integer value to 32 bits
truncating integer value to 32 bits
truncating integer value to 32 bits
montaj1 <at> phxics1:mon.d$ ./netsnmp-freespace.monitor ltxnic7
No log handling enabled - turning on stderr logging
truncating integer value to 32 bits
ltxnic7

ltxnic7:/(/dev/dsk/c0t0d0s0) total=7468 used=6002(89%) free=718  
err=/: less than 900000 free (= 736195)

Jeff Montagna
Permalink | Reply | 2 comments |
headers
Ed Ravin | 30 Nov 2006 04:53
Picon
Favicon

Re: netsnmp-freespace.monitor - No log handling enabled

Did you upgrade or downgrade the net-snmp libraries?  Googling for
"No log handling enabled - turning on stderr logging" suggests that
there is a Perl / NetSNMP library mismatch.

Another possibility is that someone installed another copy of net-snmp
/ ucd-snmp in a directory in the library path, or the library path
was changed and points to the wrong place.

On Wed, Nov 29, 2006 at 09:35:27AM -0700, Jeff Montagna wrote:
> Anyone have an idea of why logging would suddenly be disabled?  
> netsnmp-freespace.monitor was working fine yesterday then broke today.
> 
> montaj1 <at> phxics1:mon.d$ ./netsnmp-freespace.monitor sts1
> No log handling enabled - turning on stderr logging
> truncating integer value to 32 bits
> truncating integer value to 32 bits
> truncating integer value to 32 bits
> montaj1 <at> phxics1:mon.d$ ./netsnmp-freespace.monitor ltxnic7
> No log handling enabled - turning on stderr logging
> truncating integer value to 32 bits
> ltxnic7
> 
> ltxnic7:/(/dev/dsk/c0t0d0s0) total=7468 used=6002(89%) free=718  
> err=/: less than 900000 free (= 736195)
Permalink | Reply | 1 comment |
headers
Jon Meek | 1 Dec 2006 14:02

Re: Any mon-sters attending LISA '06?

I registered a bit late, but I will be there.

Jon

On Sun, 29 Oct 2006, Ed Ravin wrote:

> Hey gang, it's that time of year again.  Anyone attending LISA '06
> in DC this December?
> 
> 	-- Ed
> 
> _______________________________________________
> mon mailing list
> mon <at> linux.kernel.org
> http://linux.kernel.org/mailman/listinfo/mon
>
Permalink | Reply | 0 comments |
headers
Steven Schubiger | 1 Dec 2006 14:12
Picon

Handwritten sms.alert doesn't get executed

Hi!

I've been quite trying for a while to get a handwritten SMS executed by mon.
Everything is fine if I open a terminal and run the script with same 
parameters as defined in mon.cf -- the SMS gets send. When run
by mon, nothing happens.

Looked through the mailing list archive and found some familiar threads
which had some interesting remarks:

I checked if
* permissions are right (same as for all other alerts)
* the interpreter line was valid (same as for all other alerts)
* no absolute path specified (same as for most other alerts)
* perl -c <sms.alert>emits no warnings (same as for all other alerts)

Furthermore, I checked whether the script runs, but obviously it
doesn't. I've examined the syslog and the output generated 
from mon when called with the debugging flag, but they leave
me in a rather clueless state.

Thanks in advance,
Steven
Permalink | Reply | 2 comments |
headers
Amias Channer | 1 Dec 2006 15:09

Re: Handwritten sms.alert doesn't get executed

On Fri, 1 Dec 2006 14:12:55 +0100
Steven Schubiger <steven.schubiger <at> xwave.ch> wrote:

> Hi!
> 
> I've been quite trying for a while to get a handwritten SMS executed by mon.
> Everything is fine if I open a terminal and run the script with same 
> parameters as defined in mon.cf -- the SMS gets send. When run
> by mon, nothing happens.
> 
> Looked through the mailing list archive and found some familiar threads
> which had some interesting remarks:
> 
> I checked if
> * permissions are right (same as for all other alerts)
> * the interpreter line was valid (same as for all other alerts)
> * no absolute path specified (same as for most other alerts)
> * perl -c <sms.alert>emits no warnings (same as for all other alerts)
> 
> Furthermore, I checked whether the script runs, but obviously it
> doesn't. I've examined the syslog and the output generated 
> from mon when called with the debugging flag, but they leave
> me in a rather clueless state.

I feel your pain  , have you checked for empty lines near your 
service definitions ?

e.g.  

hostname foobar 10.0.0.2
(Continue reading)

Permalink | Reply | 1 comment |
headers
Steven Schubiger | 1 Dec 2006 16:15
Picon

Re: Handwritten sms.alert doesn't get executed

Am Freitag 01 Dezember 2006 15:09 schrieb Amias Channer:

> I feel your pain  , have you checked for empty lines near your
> service definitions ?
>
> e.g.
>
> hostname foobar 10.0.0.2
>
> watch foobar
> 	service wibble_ok
> 	service wibble_also_ok
>
> 	service wibble_will_be_ignored
>
> hostname foobaz 10.0.0.3
>
> watch foobar
>
> 	service wibble_will_also be_ignored
> 	service none_of_the_others_will_run_despite_being_ok

Yes, I had a look; there were indeed such blank lines, but removing
them didn't improve the matter in any way.

> This one bites my ass regularly especially with m4 generated configs.
>
> I'm looking at solving this problem in general and i think it can be done
> by piping the config file through sed which could run a regex to filter
> newlines around services.  That said i am wary of adding more
(Continue reading)

Permalink | Reply | 0 comments |

Gmane