flow-capture crashes after some time since run. Output from dmesg: # dmesg|grep flow-capture flow-capture[6980]: segfault at 000000000000000c rip 00000000004153c1 rsp 00007ffffffa9640 error 4 flow-capture[7398]: segfault at 000000000000000c rip 00000000004153c1 rsp 00007ffffffa93a0 error 4 flow-capture[31516]: segfault at 000000000000000c rip 00000000004153c1 rsp 00007ffffffa9370 error 4 flow-capture[6265]: segfault at 000000000000000c rip 00000000004153c1 rsp 00007ffffffa9390 error 4 flow-capture[19076]: segfault at 000000000000000c rip 00000000004153c1 rsp 00007ffffffa9350 error 4 flow-capture[5783]: segfault at 000000000000000c rip 00000000004153c1 rsp 00007ffffffa9360 error 4 Reproducible: Always Steps to Reproduce: 1. run flow-capture -w /home/flows/ -N3 -E10G 127.0.0.1/127.0.0.1/2055 2. wait ;-) Actual Results: after some time, flow-capture gets sig 11 and exits. Expected Results: Should work fine. # emerge info Portage 2.0.51.19 (default-linux/amd64/2004.3, gcc-3.4.3, glibc-2.3.4.20041102- r0, 2.6.11-gentoo-r4jd x86_64) ================================================================= System uname: 2.6.11-gentoo-r4jd x86_64 AMD Opteron(tm) Processor 244 Gentoo Base System version 1.6.10 Python: dev-lang/python-2.3.4-r1 [2.3.4 (#1, Mar 14 2005, 10:45:34)] dev-lang/python: 2.3.4-r1 sys-apps/sandbox: [Not Present] sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.5, 1.6.3, 1.4_p6, 1.9.4, 1.7.9-r1, 1.8.5-r3 sys-devel/binutils: 2.15.92.0.2-r1 sys-devel/libtool: 1.5.10-r4 virtual/os-headers: 2.6.8.1-r3 ACCEPT_KEYWORDS="amd64" AUTOCLEAN="yes" CFLAGS="-march=k8 -O2 -msse -m3dnow -msse2 -m64" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share /config /var/bind /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=k8 -O2 -msse -m3dnow -msse2 -m64" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sfperms strict userpriv" GENTOO_MIRRORS="http://gentoo.zie.pg.gda.pl http://src.gentoo.pl http://gentoo.inode.at/" MAKEOPTS="-j7" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="amd64 acpi berkdb bitmap-fonts crypt curl font-server fortran gd gdbm gif gpm ipv6 jp2 jpeg ldap libwww lzw lzw-tiff mp3 mysql ncurses nls opengl oss pam pdflib perl png python readline slang snmp ssl tcpd tiff truetype truetype- fonts type1-fonts usb userlocales xml2 xpm xrandr xv zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY
version of flow-tools? can you provide a backtrace? If not, can you tar up the data you're running flow-capture on and put it somewhere for download (or you can attach it here if it's not too big)? We'll need at least one of the above (both is better) in order to have any clue to the cause of the segfaults.
(In reply to comment #1) > version of flow-tools? # emerge -pv flow-tools (...) [ebuild R ] net-analyzer/flow-tools-0.66 0 kB > can you provide a backtrace? If not, can you tar up the > data you're running flow-capture on and put it somewhere > for download (or you can attach it here if it's not too > big)? > We'll need at least one of the above (both is better) in > order to have any clue to the cause of the segfaults. There is a little problem. Data I run on is locally generated by fprobe, /home/flows is (can be) an empty directory tree, where flow-capture stores flows. I can provide you some unfinished (broken by segfault) flow files, but it will be rather big one. How can I produce backtrace for you?
(In reply to comment #2) > (In reply to comment #1) > > version of flow-tools? > # emerge -pv flow-tools > (...) > [ebuild R ] net-analyzer/flow-tools-0.66 0 kB > Before we do anything else, try both of the newer versions of flow-tools that are in portage. Hopefully we'll get lucky and it'll be fixed. <snip> > > There is a little problem. Data I run on is locally generated by > fprobe, /home/flows is (can be) an empty directory tree, where flow-capture > stores flows. I can provide you some unfinished (broken by segfault) flow > files, but it will be rather big one. > How can I produce backtrace for you? If one of the newer versions doesn't have this fixed, then I'll give you instructions on producing a backtrace.
I've been trying 0.67, but when I tried to get anything from flows produced by 0.67, there was dummy output (for example neverending flood of identical flows). 0.68 seem to be "stable", but what is this? # ps auxww|grep capture root 18829 0.7 0.0 10200 1820 ? Ss 01:48 5:01 flow-capture - w /home/flows/ -N3 -E10G 127.0.0.1/127.0.0.1/2055 (so flow-capture shold create subdirectories tree like year/year-month/year- month-day/ and place there flow files (-N3)). Actually, results are: # find . . ./2277 ./2277/2277-07 ./2277/2277-07/2277-07-31 ./77200747 ./77200747/77200747-03 ./77200747/77200747-03/77200747-03-11 ./93827115 ./93827115/93827115-04 ./93827115/93827115-04/93827115-04-15 ./96897714 ./96897714/96897714-08 ./96897714/96897714-08/96897714-08-30 ./100403432 ./100403432/100403432-06 ./100403432/100403432-06/100403432-06-09 ./103478114 ./103478114/103478114-11 ./103478114/103478114-11/103478114-11-17 ./106498084 ./106498084/106498084-04 ./106498084/106498084-04/106498084-04-10 ./109426456 ./109426456/109426456-12 ./109426456/109426456-12/109426456-12-17 ./112260783 ./112260783/112260783-02 ./112260783/112260783-02/112260783-02-07 ./115154585 ./115154585/115154585-11 ./115154585/115154585-11/115154585-11-09 ./117986189 ./117986189/117986189-12 ./117986189/117986189-12/117986189-12-15 ./120757092 ./120757092/120757092-07 ./120757092/120757092-07/120757092-07-08 ./124614498 ./124614498/124614498-02 ./124614498/124614498-02/124614498-02-09 ./127519733 ./127519733/127519733-06 ./127519733/127519733-06/127519733-06-11 ./130553857 ./130553857/130553857-06 ./130553857/130553857-06/130553857-06-17 ./133338506 ./133338506/133338506-05 ./133338506/133338506-05/133338506-05-02 What is this? :)
Oh, i forgot, my current version is 0.68
Created attachment 62090 [details] flow-strace.log seems to start ok, at least...
I can't replicate this problem. Without the data to emulate this problem there is little else that can be done. Is this still a problem with 0.68-r1 ebuild?
Please test with 0.68-r1 and reopen if it's still a problem.
