Submissions truncated in log files

Bug #1325607 reported by Steve Magoun
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
canonical-poke
New
Undecided
Unassigned

Bug Description

There is evidence that poke submissions can be truncated in the server logs, leaving us with incomplete data. Note the 'release
' field in these 2 records:

eggfruit/data-2014-04-02-2014-04-03.log:CN [02/Apr/2014:12:50:02 +0000] "GET http://poke.canonical.com/submit?count=4&dcd=canonical-oem-somerville-precise-amd64-20130203-1&product=optiplex%203020&vendor=dell%20inc.&releas HTTP/1.1"

eggfruit/data-2014-04-30-2014-05-01.log:CN [01/May/2014:02:26:36 +0000] "GET http://poke.canonical.com/submit?count=11&dcd=canonical-oem-somerville-precise-amd64-20130203-1&product=OptiPlex%203020&vendor=Dell%20Inc.&relea HTTP/1.1"

The first record has a 1-digit value of 'count'. The second record has a 2-digit value of 'count'. Note that 'release' is missing one extra letter in the second record. I suspect there is something in our reporting that has a limit on record length that results in truncated submissions.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.