sorry, one more question, when preparing the aggregate, does the order of the values matter? right now my aggregate is like the following
aggregate: proto,src_host, dst_host, src_port, dst_port, src_as, dst_as, tcpflags,flows while the order is different in the db table, for example, protocol is not the first column in my table, it appears that pmacct "knows" if should put the proto under "proto" column, although i defined it as first value in the aggregate and defined it in the middle of the table. On Fri, Nov 13, 2009 at 4:58 PM, fedora fedora <fedoraf...@gmail.com> wrote: > Paolo, > > Thanks a lot, really appreciate your help here, it seems to work now. > > I actually read all the documents I could find and did not see this get > mentioned anywhere. I just double checked the Q16 part i printed out and did > not see anything talking about v6. > > One more question, how can i get pmacct to show the flow number in the > database? I got all "0" ,and when i change to aggregate to " > aggregate:proto,src_host, dst_host, src_port, dst_port, src_as, dst_as, > tcpflags,flows > " all the numbers are one same pretty big number" > > Also i will have to read what exactly does stamp_inserted , and > stamp_update mean.. > > > > On Fri, Nov 13, 2009 at 4:44 PM, Paolo Lucente <pa...@pmacct.net> wrote: > >> Hi, >> >> On Fri, Nov 13, 2009 at 04:21:26PM -0600, fedora fedora wrote: >> > Thanks for the reply, i disable the daemon option and here are the error >> > messages, i cannot put src_ip and src_as together? >> > >> > INFO ( default/mysql ): 131070 bytes are available to address shared >> memory >> > segment; buffer size is 128 bytes. >> > INFO ( default/mysql ): Trying to allocate a shared memory segment of >> > 2097024 bytes. >> > INFO ( default/core ): waiting for NetFlow data on 0.0.0.0:10000 >> > ERROR ( default/mysql ): SQL tables < v6 are unable to mix IP addresses >> and >> > AS numbers (ie. src_ip, src_as). >> > INFO: connection lost to 'default-mysql'; closing connection. >> >> Simply add to your config a 'sql_table_version: 6' line. Then, the >> 'sql_optimize_clauses' directive ensures you can customize your table. >> Q16 in the FAQS document explains the concept of SQL table versioning >> in pmacct. >> >> Cheers, >> Paolo >> >> >> >
_______________________________________________ pmacct-discussion mailing list http://www.pmacct.net/#mailinglists
