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

2017-03-03 Thread Paolo Lucente
+1 on Tristan's feedback. Ed, you can check at this propo also: https://github.com/pmacct/pmacct/wiki/RDBMS:-Customising-the-SQL-database-indexes If commenting out sql_dont_try_update makes things work well then it means the setup is making use of UPDATE queries. Maybe you need a larger

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

2017-03-03 Thread Tristan Bendall
Hi Edward I think what is happening here, in database speak, is that the primary key for the new record isn't unique, and that's breaking DB rules. Basically the DB is trying to add a new record that already exists, and with update turned off, it can't either update the matching record or add

[pmacct-discussion] sql_dont_try_update causes key collisions?

2017-03-03 Thread Edward Henigin
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 ):