plugin-QueuedTracking
plugin-QueuedTracking copied to clipboard
During log importing with queuedtracking enabled bulk tracking returned invalid JSON
errors occurs so often that it is hard to see anything else
2016-01-28 13:29:11,952: [INFO] bulk tracking returned invalid JSON
2016-01-28 13:29:11,953: [INFO] tracker response:
GIF89a�!�,D;
Log importer command
python misc/log-analytics/import_logs.py access.log --url=http://testurl.com --replay-tracking --token-auth=** --recorders=6 --disable-bulk-tracking
the same situation with bulk tracking enabled
@mattab probably related to #5
@jaceklubzinski could you post log file used to reproduce issue? or does it happen randomly with any log file?
we tested it on two completely different log format and warning appeared in both cases
Before writing the message above, locally I was trying to reproduce but couldn't. Can you reproduce this issue on several servers? can you reproduce it locally? can you Slack me an example log file used to reproduce this?
I couldn't reproduce this error on the local environment (with the same logs) but at the same time, the error still occurs in two different environments and with different logs format on the production env.
When this occurs can you check the server error log, maybe an internal server error was logged there?
I can reproduce the issue locally. I don't think this was ever supposed to return such a response or not supported at least. Unless it regressed at some point but cannot see how this should have ever worked.
It is also documented as known issue:
In case you are using bulk tracking the bulk tracking response varies compared to the regular one. We will always return either an image or a 204 HTTP response code in case the parameter
send_image=0
is sent.
Maybe the log importer changed and it used to support http image response
This problem is still valid today:
2018-05-09 15:05:04,069: [INFO] bulk tracking returned invalid JSON
2018-05-09 15:05:04,069: [INFO] tracker response:
GIF89a^A^@^A^@<80>^@^@^@^@^@^@^@^@!<F9>^D^A^@^@^@^@,^@^@^@^@^A^@^A^@^@^B^BD^A^@;
I experienced this error too on some Log-Lines. I am using format "common_complete" (Apache vhost_combined). The error occurs when:
- Method is HEAD instead of GET
- UserAgent is "-"
I am seeing this error too
2021-11-16 14:30:13,412: [INFO] bulk tracking returned invalid JSON
2021-11-16 14:30:13,413: [INFO] tracker response:
b'GIF89a\x01\x00\x01\x00\x80\x00\x00\x00\x00\x00\x00\x00\x00!\xf9\x04\x01\x00\x00\x00\x00,\x00\x00\x00\x00\x01\x00\x01\x00\x00\x02\x02D\x01\x00;'
Matomo 4.5.0 Apache 2 on ubuntu 18.04
@tobiasnteireho when and where is this shown? What command do you execute when this happens?
And are you using the latest version of the log importer?