[Bro] New install connection summary

[James Lay]

On Thu, 2016-11-03 at 20:23 -0500, Daniel Thayer wrote:
> On 11/3/16 4:13 PM, James Lay wrote:
> > 
> > On 2016-11-03 15:08, Azoff, Justin S wrote:
> > > 
> > > > 
> > > > On Nov 3, 2016, at 5:03 PM, James Lay <jlay at slave-tothe-box.net
> > > > >
> > > > wrote:
> > > > 
> > > > Yep...they both have pretty much the same thing...safe 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/_SubnetTree.so
> > > 
> > > on both machines and see if they are different in any way.
> > 
> > Interesting...working box:
> >          linux-vdso.so.1 =>  (0x00007ffe783fc000)
> >          libpython2.7.so.1.0 =>
> > /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0 (0x00007f49e0ab6000)
> >          libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
> > (0x00007f49e0899000)
> >          libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6
> > (0x00007f49e0516000)
> >          libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1
> > (0x00007f49e0300000)
> >          libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6
> > (0x00007f49dff37000)
> >          libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1
> > (0x00007f49dfd1c000)
> >          libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2
> > (0x00007f49dfb18000)
> >          libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1
> > (0x00007f49df915000)
> >          libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6
> > (0x00007f49df60b000)
> >          /lib64/ld-linux-x86-64.so.2 (0x000055f3a7b25000)
> > 
> > Non-working:
> >          linux-vdso.so.1 =>  (0x00007ffe6289b000)
> >          libpython3.5m.so.1.0 =>
> > /usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0 (0x00007f6a55e28000)
> >          libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
> > (0x00007f6a55c0b000)
> >          libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6
> > (0x00007f6a55888000)
> >          libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1
> > (0x00007f6a55672000)
> >          libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6
> > (0x00007f6a552a9000)
> >          libexpat.so.1 => /lib/x86_64-linux-gnu/libexpat.so.1
> > (0x00007f6a5507f000)
> >          libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1
> > (0x00007f6a54e65000)
> >          libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2
> > (0x00007f6a54c61000)
> >          libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1
> > (0x00007f6a54a5d000)
> >          libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6
> > (0x00007f6a54754000)
> >          /lib64/ld-linux-x86-64.so.2 (0x000055d9ea7fa000)
> > 
> > no workie with python3 perhaps?
> > 
> > James
> 
> 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.
James
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/bro/attachments/20161104/0569e7b1/attachment-0001.html