Re: [pmacct-discussion] sql_dont_try_update causes key collisions?

nds) it took to write all to the backend. PID, intuitively > and only for completeness, is the Process ID of the writer process. > > Paolo > > On Sun, Mar 05, 2017 at 01:55:54PM -0600, Edward Henigin wrote: > > I should have said that I know why Sqlite3 generates the error,

Re: [pmacct-discussion] sql_dont_try_update causes key collisions?

matching record or add > another non unique record. > > > > I think you'll need to add a unique field (such as an auto incrementing > ID field) then include that in the primary key contstraint in the DB. > > > > > > Tristan > > > > On 3 Mar 2

[pmacct-discussion] sql_dont_try_update causes key collisions?

Hi Paolo, When enabling sql_dont_try_update: true, I get these errors fairly continuously: Mar 3 11:33:30 server nfacctd[10661]: ERROR ( ip_dst/sqlite3 ): columns peer_ip_src, iface_in, ip_dst, stamp_inserted are not unique#012 Mar 3 11:33:33 server nfacctd[10662]: ERROR ( ip_dst/sqlite3 ): col

Re: [pmacct-discussion] nfacctd - log missed sequence numbers?

seqno'. This > way you can perform a more contextual analysis over periods of time (ie. > 1 min). > > Cheers, > Paolo > > On Thu, Feb 23, 2017 at 11:09:19AM -0600, Edward Henigin wrote: > > I see in the config keys for nfacctd that by default it checks sequence >

Re: [pmacct-discussion] nfacctd - log missed sequence numbers?

Paolo, can you help with this one please? On Thu, Feb 23, 2017 at 11:09 AM, Edward Henigin wrote: > I see in the config keys for nfacctd that by default it checks sequence > numbers and will log an error if any are missing. > > [ nfacctd_disable_checks | sfacctd_disable_chec

[pmacct-discussion] nfacctd - log missed sequence numbers?

I see in the config keys for nfacctd that by default it checks sequence numbers and will log an error if any are missing. [ nfacctd_disable_checks | sfacctd_disable_checks ] [GLOBAL, NO_PMACCTD] Values [true|false] Desc both nfacctd and sfacctd check health of incoming NetFlow/sFlow datagrams -

[pmacct-discussion] SQLite3 - issues, advice?

I guess the big question is, is SQLite3 really appropriate to use in a "light weight" but general purpose way? Is it fast enough for real-world use? Are there bugs or limitations that prevent it from really working well? My particular issues with it, given this configuration: DROP TABLE host_src

Re: [pmacct-discussion] pmacct 1.5.2 released !

int? Especially if using malloc()ed structures, ie. derived > by BGP primitives, this could be a valid scenario. Finally, can you > share your config? > > Cheers, > Paolo > > On Thu, Jan 07, 2016 at 04:04:09PM -0600, Edward Henigin wrote: > > Hi Paolo, > > > > I&

Re: [pmacct-discussion] pmacct 1.5.2 released !

Hi Paolo, I'm seeing a significant memory leak in the print plugin in 1.5.2. # service nfacctd restart Shutting down sflow collection services (nfacctd): [ OK ] Starting sflow collection services (nfacctd): INFO ( default/core ): Daemonizing. Hmm, bye bye screen.

Re: [pmacct-discussion] multiple nfacctd files being written

be more or >> less far in the past. >> >> Regards, >> Mario >> >> From: pmacct-discussion [mailto:pmacct-discussion-boun...@pmacct.net] On >> Behalf Of Edward Henigin >> Sent: Wednesday, October 21, 2015 10:34 PM >> To: pmacct-discuss. >> Subject:

Re: [pmacct-discussion] multiple nfacctd files being written

2015 1526: Wed Oct 21 15:28:10 2015 1527: Wed Oct 21 15:28:10 2015 Seems related? On Wed, Oct 21, 2015 at 3:28 PM, Edward Henigin wrote: > Hi Paolo, > > Running pmacct 1.5.2, simply using the print plugin, I'm getting multiple > files coming out at the same time with file

[pmacct-discussion] multiple nfacctd files being written

Hi Paolo, Running pmacct 1.5.2, simply using the print plugin, I'm getting multiple files coming out at the same time with filenames suggesting they should be coming out at different times, and sometimes very strange filenames like the data is very old. ls output: (root) packet1:/opt/pmacct/data

Re: [pmacct-discussion] Pro-rating netflow accounting data across time intervals

soon in touch with you privately > about this - does it sound like a good way forward? If anybody else is > interested into this and would like to give it a try, just let me know. > > Cheers, > Paolo > > On Fri, Aug 30, 2013 at 11:26:08AM -0500, Edward Henigin wrote: > >

[pmacct-discussion] Pro-rating netflow accounting data across time intervals

Hello Paolo, I'm currently using nfacctd to capture netflow accounting, for the purpose of identifying unexpected high traffic flows. (I happen to be using the print plugin, and parsing the text files to generate web reports, etc.) The netflow exporter in this case is a Cisco RSP720. One thing I

Re: [pmacct-discussion] Tips on dealing with overflowing 32-bit fields?

-Brent > > ** ** > > *From:* pmacct-discussion [mailto:pmacct-discussion-boun...@pmacct.net] *On > Behalf Of *Edward Henigin > *Sent:* Friday, May 24, 2013 1:40 PM > *To:* pmacct-discussion@pmacct.net > *Subject:* [pmacct-discussion] Tips on dealing with overflowing 32-b

[pmacct-discussion] Tips on dealing with overflowing 32-bit fields?

Hi y'all, I'm hoping that someone has some experience that might help. I'm using nfacctd to collect flows from a Cisco RSP720. After banging my head against the keyboard for a few days, I realized I should have configured pmacct with --enable-64bit. After re-building with that, accuracy is dramat