|
I have a working mon configuration up to the point of working mail alert for
fping and telnet monitor. Now I am trying to get virtualserver.alert to send
commands to LVS and something is wrong. I've set up a one-node telnet
realserver at 192.168.1.243 which is working correctly. My VIP is
192.168.1.110.
I then issue the commands:
ipvsadm -C
ipvsadm -A -t 192.168.1.110:23 -s rr
and then run /var/lib/mon/alert.d/virtualserver.alert -u -a -t
192.168.1.110:23 -r 192.168.1.243 -g -w 1
which is what is says to do to test the alert but it fails with the output:
------------------virtualserver.alert output-----------------------------
command line params: -u -a -t 192.168.1.110:23 -r 192.168.1.243 -g -w 1
Unknown option: a
Unknown option: r
, , , 192.168.1.110:23, , , , , ,
, , , , ,
kernel_type: 2.4.18-lvs2
2.2.x or 2.4.x kernel on director
bring server up
/sbin/ipvsadm -r -w
Try `/sbin/ipvsadm -h' or '/sbin/ipvsadm --help' for more information.
------------------------------end output-------------------------------------
(I commented out the extra print lines in the script for debugging...)
If I run virtualserver.alert with no arguments I get:
-------------virtualserver.alert output--------------------------------------
command line params:
, , , , , , , , ,
, , , , ,
kernel_type: 2.4.18-lvs2
2.2.x or 2.4.x kernel on director
bring server down
/sbin/ipvsadm -r
/sbin/ipvsadm: option requires an argument -- r
Try `/sbin/ipvsadm -h' or '/sbin/ipvsadm --help' for more information.
------------------------end output-------------------------------------------
Not sure what is going on here but it is definitely failing to bring the
realserver node up or down.
--
Daniel O'Neill
Systems Engineer
djoneill@xxxxxxxxxxxxxxxxx
415.644.9600 ext. 238 tel.
415.644.0015 fax
|
