Hi Andrey, So there are some rows that contain empty ip addresses and this is causing the issue. I don't have a full vision of your config so i can not guess what could be the cause - please send it over. It could also be not a config issue but rather some flow spit by the exporting IPFIX device.
Paolo On Wed, Mar 21, 2018 at 09:21:47AM +0200, Andrey Koblyuk wrote: > Здравствуйте, Paolo. > > Вы писали 21 березня 2018 р., 1:18:26: > > > > Hi Andrey, > > > Yes what i meant is: any chance you can try to understand what precisely > > is the problematic value? If it's a specific one or there is a set of > > values that give problems? Having this info would put us in pole > > position for troubleshooting the issue. Since the field type is 'inet' > > i'm ruling out this is just about v6 addresses. > > Flow contains only ipv4 data. Results with the debug option enabled: > > First purge after daemon start: > Error: > 2018-03-21 09:09:22.167 EET [19801] pmacct@pmacct CONTEXT: COPY > traffic_21032018, line 1, column ip_src: "" > Data (a few lines): > DEBUG ( storage/pgsql ): 2018-03-21 09:09:22,2018-03-21 > 00:00:00,,,0,0,0,0,0,0,0,2018-03-21 09:09:05,0,1970-01-01 03:00:00,0,0,0 > ---?????? > DEBUG ( storage/pgsql ): 2018-03-21 09:09:22,2018-03-21 > 00:00:00,191.234.72.188,94.125.122.215,12883,725,507,12883,443,49896,6,2018-03-21 > 09:07:36,164000,2018-03-21 09:08:45,586000,91,53509 > DEBUG ( storage/pgsql ): 2018-03-21 09:09:22,2018-03-21 > 00:00:00,212.90.184.234,185.16.28.49,12883,507,725,12883,39748,50737,6,2018-03-21 > 09:08:39,323000,2018-03-21 09:08:40,427000,3,120 > DEBUG ( storage/pgsql ): 2018-03-21 09:09:22,2018-03-21 > 00:00:00,35.158.154.235,212.90.176.70,12883,725,507,12883,443,38889,6,2018-03-21 > 09:07:40,917000,2018-03-21 09:08:46,44000,12,1147 > > Error: > 2018-03-21 09:09:33.265 EET [19804] pmacct@pmacct ERROR: invalid input > syntax for type inet: "" > 2018-03-21 09:09:33.265 EET [19804] pmacct@pmacct CONTEXT: COPY > traffic_21032018, line 44702, column ip_src: "" > Data: > DEBUG ( storage/pgsql ): 2018-03-21 09:09:22,2018-03-21 > 00:00:00,212.90.175.202,31.134.211.47,12883,507,755,56823,0,0,1,2018-03-21 > 09:08:11,516000,2018-03-21 09:08:20,989000,3,228 > DEBUG ( storage/pgsql ): 2018-03-21 09:09:22,2018-03-21 > 00:00:00,212.90.162.142,185.158.208.144,12883,507,755,12883,56257,443,6,2018-03-21 > 09:09:12,776000,2018-03-21 09:09:12,817000,101,6713 > DEBUG ( storage/pgsql ): 2018-03-21 09:09:22,2018-03-21 > 00:00:00,,,12883,0,0,15497,0,0,0,2018-03-21 09:09:15,0,1970-01-01 > 03:00:00,0,0,0 ---?????? > DEBUG ( storage/pgsql ): 2018-03-21 09:09:22,2018-03-21 > 00:00:00,2.62.60.114,171.25.204.96,12389,725,546,12883,56156,37777,6,2018-03-21 > 09:07:42,644000,2018-03-21 09:07:45,637000,2,104 > DEBUG ( storage/pgsql ): 2018-03-21 09:09:22,2018-03-21 > 00:00:00,212.90.183.149,120.29.215.38,12883,507,725,12883,53,19131,17,2018-03-21 > 09:04:59,926000,2018-03-21 09:04:59,995000,25,37500 > > I see that under strange conditions the daemon generates an incorrect data > string that does not contain valid data (except the fields > src_as,dst_as,timestamp_start)... > > > -- > ANK32-RIPE > _______________________________________________ pmacct-discussion mailing list http://www.pmacct.net/#mailinglists
