Hi Johannes, On Mon, 13 Apr 2009, Johannes Formann wrote:
>>>> I'm not sure why "flows" is in your aggregate set since flows are >>>> already aggregated into flows in all cases by pmacctd, as far as I >>>> know (please correct me if I'm wrong). >>> >>> flow isn't in the primary key. >> >> I didn't say it was, but it is in your aggregate set and I don't >> understand why. > > Are you shure its flow, between mac and IP it could be vlan? aggregate: src_host,dst_host,dst_port,src_port,flows,dst_mac,proto,src_mac,vlan It's right there before dst_mac. >> I guess you mean the SIGSEGV error has been logged in your syslog? gdb >> should stop when it sees the SIGSEGV error, and wait for a command such >> as "bt". So I guess it's happening in another thread than the main one, >> so it will be harder to trace. >> >> You could wait until pmacctd is up and running, then press Ctrl+C, >> enter the "info threads" command, then guess a thread other than the >> first one and switch to it with "thread xxx" and "continue", and hope >> that that thread dies with SIGSEGV. > > Is pmacctd not terminated once pressing ctrl+c? It shouldn't be, gdb should intercept the SIGINT and stop it from reaching the process. Cheers, Chris. -- Aptivate | http://www.aptivate.org | Phone: +44 1223 760887 The Humanitarian Centre, Fenner's, Gresham Road, Cambridge CB1 2ES Aptivate is a not-for-profit company registered in England and Wales with company number 04980791. _______________________________________________ pmacct-discussion mailing list http://www.pmacct.net/#mailinglists
