Skip to content
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

When importing logs, got Fatal error: Incorrect response from tracking API: 'GIF89a�!�,D;' #5

Closed
mattab opened this issue Mar 31, 2015 · 2 comments
Assignees
Labels

Comments

@mattab
Copy link
Member

mattab commented Mar 31, 2015

When queuedTracking plugin is enabled, when importing server logs, I get the following:

$ ./misc/log-analytics/import_logs.py --url=demo2.piwik.org  ~/admin/log/access.log --idsite=4
0 lines parsed, 0 lines recorded, 0 records/sec (avg), 0 records/sec (current)
Parsing log /home/piwik-demo2/admin/log/access.log...
Fatal error: Incorrect response from tracking API: 'GIF89a���!���,����D�;'
Is the BulkTracking plugin disabled?

Can we fix this issue in QueuedTracking plugin directly or does it need to be fixed in core? hopefully we can fix it in QueuedTracking as we need it ASAP

@mattab mattab added the bug label Mar 31, 2015
@tsteur
Copy link
Member

tsteur commented Mar 31, 2015

See Readme

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.

This is currently expected behaviour. The log importer was recently changed to trigger a fatal when it does not return json which causes that message: matomo-org/matomo#6982 Importing itself should work fine.

@tsteur
Copy link
Member

tsteur commented Mar 31, 2015

Should be fixed in matomo-org/matomo-log-analytics#57

A temporary workaround was done in f918c2b but we will remove this again after matomo-org/matomo-log-analytics#57 was fixed and released see matomo-org/matomo#7595

Be aware that we temporarily change the API output meaning this breaks temporarily the API

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants