Hi Jeff it seems that on your machine the uburst logger is printing null characters in place of the file header, I made some change, please update and let me know if you see any difference.
Regards Alfredo > On 16 Jul 2018, at 17:37, Jeff Bacon <ba...@walleyesoftware.com> wrote: > > updated to v.3.1.180714, still happening, though not as egregiously - > > > >> -----Original Message----- >> From: ntop-boun...@listgateway.unipi.it >> <mailto:ntop-boun...@listgateway.unipi.it> [mailto:ntop- >> boun...@listgateway.unipi.it <mailto:boun...@listgateway.unipi.it>] On >> Behalf Of Alfredo Cardigliano >> Sent: Monday, June 04, 2018 12:45 PM >> To: n...@unipi.it <mailto:n...@unipi.it> >> Subject: Re: [Ntop] uburst log headed with 0s >> >> The binary is compiled with 3.1.1.1, I guess the API is the same, it should >> work. >> >> Alfredo >> >>> On 4 Jun 2018, at 18:40, Jeff Bacon <ba...@walleyesoftware.com> wrote: >>> >>> will this work with the fiberblaze 3.1.0.1 release still? >>> >>>> -----Original Message----- >>>> From: ntop-boun...@listgateway.unipi.it [mailto:ntop- >>>> boun...@listgateway.unipi.it] On Behalf Of Alfredo Cardigliano >>>> Sent: Friday, June 1, 2018 12:12 PM >>>> To: n...@unipi.it >>>> Cc: ntop@listgateway.unipi.it >>>> Subject: Re: [Ntop] uburst log headed with 0s >>>> >>>> Hi Jeff >>>> I tried to reproduce this with no success, that means it happens under >>>> some condition, >>>> anyway I made some change to the code to make sure it flushes the >>>> buffer correctly, >>>> new packages will be available soon (30 min from now), please check if >>>> you still see >>>> this issue and let me know. >>>> >>>> Thank you >>>> Alfredo >>>> >>>>> On 31 May 2018, at 17:36, Alfredo Cardigliano <cardigli...@ntop.org> >>>> wrote: >>>>> >>>>> Hi Jeff >>>>> could you send me a log file to check what’s happening? I am not sure >>>> I understood. >>>>> >>>>> Thank you >>>>> Alfredo >>>>> >>>>>> On 31 May 2018, at 17:32, Jeff Bacon <ba...@walleyesoftware.com> >>>> wrote: >>>>>> >>>>>> we have uburst monitoring enabled, but our logs always seem to get >>>> headed with a pile of NULs. It seems to be being written as a sparse >>>> file so the file doesn't take up much disk, but it's awfully hard to >>>> parse. this is with 3.1.180226. >>>>>> >>>>>> --interface fbcard:0:a:00 >>>>>> -P=/var/run/n2disk-fbcard:0:a:00.pid >>>>>> -s 9000 >>>>>> --chunk-len 128 >>>>>> --buffer-len 4096 >>>>>> --dump-directory /srv/pcaps/7ticks-A/dumps >>>>>> --max-file-len 512 >>>>>> --max-file-duration 900 >>>>>> --file-prefix fbcard:0:a:0- >>>>>> --max-nested-dirs 10 >>>>>> --max-num-files 1000 >>>>>> --hugepages >>>>>> --timeline-dir /srv/pcaps/7ticks-A/timeline >>>>>> --reader-cpu-affinity 10 >>>>>> --writer-cpu-affinity 12 >>>>>> --compressor-cpu-affinity 32,34,36,38 >>>>>> --uburst-detection >>>>>> --uburst-log /var/log/n2disk/uburst-fbcard:0:a:0.log >>>>>> --uburst-win-size 100 >>>>>> --uburst-link-speed 10000 >>>>>> --uburst-threshold 80 >>>>>> --pcap-compression >>>>>> --cluster-id 1 >>>>>> --index >>>>>> --index-on-compressor-threads >>>>>> --nanoseconds >>>>>> >>>>>> any thoughts? >>>>>> _______________________________________________ >>>>>> Ntop mailing list >>>>>> Ntop@listgateway.unipi.it >>>>>> http://listgateway.unipi.it/mailman/listinfo/ntop >>>>> >>>>> _______________________________________________ >>>>> Ntop mailing list >>>>> Ntop@listgateway.unipi.it >>>>> http://listgateway.unipi.it/mailman/listinfo/ntop >>> >>> _______________________________________________ >>> Ntop mailing list >>> Ntop@listgateway.unipi.it >>> http://listgateway.unipi.it/mailman/listinfo/ntop > > <uburst.log.tar.gz>_______________________________________________ > Ntop mailing list > Ntop@listgateway.unipi.it <mailto:Ntop@listgateway.unipi.it> > http://listgateway.unipi.it/mailman/listinfo/ntop > <http://listgateway.unipi.it/mailman/listinfo/ntop>
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ Ntop mailing list Ntop@listgateway.unipi.it http://listgateway.unipi.it/mailman/listinfo/ntop
