Help please in setting up alerts
Hi, I'm pretty new to mon and am having trouble with configuring alerts. I get this error in email alerts and am not sure what to do to resolve it. My knowledge of Perl is virtually non-existent, so I'm not sure if it's something I've done or haven't done. I don't have any file called SSLeay.pm on the system - should it have been installed with initial setup? Thanks for any help that may be provided. -Jeff Summary output: Can't locate Net/SSLeay.pm in @INC (@INC contains: /usr/lib/perl5/5.8.3/i586-linux-thread-multi /usr/lib/perl5/5.8.3 /usr/lib/perl5/site_perl/5.8.3/i586-linux-thread-multi /usr/lib/perl5/site_perl/5.8.3 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.3/i586-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.3 /usr/lib/perl5/vendor_perl .) at /usr/lib/mon/mon.d/https.monitor line 37. Group : WWW-GROUPRISK Service : https Time noticed : Wed Jan 10 17:26:28 2007 Secs until next alert : Detailed text (if any) follows: --- BEGIN failed--compilation aborted at /usr/lib/mon/mon.d/https.monitor line 37. ___ mon mailing list mon@linux.kernel.org http://linux.kernel.org/mailman/listinfo/mon
Re: Help !!!
--On Wednesday, July 06, 2005 10:04 AM +0800 D K [EMAIL PROTECTED] wrote: hi, I am a Chinese, my english is poor, so I hope you can understand this letter. Yesterday I use Mon to monitor a server, I hope Mon can alert via xmpp protocol, so I wrote a alert file, but mon seem not work. If I execute alert file, it canalert to my jabber. Now I hope mon can monitor a services is down, it can alert to my jabber. Please Help me! I wait your reply! Thanks!!! A Helper 2005.7.6 Your english isn't too bad, but your problem reporting skills definitely need some work. In order to be able to help you, we need to know in what way mon isn't working. What did you do, what behavior did you expect, and what behavior did mon show? Is mon detecting your failure and not calling the alert, or calling the alert but it fails to behave as desired? Or is mon not detecting the failure at all. If your script works when you run it but not when Mon runs it, the most likely causes are: - $PATH differences (i.e. your script is running some program that appears in your PATH but not in the PATH that mon provides to the alert script) - privilege difference. i.e you ran your test as root but Mon is running as nobody, or similar. We need more information in order to provide any better guidance for solving your problem. -David David Nolan*[EMAIL PROTECTED] curses: May you be forced to grep the termcap of an unclean yacc while a herd of rogue emacs fsck your troff and vgrind your pathalias! ___ mon mailing list mon@linux.kernel.org http://linux.kernel.org/mailman/listinfo/mon
Re: Help with mon and process.monitor
--On Tuesday, January 11, 2005 2:07 PM +1100 Craig Reeson [EMAIL PROTECTED] wrote: Now I am getting a SNMP timeout issue (using monshow.cgi). I have tried increasing the timeout in process.monitor but it has made no difference. However, if I just run 'process.monitor -c mycom 172.28.47.60' then it works! I assume your test runs of process.monitor are on the same machine as your mon server. Are you logged in as the user that your mon server runs as? i.e. could it be something about your login environment thats allowing the script to work. Can you post a snippet of your mon.cfg, showing the group definition and the service definition? Also, you might want to try running this monitor script to verify that SNMP transactions with the target host are working. https://bugzilla.andrew.cmu.edu/cgi-bin/cvsweb.cgi/~checkout~/src/netsage/mon/mon.d/host.monitor?rev=1.9 (Thats the script we use to verify that the host is responding to snmp, and test the load average.) -David Nolan Network Software Designer Computing Services Carnegie Mellon University ___ mon mailing list mon@linux.kernel.org http://linux.kernel.org/mailman/listinfo/mon
Help with mon and process.monitor
Guys, I am still having difficulty getting this to work (fixed previous issues, the mon.cf I was given was wrong). Now I am getting a SNMP timeout issue (using monshow.cgi). I have tried increasing the timeout in process.monitor but it has made no difference. However, if I just run 'process.monitor -c mycom 172.28.47.60' then it works! Any ideas? Need more details? Thanks, Craig --- This email and any files transmitted with it are solely intended for the use of the addressee(s) and may contain information that is confidential and privileged. If you receive this email in error, please advise us by return email immediately. Please also disregard the contents of the email, delete it and destroy any copies immediately. Computershare Limited and its subsidiaries do not accept liability for the views expressed in the email or for the consequences of any computer viruses that may be transmitted with this email. This email is also subject to copyright. No part of it should be reproduced, adapted or transmitted without the written consent of the copyright owner. ___ mon mailing list mon@linux.kernel.org http://linux.kernel.org/mailman/listinfo/mon
RE: Help with mon.cf switches
Ok, thanks again for everybodies help
I am beginning to understand the way Mon works :)
Anyway, I believe I have made some progress..
Mon now gives me the green light on my process monitoring, BUT I get an
error like such:
Server1 returned an SNMP error: Unknown user name
Any ideas?
Thanks,
Craig
-Original Message-
From: zalktis [mailto:[EMAIL PROTECTED]
Sent: Friday, 7 January 2005 9:49
To: Craig Reeson
Subject: RE: Help with mon.cf switches
Hi,
Arguments (parameters) of mon server and process.monitor spawned for
particular watchgroup is completely different things. Maybe - that's the
problem?
To use process.monitor you should:
- install UCD-SNMP/NetSNMP software on target host
- configure snmpd on target host, e.g:
proc httpd 10 20
# number of httpd-s should be between 10 and 20
- start snmpd on target host
(target host = host to check)
Then you can manually check (from mon server shell):
$ process.monitor -c SNMP_community_if_not_public host
or you can add service in mon.cf which will be periodically checked by
mon server using process.monitor. e.g:
# example
--
hostgroup billing bill01.domain.com
watchgroup billing
service ping
service disk-space
...
...
service proc
exclude_period wd{sun-sat},hr{18-7}
description Check of billing processes
depend SELF:ping
interval 35m
randskew 25s
monitor process.monitor
failure_interval 5m
period
alertafter 2
alert mail.alert [EMAIL PROTECTED]
upalertafter 10s
upalert mail.alert -u [EMAIL PROTECTED]
--
z
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
---
This email and any files transmitted with it are solely intended for the use of
the addressee(s) and may contain information that is confidential and
privileged. If you receive this email in error, please advise us by return
email immediately. Please also disregard the contents of the email, delete it
and destroy any copies immediately.
Computershare Limited and its subsidiaries do not accept liability for the
views expressed in the email or for the consequences of any computer viruses
that may be transmitted with this email.
This email is also subject to copyright. No part of it should be reproduced,
adapted or transmitted without the written consent of the copyright owner.
___
mon mailing list
mon@linux.kernel.org
http://linux.kernel.org/mailman/listinfo/mon
Re: Help with mon.cf switches
On Wed, 5 Jan 2005, Craig Reeson wrote: Guys, I'm new to Mon and have taken over a non working install of Mon which I desperately need to get working... Anyway, what does the -P option mean/do? Ie. monitor process.monitor -P augw -C /etc/mon/process.monitor.conf for process.monitor, -P does nothing. i'm not sure what you're trying to do or from where you got that example, but if you elaborate then maybe i can help out. ___ mon mailing list mon@linux.kernel.org http://linux.kernel.org/mailman/listinfo/mon
RE: Help with mon.cf switches
Thanks for everybody's help so far...
It has been mentioned that the -P and -C switches are no longer
supported/used in mon-0.99.2
So what should I replce these switches with? (I am running Debian
testing w/ 0.99.2-7)
Here is a larger section of my mon.cf:
# global options
#
cfbasedir = /etc/mon
alertdir= /usr/lib/mon/alert.d
mondir = /usr/lib/mon/mon.d
maxprocs= 20
histlength = 100
randstart = 60s
authtype = getpwnam
###
# After a failover, the monitor will be monitoring the wrong boxes.
# Simply swap the MAINAUPROD and BACKAUPROD
# The Main Australian ORMS box
hostgroup MAINAUPROD 172.28.xx.xx
# The Backup Australian ORMS box
hostgroup BACKAUPROD 172.28.xx.xx
# The first hop before the production subnet
hostgroup DMZ_ROUTER 203.xx.xx.xx
# The Chicago ORMS boxes
hostgroup MAINNAPROD chilorms1.cshare.com
hostgroup chilgw 57.35.xx.xx
# SMS alerting check
hostgroup SMS_Test 127.0.0.1
# cmtdemo
hostgroup CMTDEMO cmtdemo
###
# Send a test SMS each day to check SMS alerting is actually still
working.
#
watch SMS_Test
service SMS_Test
description Test failure for SMS alerting. This has been
set to fail once per day to test the SMS message alerting. Disregard
this failure.
interval 50m
monitor daily_sms.monitor Daily SMS test
period wd {Sun-Sat}
alert smsclient.alert craig
alertevery 1h
###
# Main Australian ORMS production box
#
watch MAINAUPROD
service Ping
description Ping ORMS box
interval 15s
monitor fping.monitor -r 3
period LOW1: hr {22-06}
alert mail.alert
[EMAIL PROTECTED]
alertevery 8h
alertafter 3
period HIGH1: hr {06-22}
alert mail.alert
[EMAIL PROTECTED]
alertevery 1h
alertafter 3
period LOW2: hr {22-06}
alert smsclient.alert craig
alertevery 8h
alertafter 3
period HIGH2: hr {06-22}
alert smsclient.alert craig
alertevery 1h
alertafter 3
service RE_Procs
description ORMS Routing Engine processes
interval 1m
monitor process.monitor -P
RoutingEngine,BCServer,TSMRServ,RETimer,TableDownloadSe,DBIntradayUpdat,
GenericServer,SOGWReport,dataserver,backupserver -C /etc/mon/proce
ss.monitor.conf
period LOW1: hr {22-06}
alert mail.alert
[EMAIL PROTECTED]
alertevery 8h
alertafter 1
period HIGH1: hr {06-22}
alert mail.alert
[EMAIL PROTECTED]
alertevery 1h
alertafter 1
period LOW2: hr {22-06}
alert smsclient.alert craig
alertevery 8h
alertafter 1
period HIGH2: hr {06-22}
alert smsclient.alert craig
alertevery 1h
alertafter 1
service ETrade_Australia_Gateway
description ORMS ETrade Australia Gateway processes
interval 1m
monitor process.monitor -P etradeaugw -C
/etc/mon/process.monitor.conf
period MORNING1: wd {2-6} hr {09} min {30-59}
alert mail.alert
[EMAIL PROTECTED]
alertevery 1h
alertafter 1
period DAY1: wd {2-6} hr {10-15}
alert mail.alert
[EMAIL PROTECTED]
alertevery 1h
alertafter 1
period ARVO1: wd {2-6} hr {16} min {0-29}
alert mail.alert
[EMAIL PROTECTED]
alertevery 1h
alertafter 1
period MORNING2: wd {2-6} hr {09} min {30-59}
alert smsclient.alert craig
alertevery 1h
alertafter 1
period DAY2: wd {2-6} hr {10-15}
alert smsclient.alert craig
alertevery 1h
alertafter 1
period ARVO2: wd {2-6} hr {16} min {0-29}
alert smsclient.alert craig
alertevery 1h
alertafter 1
-Original Message-
From: Jim Trocki [mailto:[EMAIL PROTECTED]
Sent: Thursday
help!
I want to know some information about the archive and the principleof mon.Whocan tell me where i can find some materlsabout these. Thank you !Do You Yahoo!? 150MP3 1G1000___ mon mailing list [EMAIL PROTECTED] http://linux.kernel.org/mailman/listinfo/mon
RE: Mon Server Goes Foobar, help!
Hey All, Im doing some more research into this. A ran d:Profile for perl and found that 96% of the time is spent in Sys::Syslog::_syslog_send_socket. Is this normal? Thanks. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gary Richardson Sent: Friday, January 09, 2004 8:09 PM To: [EMAIL PROTECTED] Subject: Mon Server Goes Foobar, help! Hey, I have a mon server that has been running fine for a few months. All of a sudden it is doing crazy things. We are using mon.cgi for reporting. It is now timing out 9 out of 10 times. When you telnet to the mon port and try to issue commands, sometimes it hangs for a long time and others it hangs for 10 seconds. Running top shows all of the monitors going off at the same time instead of the normal random intervals. I have a feeling this is related. I have a feeling that a perl module got upgraded in the background and is causing this problem. There havent been any configuration changes since before Christmas. Has anyone experienced this or something similar before? Thanks. ___ mon mailing list [EMAIL PROTECTED] http://linux.kernel.org/mailman/listinfo/mon
RE: Mon Server Goes Foobar, help!
--On Monday, January 12, 2004 12:09 PM -0800 Gary Richardson [EMAIL PROTECTED] wrote: I'm doing some more research into this. A ran --d:Profile for perl and found that 96% of the time is spent in Sys::Syslog::_syslog_send_socket. Is this normal? Sounds like your syslog server may be having problems. But then I've never run Mon in the Profiler, so I don't know if thats really abnormal. Try disabling syslog's from Mon and see if that helps. The other situation in which I've seen Mon have problems like yours is when an alert script is hanging. But I don't have that problem any more, because I've long since patched my copy of Mon to handle fork alerts cleanly, and clean them up during the normal child processing code. -David Nolan Network Software Developer Computing Services Carnegie Mellon University ___ mon mailing list [EMAIL PROTECTED] http://linux.kernel.org/mailman/listinfo/mon
RE: Mon Server Goes Foobar, help!
On Mon, 12 Jan 2004, Gary Richardson wrote: I'm doing some more research into this. A ran -d:Profile for perl and found that 96% of the time is spent in Sys::Syslog::_syslog_send_socket. Is this normal? Maybe the output logfile is set to fsync-on-write. This is the (unfortunate) default for some syslogs. Try prepending the filename with a '-' to turn it off, like: local1.*-/var/log/mon.log NB not all syslogs support this, check your local man pages for details. -- Eric Sorenson - Systems / Network Administrator, MIS - Transmeta Corporation ___ mon mailing list [EMAIL PROTECTED] http://linux.kernel.org/mailman/listinfo/mon
RE: Mon Server Goes Foobar, help!
For the mailing list archives, it turns out there was a routing problem preventing our name servers from reaching our ISP's authoritative name servers. This stopped us from getting reverse DNS for our internet address space which caused our syslog server (which was functioning as a syslog collector) to block. Mon would then wait on the block. Thanks for all the help guys. Without it, it would have been a long time before I found the problem. Out. -Original Message- From: Eric Sorenson [mailto:[EMAIL PROTECTED] Sent: Monday, January 12, 2004 12:45 PM To: Gary Richardson Cc: [EMAIL PROTECTED] Subject: RE: Mon Server Goes Foobar, help! On Mon, 12 Jan 2004, Gary Richardson wrote: I'm doing some more research into this. A ran -d:Profile for perl and found that 96% of the time is spent in Sys::Syslog::_syslog_send_socket. Is this normal? Maybe the output logfile is set to fsync-on-write. This is the (unfortunate) default for some syslogs. Try prepending the filename with a '-' to turn it off, like: local1.*-/var/log/mon.log NB not all syslogs support this, check your local man pages for details. -- Eric Sorenson - Systems / Network Administrator, MIS - Transmeta Corporation ___ mon mailing list [EMAIL PROTECTED] http://linux.kernel.org/mailman/listinfo/mon
Mon Server Goes Foobar, help!
Hey, I have a mon server that has been running fine for a few months. All of a sudden it is doing crazy things. We are using mon.cgi for reporting. It is now timing out 9 out of 10 times. When you telnet to the mon port and try to issue commands, sometimes it hangs for a long time and others it hangs for 10 seconds. Running top shows all of the monitors going off at the same time instead of the normal random intervals. I have a feeling this is related. I have a feeling that a perl module got upgraded in the background and is causing this problem. There havent been any configuration changes since before Christmas. Has anyone experienced this or something similar before? Thanks. ___ mon mailing list [EMAIL PROTECTED] http://linux.kernel.org/mailman/listinfo/mon
Help with authentication
Hi all, this is my problem: 1) I set the following in mon.cf: authtype = userfile userfile = /usr/local/mon/etc/userfile 2) and create userfile with: /usr/local/apache/bin/htpasswd -c /usr/local/mon/etc/userfile root 3) restarted the mon server While accessing from the mon.cgi web interface (v.1.52) I cannot perform some reserved tasks and I got the following errors: Could not reload auth mon server on server localhost: 520 command could not be executed (perhaps you don't have permissions in auth.cf?) What's missing? Thank you. Emanuele Zanotti ___ mon mailing list [EMAIL PROTECTED] http://linux.kernel.org/mailman/listinfo/mon
Re: Help with authentication
In addition to setting up a userfile and creating a user, which you did, you also need to make sure that the auth.cf file is set up properly for that user. Also make sure that the user mon runs as has permissions to read the userfile and auth.cf file. On Mon, 28 Jul 2003, Emanuele Zanotti wrote: Hi all, this is my problem: 1) I set the following in mon.cf: authtype = userfile userfile = /usr/local/mon/etc/userfile 2) and create userfile with: /usr/local/apache/bin/htpasswd -c /usr/local/mon/etc/userfile root 3) restarted the mon server While accessing from the mon.cgi web interface (v.1.52) I cannot perform some reserved tasks and I got the following errors: Could not reload auth mon server on server localhost: 520 command could not be executed (perhaps you don't have permissions in auth.cf?) What's missing? Thank you. Emanuele Zanotti ___ mon mailing list [EMAIL PROTECTED] http://linux.kernel.org/mailman/listinfo/mon ___ mon mailing list [EMAIL PROTECTED] http://linux.kernel.org/mailman/listinfo/mon
help with ping service
Hi all, I am new to mon. After installing it I have this error message from the 'monshow --full' command for the ping service (using the default fping.monitor): could not open pipe to fping: No such file or directory However, fping is working fine and fping.monitor as well. Any suggestions? Thank you. -Emanuele ___ mon mailing list [EMAIL PROTECTED] http://linux.kernel.org/mailman/listinfo/mon
RE: Hello !!! I would like a help please .... it´s about snmp2montrap....
Sorry
I misunderstood you... What I told you to do would ignore the messages what you
really want to do is map it intoa serivce watch statement so you'll want
it something like this added to the $Patterns hash...
-
'\.iso\.org\.dod\.internet\.snmpV2\.snmpModules\.snmpMIB\.snmpMIBObjects\.snmpTraps\.linkDown'
= {
group =
'IFMIB',
service =
'link',
status = 'ok',},
'\.iso\.org\.dod\.internet\.snmpV2\.snmpModules\.snmpMIB\.snmpMIBObjects\.snmpTraps\.linkUp'
= {
group =
'IFMIB',
service =
'link,
status = 'ok',},
--
Then in your mon.cf you can add a watch for it
something like
---
watchIFMIB
servicelink description SNMP Link Status
traps period wd
{Sun-Sat} alert mail.alertbob
joe upalert mail.alert -u bob
joe
-
Hope this
helps
-Original Message-From: André Leão
[mailto:[EMAIL PROTECTED]]Sent: Friday, November 08, 2002 11:18
AMTo: Ralph.BuggCc:
[EMAIL PROTECTED]Subject: RE: Hello !!! I would like a help
please it´s about snmp2montrap
Thank you for yor
suggestion, but i don´t know perl so much but i tried to do this and
it´s no working fine and, i would like to receive LinkUP
and LinkDown
Traps...
These traps are linkUp traps which get generated whenever an
interface comes up... I'm guessing that you are getting them when the
machines bootup.
If you don't care about them what you could do is add this to the
$Patterns hash in snmp2montrap
'\.iso\.org\.dod\.internet\.snmpV2\.snmpModules\.snmpMIB\.snmpMIBObjects\.snmpTraps\.linkUp'
= { ignore = 1},
and that will silently ignore the linkUp traps (you'll probably
want to add linkDown traps as well)
-Original Message-From: André Leão
[mailto:[EMAIL PROTECTED]]Sent: Tuesday, November 05,
2002 3:06 PMTo: [EMAIL PROTECTED]Subject:
Hello !!! I would like a help please it´s about
snmp2montrap
my snmptrapd.conf
traphandledefault
/etc/snmp2montrap
When i receiveany trap i always
receivesomething like this:
Summary output :
/etc/snmp2montrap: Unrecognized SNMP
trapGroup
:
defaultService
: defaultTime
noticed : Tue
Nov 5 17:43:09 2002Secs until next alert : Members
: defaultDetailed text (if any)
follows:---=148.5.7.130148.5.7.130system.sysUpTime.0
13:9:39:02.30.iso.org.dod.internet.snmpV2.snmpModules.snmpMIB.snmpMIBObjects.snmpTrap.snmpTrapOID.0
.iso.org.dod.internet.snmpV2.snmpModules.snmpMIB.snmpMIBObjects.snmpTraps.linkUp.iso.org.dod.internet.snmpV2.snmpModules.snmpCommunityMIB.snmpCommunityMIBObjects.snmpTrapAddress.0
192.168.0.130.iso.org.dod.internet.snmpV2.snmpModules.snmpCommunityMIB.snmpCommunityMIBObjects.snmpTrapCommunity.0
"public".iso.org.dod.internet.snmpV2.snmpModules.snmpMIB.snmpMIBObjects.snmpTrap.snmpTrapEnterprise.0
enterprises.3.1.1=
I receive traps of Windows 2000 server,
Linux, Cisco routers, Cyclades routers, Cisco Switchand
it´s the same thing.
i hope you help me please...
Thank you so lot.
André Guizarde Q. de
Leão Suporte TécnicoSysdata
Sistemas Integrados (91) 3084 1610
(Direto) (91) 3084 1600
(Geral) 0300-789-2214
RE: Hello !!! I would like a help please .... it´s about snmp2montrap....
Thank you for yor
suggestion, but i don´t know perl so much but i tried to do this and it´s
no working fine and, i would like to receive LinkUP
and LinkDown
Traps...
These traps are linkUp traps which get generated whenever an
interface comes up... I'm guessing that you are getting them when the
machines bootup.
If you don't care about them what you could do is add this to the
$Patterns hash in snmp2montrap
'\.iso\.org\.dod\.internet\.snmpV2\.snmpModules\.snmpMIB\.snmpMIBObjects\.snmpTraps\.linkUp'
= { ignore = 1},
and that will silently ignore the linkUp traps (you'll probably
want to add linkDown traps as well)
-Original Message-From: André Leão
[mailto:[EMAIL PROTECTED]]Sent: Tuesday, November 05, 2002
3:06 PMTo: [EMAIL PROTECTED]Subject: Hello !!!
I would like a help please it´s about
snmp2montrap
my snmptrapd.conf
traphandledefault
/etc/snmp2montrap
When i receiveany trap i always
receivesomething like this:
Summary output : /etc/snmp2montrap:
Unrecognized SNMP
trapGroup
:
defaultService
: defaultTime
noticed : Tue
Nov 5 17:43:09 2002Secs until next alert : Members
: defaultDetailed text (if any)
follows:---=148.5.7.130148.5.7.130system.sysUpTime.0
13:9:39:02.30.iso.org.dod.internet.snmpV2.snmpModules.snmpMIB.snmpMIBObjects.snmpTrap.snmpTrapOID.0
.iso.org.dod.internet.snmpV2.snmpModules.snmpMIB.snmpMIBObjects.snmpTraps.linkUp.iso.org.dod.internet.snmpV2.snmpModules.snmpCommunityMIB.snmpCommunityMIBObjects.snmpTrapAddress.0
192.168.0.130.iso.org.dod.internet.snmpV2.snmpModules.snmpCommunityMIB.snmpCommunityMIBObjects.snmpTrapCommunity.0
"public".iso.org.dod.internet.snmpV2.snmpModules.snmpMIB.snmpMIBObjects.snmpTrap.snmpTrapEnterprise.0
enterprises.3.1.1=
I receive traps of Windows 2000 server,
Linux, Cisco routers, Cyclades routers, Cisco Switchand it´s
the same thing.
i hope you help me please...
Thank you so lot.
André Guizarde Q. de
Leão Suporte TécnicoSysdata
Sistemas Integrados (91) 3084 1610
(Direto) (91) 3084 1600
(Geral) 0300-789-2214
Hello !!! I would like a help please .... it´s about snmp2montrap....
my snmptrapd.conf traphandledefault /etc/snmp2montrap When i receiveany trap i always receivesomething like this: Summary output : /etc/snmp2montrap: Unrecognized SNMP trapGroup : defaultService : defaultTime noticed : Tue Nov 5 17:43:09 2002Secs until next alert : Members : defaultDetailed text (if any) follows:---=148.5.7.130148.5.7.130system.sysUpTime.0 13:9:39:02.30.iso.org.dod.internet.snmpV2.snmpModules.snmpMIB.snmpMIBObjects.snmpTrap.snmpTrapOID.0 .iso.org.dod.internet.snmpV2.snmpModules.snmpMIB.snmpMIBObjects.snmpTraps.linkUp.iso.org.dod.internet.snmpV2.snmpModules.snmpCommunityMIB.snmpCommunityMIBObjects.snmpTrapAddress.0 192.168.0.130.iso.org.dod.internet.snmpV2.snmpModules.snmpCommunityMIB.snmpCommunityMIBObjects.snmpTrapCommunity.0 "public".iso.org.dod.internet.snmpV2.snmpModules.snmpMIB.snmpMIBObjects.snmpTrap.snmpTrapEnterprise.0 enterprises.3.1.1= I receive traps of Windows 2000 server, Linux, Cisco routers, Cyclades routers, Cisco Switchand it´s the same thing. i hope you help me please... Thank you so lot. André Guizarde Q. de Leão Suporte TécnicoSysdata Sistemas Integrados (91) 3084 1610 (Direto) (91) 3084 1600 (Geral) 0300-789-2214
alerts not found in 99.2 -help-
Hello:
I'm upgrading mon from an old version of mon to .99.2 on tru64. We are
using perl 5.6.0.
Everything is fine, except that for some reason I _cannot_ get mon to read
alerts in alert.d directory. Then it begins to even refuse to see the
mail.alerts which are untouched.
Did something in the mon.cf file format change?
I use two alerts-- the mail.alert for problems and a custom 'service
availability' alert (nesavail.alert) that is called every 10min, plus an
upalert which also calls the nesavail.alert.
I've gone thru a complete fresh install of mon twice, and torn apart the
main mon script (playing with paths) to try and get mon to read the alerts
which are plainly there.
Here is the syslog output of mon starting:
...
Sep 24 08:34:17 koi mon[252109]: mail.alert not found in one of
(@alerttdirs[/usr/local/lib/mon/alert.d])
Sep 24 08:34:17 koi mon[252109]: nesavail.alert not found in one of
(@alerttdirs[/usr/local/lib/mon/alert.d])
Sep 24 08:34:17 koi mon[252109]: nesavail.alert not found in one of
(@alerttdirs[/usr/local/lib/mon/alert.d])
Sep 24 08:34:17 koi mon[252109]: mail.alert not found in one of
(@alerttdirs[/usr/local/lib/mon/alert.d])
Sep 24 08:34:17 koi mon[252109]: mon server started
here is how I'm starting mon to test:
mon@koi:~$ MONHOME=/usr/local/lib/mon
mon@koi:~$ export MONHOME
mon@koi:~$ ./mon -c etc/mon.cf -A $MONHOME/etc/auth.cf -b `pwd`
and finally, here is a sample of a watch in my mon.cf:
watch listserv
service smtp
interval 10m
monitor smtp3.monitor -t 30
period wd {Mon-Sun}
alertevery 4h
alertafter 2 30m
alert mail.alert mon-listserv@isc
period wd {Mon-Sun}
alertevery 10m
alert nesavail.alert
upalert nesavail.alert
Why is mon refusing to acknowledge these alerts which is plainly there in
the alert.d directory?
_Andy Diller_
Sudan Acid
___
mon mailing list
[EMAIL PROTECTED]
http://linux.kernel.org/mailman/listinfo/mon
alerts not found in 99.2 -help- (fwd)
Hello:
I'm upgrading mon from an old version of mon to .99.2 on tru64. We are
using perl 5.6.0.
Everything is fine, except that for some reason I _cannot_ get mon to read
alerts in alert.d directory. Then it begins to even refuse to see the
mail.alerts which are untouched.
Did something in the mon.cf file format change?
I use two alerts-- the mail.alert for problems and a custom 'service
availability' alert (nesavail.alert) that is called every 10min, plus an
upalert which also calls the nesavail.alert.
I've gone thru a complete fresh install of mon twice, and torn apart the
main mon script (playing with paths) to try and get mon to read the alerts
which are plainly there.
Here is the syslog output of mon starting:
...
Sep 24 08:34:17 koi mon[252109]: mail.alert not found in one of
(@alerttdirs[/usr/local/lib/mon/alert.d]) Sep 24 08:34:17 koi mon[252109]:
nesavail.alert not found in one of (@alerttdirs[/usr/local/lib/mon/alert.d])
Sep 24 08:34:17 koi mon[252109]: nesavail.alert not found in one of
(@alerttdirs[/usr/local/lib/mon/alert.d]) Sep 24 08:34:17 koi mon[252109]:
mail.alert not found in one of (@alerttdirs[/usr/local/lib/mon/alert.d])
Sep 24 08:34:17 koi mon[252109]: mon server started
here is how I'm starting mon to test:
mon@koi:~$ MONHOME=/usr/local/lib/mon
mon@koi:~$ export MONHOME
mon@koi:~$ ./mon -c etc/mon.cf -A $MONHOME/etc/auth.cf -b `pwd`
and finally, here is a sample of a watch in my mon.cf:
watch listserv
service smtp
interval 10m
monitor smtp3.monitor -t 30
period wd {Mon-Sun}
alertevery 4h
alertafter 2 30m
alert mail.alert mon-listserv@isc
period wd {Mon-Sun}
alertevery 10m
alert nesavail.alert
upalert nesavail.alert
Why is mon refusing to acknowledge these alerts which is plainly there in
the alert.d directory?
_Andy Diller_
___
mon mailing list
[EMAIL PROTECTED]
http://linux.kernel.org/mailman/listinfo/mon
Re: alerts not found in 99.2 -help- (fwd)
--On Tuesday, September 24, 2002 8:55 AM -0400 Andy Diller [EMAIL PROTECTED] wrote: Why is mon refusing to acknowledge these alerts which is plainly there in the alert.d directory? My first guess would be a permissions problem. Either the alerts aren't executable, or they aren't readable by the user your mon server is running as. (Or the directory isn't readable, etc.) Have you verified the permissions are set correctly? -David Nolan Network Software Developer Computing Services Carnegie Mellon University ___ mon mailing list [EMAIL PROTECTED] http://linux.kernel.org/mailman/listinfo/mon
Re: alerts not found in 99.2 -help- (fwd)
Ok, they needed the execute bit set. Sigh.. thanks! --On Tuesday, September 24, 2002 9:56 AM -0400 David Nolan [EMAIL PROTECTED] wrote: My first guess would be a permissions problem. Either the alerts aren't executable, or they aren't readable by the user your mon server is running as. (Or the directory isn't readable, etc.) Have you verified the permissions are set correctly? -David Nolan Network Software Developer Computing Services Carnegie Mellon University _Andy Diller_ Sudan Acid ___ mon mailing list [EMAIL PROTECTED] http://linux.kernel.org/mailman/listinfo/mon
RE: Please help - syslog_facility
Markus,
The facility in syslog is akin to a channel or file number.
A syslog client always sends every log message to syslog, along with the
facility and priority.
Syslog checks its config line by line to see if it finds a matching
facility and logs messages of the indicated or higher priority.
Normally, you'd have an entry like
*.notice;mail.none;authpriv.none/var/log/messages
and the messages you get (daemon.notice) match that, that's why you see
them in /var/log/messages.
So, first set the syslog facility in mon.cf to an unused localx, let's
say local2.
Then, depending on your needs, you can either suppress mon's messages at
all:
*.notice;mail.none;authpriv.none;local2.none
/var/log/messages
or you limit them to info and higher:
*.notice;mail.none;authpriv.none;local2.info
/var/log/messages
or you send mon's output elsewhere (e.g. again only info higher):
*.notice;mail.none;authpriv.none;local2.none
/var/log/messages
local2.info
/var/log/mon
(In the latter case, remember to include the new log file in the log
rotation scheme you use!)
Regards,
--Peter Holzleitner
Group Leader, Operations
Information Technology and Knowledge Management (IPC/ITKM)
United Nations Industrial Development Organization (UNIDO)
Vienna, Austria http://www.unido.org
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 15, 2002 1:47 PM
To: [EMAIL PROTECTED]
Subject: Please help - syslog_facility
I am a newbie and don´t unterstand the syslog_facility option:
I have a SUSE 7.3 Linux
I found a file /etc/syslog.conf
I read the man syslog and man syslog.conf
I know there is the facitlity:
auth,
auth-priv,cron,daemon,kern,lpr,mail,mark,news,security,syslog,user
uusp, local0 through local7
I know there is the priority:
debug,info,notice,warning,warn,error,crit,alert,panic
I know there is the mon.conf:
syslog_facility = daemon (default)
Or there is the parameter -0 facility
/usr/local/mon/mon -O facility
I look at the perl code and find Hardcoded following commands:
syslog('info', client command \$l\)
info = priority ?!
My cgi-script with the mon-client command makes many queries (html
refresh=5);
On the remote server, there are many mon entries in the
/var/log/messages
...
e.g.
Jan 15 13:29:35 pc426 mon[20686]: client connection from
172.20.12.216:34029
Jan 15 13:29:35 pc426 mon[20686]: client command protid 9745
Jan 15 13:29:35 pc426 mon[20686]: client command list failures
Jan 15 13:29:35 pc426 mon[20686]: client connection from
172.20.12.216:34030
Jan 15 13:29:36 pc426 mon[20686]: client command protid 9745
Jan 15 13:29:36 pc426 mon[20686]: client command list disabled
Jan 15 13:29:36 pc426 mon[20686]: client connection from
172.20.12.216:34031
Jan 15 13:29:37 pc426 mon[20686]: client command protid 9745
Jan 15 13:29:37 pc426 mon[20686]: client command list disabled
Jan 15 13:29:37 pc426 mon[20686]: client connection from
172.20.12.216:34032
Jan 15 13:29:38 pc426 mon[20686]: client command protid 9745
Jan 15 13:29:38 pc426 mon[20686]: client command list disabled
Jan 15 13:34:38 pc426 mon[20686]: client connection from
172.20.12.216:34061
Jan 15 13:34:38 pc426 mon[20686]: client command protid 9745
Jan 15 13:34:38 pc426 mon[20686]: client command list failures
Jan 15 13:34:38 pc426 mon[20686]: client connection from
172.20.12.216:34062
Jan 15 13:34:39 pc426 mon[20686]: client command protid 9745
Jan 15 13:34:39 pc426 mon[20686]: client command list disabled
Jan 15 13:34:39 pc426 mon[20686]: client connection from
172.20.12.216:34063
Jan 15 13:34:40 pc426 mon[20686]: client command protid 9745
Jan 15 13:34:40 pc426 mon[20686]: client command list disabled
Jan 15 13:34:40 pc426 mon[20686]: client connection from
172.20.12.216:34064
Jan 15 13:34:41 pc426 mon[20686]: client command protid 9745
Jan 15 13:34:41 pc426 mon[20686]: client command list disabled
How can I disable this many info mon messages in the
/var/log/messages file
Can I use the syslog_facility for my problem ?
Please help
Thanks
Markus
Markus Lehmann
Netzwerkmanagment
PALMERS TEXTIL AG
A-2351 Wiener Neudorf
Palmersstrasse 6-8
Tel.: +43 (2236) 63 500 244
Fax.: +43 (2236) 63 533 244
@mail: [EMAIL PROTECTED]
Peter HOLZLEITNER (E-mail).vcf
Description: Binary data
