On Fri, Oct 18, 2019 at 12:55:02AM -0700, Sacha wrote: > Dear all, > > first of all sorry if this bug report is not complete, the issue is on our > production firewalls and each test cut all our AS network, we have to be in > the datacenter to go further.
This is not good. > We have 2 firewalls on master/slave Carp failover, with BGPD and OSPF. > After upgrading on 6.6, we have an issue when we reboot one of our two > firewalls, it make the other crash the BGPD daemon (our AS is no more > announced). > This occurs even on master and slave firewall, when we reboot one the other > looses it's bgp. > What we know so far is if we stop ospf & ospf6 daemons before the reboot, > there is no more issue. > I'm going to the datacenter this afternoon, I will try to reproduce with > more logs. > All ideas for debugging are welcome. > Check /var/log/daemon what did bgpd log before going down? I would be interested to see the bgpd related syslog output. You can increase logging with bgpctl log verbose or just run bgpd in debug more (bgpd -dvv). If one of the process crashes (normally by a SIGSEGV or similar signal) then set the sysctl kern.nosuidcoredump=3 and create a directory called /var/crash/bgpd. Also make sure your limit for the coredumpsize is high enough. This should allow you to get a coredump of the crashing process. Once you have a core it should be possible to get a backtrace. -- :wq Claudio
