Subject: Re: Arguslist Digest, Vol 57, Issue 4

From: Andy <[email-masked]>
Date: Thu, 18 Dec 2008 11:51:36 +0000

2008/12/15 <[email-masked]>

> Send Arguslist mailing list submissions to
>        [email-masked]
>
> To subscribe or unsubscribe via the World Wide Web, visit
>        http://www.tcp4me.com/mailman/listinfo/arguslist
> or, via email, send a message with subject or body 'help' to
>        [email-masked]
>
> You can reach the person managing the list at
>        [email-masked]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Arguslist digest..."
>
>
> Today's Topics:
>
>   1. DARP Problems? (Andy)
>   2. Re: DARP Problems? (Jeff Weisberg)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 15 Dec 2008 10:43:58 +0000
> From: Andy <[email-masked]>
> Subject: DARP Problems?
> To: [email-masked]
> Message-ID:
>        <[email-masked]>
> Content-Type: text/plain; charset=ISO-8859-1
>
> I'm just trying to test DARP mode in a very simple setup, and I am getting
> the following error in the logs
>
>
>
> "master machine error"  WARNING: in file '/var/argus/config' on line 15 -
> additional data not permitted here (ignored)
>
> "slave machine error" WARNING: in file '/var/argus/config' on line 13 -
> additional data not permitted here (ignored)
>
>
> No firewall between the two machines, no iptables rules either, configs
> included below just in case I'm missing something blindingly obvious?
>
> Is DARP mode still only available when you purchase support?
>
>
>
> Master config
>
> icon:           /arguscss/smile.gif
> icon_down:      /arguscss/sadred.gif
> style_sheet:    /arguscss/argus.css
> javascript:     /arguscss/argus.js
>
>
>
> Method "isg_mail" {
>        command:        sendmail -t
>        send: From: [email-masked]\nTo: [email-masked] \nSubject:
> Argus %O %S\n \n%M %T %C \n\n\n
>        }
>
>
>
> darp_mode: failover
>
> DARP "master1" {
>
>        slave "slave1" {
>                hostname: 192.168.3.56
>                secret: testing
>        }
> }
>
>
>
> Group "Darp Slaves" {
>        Service DARP/WATCH/slave1
> }
>
>
>
>  Group "Argus" {
>        graph: yes
>        Service Self/idle {
>            title:  Percent Idle
>            calc:   ave-rate
>            scale:  0.01
>            # let someone know when it is time to upgrade h/w
>            minvalue:  20
>            messagedn: time to buy faster server
>        }
>
>        Service Self/tested {
>            title:  Monitoring Rate
>            ylabel: tests per second
>            calc:   ave-rate
>        }
>
>        Service Prog {
>            # how much memory is argus using?
>            # your ps may be different
>            command:        ps -p $ARGUS_PID -o vsz | tail -1
>            uname:          VSZ
>            title:          Memory Use
>            ylabel:         kBytes
>        }
>   }
>
>
>
>
> Group   "Special Monitor" {
>        notify: isg_mail:
>        renotify:       1200
>        overridable:    yes
>        messagedn:      %i %r %s %t %o
>        Include "/var/argus/special"
> }
>
> output of argusctl status on master
>
>
> ARGUS/2.0 200 OK
> status:    running
> version:   3.5
> perlver:   118.53.46.49.48.46.48
> osinfo:    Linux 2.6.25.16-0.1-pae i686
> darpmode:  master
> objects:   56
> services:  28
> notifies:  2
> uptime:    0:01:42
> idle:      99.21%
> monrate:   0.44 tests per second
>
>
> Slave config
>
> icon:           /arguscss/smile.gif
> icon_down:      /arguscss/sadred.gif
> style_sheet:    /arguscss/argus.css
> javascript:     /arguscss/argus.js
>
>
> Method "isg_mail" {
>        command:        sendmail -t
>        send: From: [email-masked]\nTo: [email-masked] \nSubject:
> Argus %O %S\n \n%M %T %C \n\n\n
>        }
>
>
> darp_mode:      failover
>
> DARP "slave1" {
>
>        master "master1" {
>                hostname:       192.168.3.50
>                secret:         testing
>        }
> }
>
>
>
> output of argusctl status on slave
>
>
> ARGUS/2.0 200 OK
> status:    running
> version:   3.5
> perlver:   118.53.46.49.48.46.48
> osinfo:    Linux 2.6.25.18-0.2-pae i686
> darpmode:  slave
> objects:   2
> services:  1
> notifies:  0
> uptime:    0:02:10
> idle:      99.90%
> monrate:   0.01 tests per second
>
>
> ------------------------------
>
> Message: 2
> Date: Mon, 15 Dec 2008 10:54:12 -0500
> From: Jeff Weisberg <[email-masked] <[email-masked]>
> >
> Subject: Re: DARP Problems?
> To: Discussion about Argus <[email-masked]>
> Message-ID: <[email-masked]>
> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
>
>
> On 15 Dec, 2008, at 5:43, Andy wrote:
>
> > I'm just trying to test DARP mode in a very simple setup, and I am
> > getting
> > the following error in the logs
> >
> > "master machine error"  WARNING: in file '/var/argus/config' on line
> > 15 -
> > additional data not permitted here (ignored)
>
>
>
> > Method "isg_mail" {
> >        command:        sendmail -t
> >        send: From: [email-masked]\nTo: [email-masked]
> > \nSubject:
> > Argus %O %S\n \n%M %T %C \n\n\n
> >        }
> >
> >
> > darp_mode: failover
>
>
> this line needs to be moved above the Method block.
> otherwise, it will be ignored and you will get a warning.
>
>
>
> > output of argusctl status on master
> >
> >
> > ARGUS/2.0 200 OK
> > darpmode:  master
>
> this means that darp is working.
> for more details, you can:
>
> % argusctl darp_status
>
> ARGUS/2.0 200 OK
> master0:        DARP:up
> slave1:         Slave:up
>
>
>
Thanks Jeff :)

Just a quick gotcha for anyone upgrading a old Argus installation and then
using DARP.

You can specify hosts that only need to be tested by ping in the following
manner, in a non DARP install

Host "test router" {
        hostname: 192.168.2.1
        note:   testing stuff
        Service Ping
}

And it will quite happily test the host. However when running in DARP mode
the slave only appears to get the config in the following manner

Host "test router" {
        note:   testing stuff
        Service Ping
}

And will try and resolve the name of the device from the Host string, which
is fine if you are using resolvable names, how ever if you are not using
resolvable names in the Host field;

Host "test router" {
         note: testing stuff
         Service Ping {
                    hostname: 192.168.2.1
         }
}

Will transfer completely from the master to the slave without any problems.

nb this is using Argus 3.5 you milage may differ if using 3.6