New install connection summary

New install config'd with --prefix=/opt/bro...first summary I received this:

Traceback (most recent call last):
   File "/opt/bro/bin/trace-summary", line 19, in <module>
     import SubnetTree
   File "/opt/bro/lib/broctl/", line 28, in <module>
     _SubnetTree = swig_import_helper()
   File "/opt/bro/lib/broctl/", line 24, in swig_import_helper
     _mod = imp.load_module('_SubnetTree', fp, pathname, description)
ImportError: dynamic module does not define init function (init_SubnetTree) Command exited with non-zero status 1
0:00.17 real, 0.03 user, 0.01 sys, 0K total memory

Clearly I'm missing something, but not sure what at this stage...any hints on this? Thank you.


Any takers on this? I got about 3.5 hours before the box in UTC time gets to run the summary again. Thank you.


What distribution is this and what version(s) of python are installed?

Thanks Justin. Here's the info:

Ubuntu 16.04.1 LTS 64 bit

[20:45:36 ~/current$] python2 --version
Python 2.7.12

[20:45:39 ~/current$] python3 --version
Python 3.5.2

Everything else is working great...I have a test machine at home, granted with beta's and git's, with the same OS and python versions with no issues. It's just this one thing..crazytown!


Ah.. that's great (that you have a similar working machine)

Does 'python' default to the same version on both machines?

Can you compare your installed packages? I wonder if you have python-dev on one machine and python3-dev on the other, or a different version of swig.

Yep...they both have pretty much the same one is standalone, the other using pfring with workers and all that jazz. It's kind of weird. Like I said...everything else works great. Is there a debug mode I can run? Thank you.

Not really.. one thing that might help would be to run

ldd /opt/bro/lib/broctl/

on both machines and see if they are different in any way.

Interesting...working box: => (0x00007ffe783fc000) => /usr/lib/x86_64-linux-gnu/ (0x00007f49e0ab6000) => /lib/x86_64-linux-gnu/ (0x00007f49e0899000) => /usr/lib/x86_64-linux-gnu/ (0x00007f49e0516000) => /lib/x86_64-linux-gnu/ (0x00007f49e0300000) => /lib/x86_64-linux-gnu/ (0x00007f49dff37000) => /lib/x86_64-linux-gnu/ (0x00007f49dfd1c000) => /lib/x86_64-linux-gnu/ (0x00007f49dfb18000) => /lib/x86_64-linux-gnu/ (0x00007f49df915000) => /lib/x86_64-linux-gnu/ (0x00007f49df60b000)
         /lib64/ (0x000055f3a7b25000)

Non-working: => (0x00007ffe6289b000) => /usr/lib/x86_64-linux-gnu/ (0x00007f6a55e28000) => /lib/x86_64-linux-gnu/ (0x00007f6a55c0b000) => /usr/lib/x86_64-linux-gnu/ (0x00007f6a55888000) => /lib/x86_64-linux-gnu/ (0x00007f6a55672000) => /lib/x86_64-linux-gnu/ (0x00007f6a552a9000) => /lib/x86_64-linux-gnu/ (0x00007f6a5507f000) => /lib/x86_64-linux-gnu/ (0x00007f6a54e65000) => /lib/x86_64-linux-gnu/ (0x00007f6a54c61000) => /lib/x86_64-linux-gnu/ (0x00007f6a54a5d000) => /lib/x86_64-linux-gnu/ (0x00007f6a54754000)
         /lib64/ (0x000055d9ea7fa000)

no workie with python3 perhaps?


It won't work if you build bro with Python 3 and then run
trace-summary with Python 2. Have you tried the beta2 that
was released today?

Thanks Daniel,

The issue was I had python3 dev install, but not python2. So bro compiled with 3, but ran with 2…makes sense why it didn’t work. I’m currently testing the beta and git elsewhere…looking forward to the new release…thank you.