so... after digging a bit it is the combination of 2 things 1/ apparently some web-clients parallelize download by requesting a zillion of small pieces each one generate a log entry.. in the past we saw these mostly for resume download but on match 10th ther was a huge space of these fractionned download which as I said create a log entry each, which in turn confuse the log parsing in thinking that the entire file has been reqeusted and downloaded which explain the weird count
2/ that influx of log was enough apparently to drive a 'no disk space' situation for bilbo2 at about 18-19h00 which prolly explain the lack of log for the following days.... so... a/ I'm going to fix the log parsing to eliminate these false positive... and re-parse a good chunk of the history. b/ we should really work on monitoring, especially for free space, to get advance notice of impendding doom.. to avoid actually loosing logs. Norbert -- To unsubscribe e-mail to: [email protected] Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/website/ All messages sent to this list will be publicly archived and cannot be deleted
