-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
During log importing with queuedtracking enabled bulk tracking returned invalid JSON #34
Comments
@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:
Maybe the log importer changed and it used to support http image response |
This problem is still valid today:
|
I experienced this error too on some Log-Lines. I am using format "common_complete" (Apache vhost_combined). The error occurs when:
|
I am seeing this error too
Matomo 4.5.0 |
@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? |
errors occurs so often that it is hard to see anything else
Log importer command
the same situation with bulk tracking enabled
@mattab probably related to #5
The text was updated successfully, but these errors were encountered: