[dev] Bgpd 5.0.1 gets killed by watchdog timeout

Donald Sharp sharpd at cumulusnetworks.com
Thu Sep 20 13:04:02 EDT 2018


the tools/frr script parses the /etc/frr/daemons file and generates
the list of daemons to pass to watchfrr at invocation time.
watchfrr.c is receiving this list, and in your case a list of (bgpd),
and noticing that zebra is not on that list and it is exiting from the
it's execution.  Since stderr is not properly being handled by
systemd?( not sure what is going on here yet ) we missed the log
message indicating what has gone wrong.  I just submitted a PR
https://github.com/FRRouting/frr/pull/3063 that allows us to capture
these messages in a way that it will be obvious to the end user what
needs to be done.

On Thu, Sep 20, 2018 at 11:03 AM, François <francois.serman at corp.ovh.com> wrote:
> Hi Donald,
>
> first, thank you for the heads up!
>
> On Wed, Sep 19, 2018 at 02:10:12PM -0400, Donald Sharp wrote:
>> So this appears to be a basic assumption in watchfrr.c that zebra is
>> being started.
>
> Great spot! I feel stupid, but I didn't figure it out.
>
>> Since it looks like you are going to run BGP as a
>> Route Reflector, I would recommend adding `zebra=yes` to your
>> `/etc/frr/daemons` file and making sure you create your bgp instance
>> as a view to avoid passing data to zebra.
>
> Well it's not exactly a RR, but at some point zebra could/should be turned on.
> I'm not familiar with the view thing, but I get the idea. I'll dig into that.
>
>
>> In the meantime we need to have a bit of a discussion about
>> whether or not this makes sense to continue having
>> watchfrr.c assume that zebra must be running.
>
>
> Well, would that be stupid to parse the daemons file, and only check those who
> have a "yes" value?
> If so, I would like to dig into it.
>
> Thanks again!
>
> --
> François
>
> _______________________________________________
> dev mailing list
> dev at lists.frrouting.org
> https://lists.frrouting.org/listinfo/dev



More information about the dev mailing list