Hi Olivier, Sorry for the late reply but I was busy these days. I went into several issues when disabling the sessions: --- router.bsdrp.net(config-router)# neighbor x.x.x.1 shutdown router.bsdrp.net(config-router)# neighbor x.x.x.2 shutdown router.bsdrp.net(config-router)# neighbor x.x.x.3 shutdown router.bsdrp.net(config-router)# neighbor x.x.x.4 shutdown router.bsdrp.net(config-router)# neighbor x.x.x.5 shutdown router.bsdrp.net(config-router)# router.bsdrp.net(config-router)# router.bsdrp.net(config-router)# ^ZWarning: closing connection to zebra because of an I/O error! Warning: connecting to zebra...failed!
user@router/#service frr status zebra is not running. ospfd is running as pid 1586. ospf6d is running as pid 3340. bgpd is running as pid 6100. --- Here are the logs (please disregard the date and time). - from /var/log/messages: --- Aug 16 18:07:25 router kernel: pid 44117 (zebra), jid 0, uid 168: exited on signal 6 --- - from /var/log/bgpd.log --- 2008/08/16 18:07:25 ZEBRA: Kernel: message seq 1632715 2008/08/16 18:07:25 ZEBRA: Kernel: pid 44117, rtm_addrs 0x7 2008/08/16 18:07:25 ZEBRA: rtm_read: got rtm of type 2 (RTM_DELETE) 2008/08/16 18:07:25 ZEBRA: Kernel: Len: 200 Type: RTM_DELETE 2008/08/16 18:07:25 ZEBRA: Kernel: GATEWAY DONE PROTO1 2008/08/16 18:07:25 ZEBRA: Kernel: message seq 1634039 2008/08/16 18:07:25 ZEBRA: Kernel: pid 44117, rtm_addrs 0x7 2008/08/16 18:07:25 ZEBRA: rtm_read: got rtm of type 2 (RTM_DELETE) 2008/08/16 18:07:25 BGP: buffer_write: write error on fd 10: Broken pipe 2008/08/16 18:07:25 BGP: zclient_send_message: buffer_write failed to zclient fd 10, closing --- I decided to change the date and check again and then I went into something else. After enabling the sessions and checking for neighbor statistics I decided to clear one of the sessions that was not starting: --- router.bsdrp.net# clear ip bgp x.xSegmentation fault user has logged on pts/0 from y.y.y.y --- I used the "tab" key to complete the ip address in the above command. In /var/log/messages I get: --- Apr 9 10:49:56 router kernel: pid 14177 (zebra), jid 0, uid 168: exited on signal 6 Apr 9 10:50:35 router kernel: pid 54325 (vtysh), jid 0, uid 0: exited on signal 11 --- This time there is nothing in /var/log/bgpd.log. --- user@router/# service frr statusservice frr status zebra is not running. ospfd is running as pid 1586. ospf6d is running as pid 3340. bgpd is running as pid 6100. --- It could be a coincidence that vtysh has failed together with zebrad (could be that the session has established at the moment I have pressed the 'tab' key). I will try once again but this time will enabled some more debuging: --- router.bsdrp.net# show debugging Zebra debugging status: Zebra event debugging is on Zebra packet debugging is on Zebra kernel debugging is on Zebra RIB debugging is on OSPF debugging status: OSPF6 debugging status: BGP debugging status: BGP zebra debugging is on --- I will write hopefully tomorrow. Regards, Lyubo On Mon, 8 Apr 2019 at 20:39, Lyubomir Yotov <l.yo...@gmail.com> wrote: > Hi Olivier, > I just couldn't think of anything else (except changing frr with bird). > You are absolutely right about the panic (as well as for the zebra daemon > crash). This should not happen, regardles the wrong configuration. > The system is still working as expected (no traffic going in or out, as it > is a test system, but zebrad has not crashed so far). Tomorrow I will check > again with the original image and report back > . > Regards, > > Lyubomir > > On Mon, 8 Apr 2019 at 17:52, Olivier Cochard-Labbé <oliv...@cochard.me> > wrote: > >> On Mon, Apr 8, 2019 at 3:37 PM Lyubomir Yotov <l.yo...@gmail.com> wrote: >> >>> I actually found an error in the AS number (last digit was missing). >>> So far (more than an hour) it seems fine. As it has happened before that >>> it could crash after several hours I will wait until tomorrow. >>> If everything is fine I will try again with a fresh install (on another >>> flash drive) to check if the wrong config was the problem. >>> Just for the record here is the "show version" from the installed frr6: >>> router.bsdrp.net#show version >>> FRRouting 6.0.2 (router.bsdrp.net). >>> >>> >> Hi, >> Like you've seen, the binary version is stil 6.0.2, because the port >> revision "2" didn't modified the binary: >> - frr6.0.2_1 : It was just an update of an RC script, so no change into >> FRR binaries >> - frr6.0.2_2 : It was just a typo in RC script's comment >> So I don't think the resolution came from this upgrade. >> >> But in any case, even if the panic came from the wrong AS number: it >> should have not triggered a panic. >> >> Regards, >> >> Olivier >> _______________________________________________ >> Bsdrp-users mailing list >> Bsdrp-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/bsdrp-users >> >
_______________________________________________ Bsdrp-users mailing list Bsdrp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bsdrp-users
