If you are interested below is my upstart conf (bird.conf)
I am running Ubuntu so I removed the bird init.d script and added this in
/etc/init/
<SNIP>
description "BIRD Router Daemon"
start on runlevel [2345]
stop on runlevel [!2345]
# An Upstart script to manage the foo service
respawn
expect fork
script
. /etc/default/bird
exec /usr/sbin/bird $DAEMON_ARGS
end script
post-start script
sleep 5
echo "my-foo service started at `date +"%F %T.%N"`" | mail -s "My-foo
Service Started" [email protected]
chown root.nagios /var/run/bird.ctl
end script
</SNIP>
This appears to work rather well. That said I am sure there is a much better
way of doing it… :)
Joe
On 23/04/2013, at 12:42 PM, Bao Nguyen <[email protected]> wrote:
> @Joe, thanks for starting this thread, I was just thinking along this line of
> making sure bird is running.
>
> Apollon, I would love to give your plugin a try.
>
> To summarize, I'm deploying Bird on 120 machines (2 nic each) + 6 routers
> (total of 240 ptp links in a clos configuration) and participate in a single
> area OSPF. Anyone know whether bird have been being deploy/tested in this use
> case?
>
>
> thanks,
>
> -bn
> 0216331C
>
>
> On Mon, Apr 22, 2013 at 4:35 AM, Apollon Oikonomopoulos <[email protected]>
> wrote:
> On 19:20 Mon 22 Apr , Joe Wooller wrote:
> > On a similar note, does anyone monitor the process externally, (say via
> > nagios or the like?)
> > I would be interested to see how people monitor the active process,
> > and possibly if anyone monitors sessions and prefixes received,
> > used/filtered?
> >
> > I haven't been able to find any thing out there that suits my needs, so
> > with the assistance of a friend we have come up with this, still in
> > progress though..
> >
> > https://github.com/dowlingw/bird-tool
> >
> > Cheers
> > Joe
>
> We are monitoring the process with icinga & check_mk. Check_mk has a
> notion of state, so we essentially persist ("inventorize") the admin
> state of all protocols (up/down) and their status (Connected, Running
> etc) and if anything changes we get an alert.
>
> I could share the check_mk plugin that does all this, if anyone is
> interested.
>
> We also monitor the prefix count directly in the Linux kernel (via
> /proc/net/fib_triestat and /proc/net/rt6_stats) and use it to score our
> keepalived processes higher or lower and possibly trigger a failover of
> the access interface IPs if one router seems to receive significantly
> less prefixes than the other for some reason.
>
> Cheers,
> Apollon
>
> !DSPAM:1,5176115080744122215783!
