|
Hello, I'm back with a strange virtualserver.alert issue. I tried with a
ftp.monitor and a http.monitor (telnet.monitor gave me an error like:
192.168.82.20: did not get prompt: pattern match timed-out). I ran mon and I
have no mail until I unplug the computer. It gives me an Alert and
virtualserver.alert removes the service from the ipvsadm table, so everything
is fine until here. But when I plug the server back in, although I get the
expecte UPALERT, it doesn't add the service in the ipvsadm table. After the
UPALERT mail I do not get any other mail. Maybe I did something wrong in the
mon.cf, here is the listing:
alertdir = /usr/lib/mon/alert.d/
mondir = /usr/lib/mon/mon.d/
#mon wants writes to a state file, or else will fill your syslog file with
complaints.
#The default statedir is the same as the alertdir (or basedir)
#However I don't want anything writing to /usr so put it in the log file
directory.
#you need to touch files 'opstatus' and 'disabled' in statedir, or mon will
complain about not being able to open statedir #files.
statedir = /var/adm/
#maxprocs = 20
histlength = 100
#delay before starting
#randstart = 60s
#------
hostgroup LVS1 192.168.82.20
watch LVS1
#the string/text following service (to OEL) is put in header of mail messages
#service "ftp on LVS1 192.168.82.20"
service http
interval 15s
monitor http.monitor
allow_empty_group
period wd {Sun-Sat}
#numalerts 2
#alertevery 1h
alert mail.alert root
upalert mail.alert root
alert test.alert
upalert test.alert
#-V is virtual service, -R is remote service, -P is protocol, -A is
add/delete (t|u)
alert virtualserver.alert -A -d -P -t -V 192.168.82.100:80 -R
192.168.82.20
upalert virtualserver.alert -A -a -P -t -V 192.168.82.100:80 -R
192.168.82.20 -T -q -w 1
#the line above must be blank
here is some listing from test.alert.log:
Wed Mar 22 17:44:49 EET 2006 -s ftp -g LVS1 -h 192.168.82.20 -t 1143042289
---here I unplug the server
Wed Mar 22 17:44:54 EET 2006 -s ftp -g LVS1 -h 192.168.82.20 -t 1143042294
Wed Mar 22 17:44:59 EET 2006 -s ftp -g LVS1 -h 192.168.82.20 -t 1143042299
Wed Mar 22 17:45:12 EET 2006 -s ftp -g LVS1 -h 192.168.82.20 -t 1143042312
Wed Mar 22 17:45:26 EET 2006 -s ftp -g LVS1 -h 192.168.82.20 -t 1143042326
Wed Mar 22 17:45:39 EET 2006 -s ftp -g LVS1 -h 192.168.82.20 -t 1143042339 -u
---here I plug it back, so it looks good,as
I have the -u
some mail listing:
From root@xxxxxxxxxxxxxxxxxxxxx Wed Mar 22 17:44:49 2006
Return-Path: <root@xxxxxxxxxxxxxxxxxxxxx>
Received: from localhost.localdomain (Fedora [127.0.0.1])
by localhost.localdomain (8.13.4/8.13.4) with ESMTP id k2MFim29007166
for <root@xxxxxxxxxxxxxxxxxxxxx>; Wed, 22 Mar 2006 17:44:48 +0200
Received: (from root@localhost)
by localhost.localdomain (8.13.4/8.13.4/Submit) id k2MFimn2007165;
Wed, 22 Mar 2006 17:44:48 +0200
Date: Wed, 22 Mar 2006 17:44:48 +0200
From: root <root@xxxxxxxxxxxxxxxxxxxxx>
Message-Id: <200603221544.k2MFimn2007165@xxxxxxxxxxxxxxxxxxxxx>
To: root@xxxxxxxxxxxxxxxxxxxxx
Subject: ALERT LVS1/ftp: 192.168.82.20 (Wed Mar 22 17:44:48)
X-Mailer: /usr/lib/mon/alert.d/mail.alert
Summary output : 192.168.82.20
Group : LVS1
Service : ftp
Time noticed : Wed Mar 22 17:44:48 2006
Secs until next alert :
Members : 192.168.82.20
Detailed text (if any) follows:
-------------------------------
HOST 192.168.82.20: connect: No route to host
From root@xxxxxxxxxxxxxxxxxxxxx Wed Mar 22 17:44:59 2006
Return-Path: <root@xxxxxxxxxxxxxxxxxxxxx>
Received: from localhost.localdomain (Fedora [127.0.0.1])
by localhost.localdomain (8.13.4/8.13.4) with ESMTP id k2MFixUK007188
for <root@xxxxxxxxxxxxxxxxxxxxx>; Wed, 22 Mar 2006 17:44:59 +0200
Received: (from root@localhost)
by localhost.localdomain (8.13.4/8.13.4/Submit) id k2MFixTJ007187;
Wed, 22 Mar 2006 17:44:59 +0200
Date: Wed, 22 Mar 2006 17:44:59 +0200
From: root <root@xxxxxxxxxxxxxxxxxxxxx>
Message-Id: <200603221544.k2MFixTJ007187@xxxxxxxxxxxxxxxxxxxxx>
To: root@xxxxxxxxxxxxxxxxxxxxx
Subject: ALERT LVS1/ftp: 192.168.82.20 (Wed Mar 22 17:44:59)
X-Mailer: /usr/lib/mon/alert.d/mail.alert
Summary output : 192.168.82.20
Group : LVS1
Service : ftp
Time noticed : Wed Mar 22 17:44:59 2006
Secs until next alert :
Members : 192.168.82.20
Detailed text (if any) follows:
-------------------------------
HOST 192.168.82.20: connect: No route to host
From root@xxxxxxxxxxxxxxxxxxxxx Wed Mar 22 17:45:39 2006
Return-Path: <root@xxxxxxxxxxxxxxxxxxxxx>
Received: from localhost.localdomain (Fedora [127.0.0.1])
by localhost.localdomain (8.13.4/8.13.4) with ESMTP id k2MFjdtC007224
for <root@xxxxxxxxxxxxxxxxxxxxx>; Wed, 22 Mar 2006 17:45:39 +0200
Received: (from root@localhost)
by localhost.localdomain (8.13.4/8.13.4/Submit) id k2MFjdx1007223;
Wed, 22 Mar 2006 17:45:39 +0200
Date: Wed, 22 Mar 2006 17:45:39 +0200
From: root <root@xxxxxxxxxxxxxxxxxxxxx>
Message-Id: <200603221545.k2MFjdx1007223@xxxxxxxxxxxxxxxxxxxxx>
To: root@xxxxxxxxxxxxxxxxxxxxx
Subject: UPALERT LVS1/ftp: 192.168.82.20 (Wed Mar 22 17:45:39)
X-Mailer: /usr/lib/mon/alert.d/mail.alert
Summary output : 192.168.82.20
Group : LVS1
Service : ftp
Time noticed : Wed Mar 22 17:45:39 2006
Secs until next alert :
Members : 192.168.82.20
Detailed text (if any) follows:
-------------------------------
HOST 192.168.82.20: connect: No route to host
Any ideas? I am out of them :)
Thanks, Dan
---------------------------------
Yahoo! Mail
Use Photomail to share photos without annoying attachments.
|
