Hi Raphael, Can you dig what entry is precisely causing this? I've seen that happening especially when enabling IPv6, ie. when pmacct tries to insert strings like "ipv6-icmp" in a CHAR(4). On the other hand, pmacct is unaware of the length of the field in the schema (nor i'm aware MySQL, or any other supported RDBMS, offers a feature to truncate values) so, in a few docs, i believe it's specified correctness of the schema is user responsibility (basic but effective).
Cheers, Paolo On Tue, Jul 01, 2014 at 06:34:43PM +0200, Raphael Mazelier wrote: > Hum find it, but I seems I found a bug : > > with mysqld parameter : > > sql_mode = TRADITIONAL > > which enable strict mode, an insert failed immediatly if an error of > size or else is detected. > This is strange beacause column ip_proto is CHAR(4), that is sufficient. > > I think pmacct should handle this error earlier, or truncate the > data, because when arriving in the rdbm the field is left blanked. > > Regards, > > > Le 01/07/2014 18:20, Raphael Mazelier a écrit : > >Hello Paolo, > > > >I upgrade my system today to debian wheezy, percona-server-5.6. > >Since this upgrade I have error message like : > > > >Jul 01 18:18:01 ERROR ( out_hour/mysql ): Data too long for column > >'ip_proto' at row 445 > > > >and no data are filled in the database. > > > >How I can debug this issue ? > > > > _______________________________________________ > pmacct-discussion mailing list > http://www.pmacct.net/#mailinglists _______________________________________________ pmacct-discussion mailing list http://www.pmacct.net/#mailinglists
