2014-04-10 11:35 GMT+04:00 Alexander V. Chernikov <melif...@freebsd.org>:
> On 10.04.2014 10:14, Peter Andreev wrote: > > Hi Alexander, > > > > I tried "debug MLPA1 all" from birdc console, but nothing new appeared > > in log file. > Interesting. > > > > Currently I rolled back to 1.3.10 version from ports because 1.4.2 > > started to crash with the following backtrace: > > > > > > GNU gdb 6.1.1 [FreeBSD] > > Copyright 2004 Free Software Foundation, Inc. > > GDB is free software, covered by the GNU General Public License, and you > are > > welcome to change it and/or distribute copies of it under certain > > conditions. > > Type "show copying" to see the conditions. > > There is absolutely no warranty for GDB. Type "show warranty" for > details. > > This GDB was configured as "amd64-marcel-freebsd"... > > Core was generated by `bird6'. > > Program terminated with signal 11, Segmentation fault. > > Reading symbols from /lib/libthr.so.3...done. > > Loaded symbols for /lib/libthr.so.3 > > Reading symbols from /lib/libc.so.7...done. > > Loaded symbols for /lib/libc.so.7 > > Reading symbols from /libexec/ld-elf.so.1...done. > > Loaded symbols for /libexec/ld-elf.so.1 > > #0 0x0000000000464a9e in add_tail (l=0x801017798, n=0x80102a650) at > > lists.c:46 > > 46 z->next = n; > > [New Thread 801007400 (LWP 100292/bird6)] > > (gdb) bt > > #0 0x0000000000464a9e in add_tail (l=0x801017798, n=0x80102a650) at > > lists.c:46 > > #1 0x0000000000469ce6 in ralloc (p=0x801017780, c=0x692260) at > > resource.c:224 > > #2 0x000000000045c20a in tm_new (p=0x801017780) at io.c:226 > > #3 0x0000000000425bef in bgp_setup_conn (p=0x801008020, > > conn=0x8010081c8) at ../../../proto/bgp/bgp.c:631 > > #4 0x0000000000425d97 in bgp_active (p=0x801008020) at > > ../../../proto/bgp/bgp.c:660 > > #5 0x00000000004252cb in bgp_decision (vp=0x801008020) at > > ../../../proto/bgp/bgp.c:334 > > #6 0x000000000045bd67 in ev_run (e=0x801017800) at event.c:85 > > #7 0x000000000045be02 in ev_run_list (l=0x694aa0) at event.c:135 > > #8 0x000000000045f05f in io_loop () at io.c:1716 > > #9 0x00000000004669b3 in main (argc=3, argv=0x7fffffffdb20) at > main.c:820 > > (gdb) quit > > > > > > If this crash is interesting to you as port maintainer, I will provide > > any additional information which can help to understand why it happened. > Yes, definitely. > > Can you provide me with config, core file and a binary? > Ok. I'll send in private message. > Is this stock bird from 1.4.2, default options, no patches? > Stock bird, default options. > Do you using gcc or clang to build and which version? > /home/apn>cc -v Using built-in specs. Target: amd64-undermydesk-freebsd Configured with: FreeBSD/amd64 system compiler Thread model: posix gcc version 4.2.1 20070831 patched [FreeBSD] > > How can one reproduce this scenario? > My rc.conf: vlans_em2="10 20" ifconfig_em2_10="<some_ip>" ifconfig_em2_20_ipv6="<some_v6_ip>" ifconfig_em2="up" > Does the same config work on 1.3.10? > 1.3.10 doesn't crash, but BGP sessions don't set up. > > > > > 2014-04-09 23:10 GMT+04:00 Alexander V. Chernikov <melif...@freebsd.org > > <mailto:melif...@freebsd.org>>: > > > > On 09.04.2014 13:36, Peter Andreev wrote: > > > Hi everybody, > > > > Hello! > > > > > > I'm trying to set up bird 1.4.2 on FreeBSD 9.1 and stuck on the > > > following: > > > > > > bird> sh pro name proto table state since info > > > kernel1 Kernel master up 13:10:06 device1 Device master > > > up 13:10:06 NICbr1 BGP master up 13:10:28 > > > Established NICbr2 BGP master up 13:10:29 > > > Established PTTlg BGP master start 13:10:24 Connect > > > Socket: Invalid argument MLPA1 BGP master start 13:10:24 > > > Connect Socket: Operation timed out MLPA2 BGP master > > > start 13:10:24 Connect Socket: Invalid argument MLPA3 > > > BGP master start 13:12:51 OpenConfirm BGP Error: Hold > > > timer expired MLPA4 BGP master start 13:10:24 Connect > > > Socket: Invalid argument STATIC_BGP Static master up > > > 13:10:06 > > > > > > All these BGP protocols are inherited from one template. The only > > > difference is that those are established, use another source > > > address which is configured on virtual interface. > > > > > > However my question is how to find out what's going on and how to > > > detect a problem? Setting "log syslog all;" is not very helpful - > > > it only fills the log file with a lot of "bird6: KRT: Error sending > > > route 2c0f:fb50::/0 to kernel: No such process" messages. > > You can look at detailed protocol status via > > "show protocol [nam] all" > > You can enable appropriated level of per-protocol debug (e.g. add > > "debug { events, states };" to protocol config. > > > > > > > > -- Is there any problem Exterminatus cannot solve? I have not found > > > one yet. > > > > > > > > > > > > > -- > > Is there any problem Exterminatus cannot solve? I have not found one yet. > > > > -- Is there any problem Exterminatus cannot solve? I have not found one yet.