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

archive.php failing on GeoIP Update in 1.10.1 #3678

Closed
anonymous-matomo-user opened this issue Jan 16, 2013 · 6 comments
Closed

archive.php failing on GeoIP Update in 1.10.1 #3678

anonymous-matomo-user opened this issue Jan 16, 2013 · 6 comments
Labels
Bug For errors / faults / flaws / inconsistencies etc.

Comments

@anonymous-matomo-user
Copy link

I upgraded to 1.10.1 last night and I setup automatic updating for my geo location database using the suggested URL. Last night when archive.php ran it generated the following errors (note, I changed my filesystem path)

SCHEDULED TASKS
Starting Scheduled tasks... 
ERROR: Got invalid response from API request: http://stats.thingelstad.com/index.php?module=API&method=CoreAdminHome.runScheduledTasks&format=csv&convertToUnicode=0&token_auth=c2a0c68752275b18010b1d93ae97b977&trigger=archivephp. Response was 'task,output
Piwik_PDFReports.dailySchedule,Time elapsed: 1.106s
Piwik_UserCountry_GeoIPAutoUpdater.update,ERROR: Piwik_UserCountry_GeoIPAutoUpdater: failed to download '' to '/path/to/piwik/public_html/misc/GeoIPISP.dat.': curl_exec: <url> malformed'

done
---------------------------
SUMMARY OF ERRORS
Error: Got invalid response from API request: http://stats.thingelstad.com/index.php?module=API&method=CoreAdminHome.runScheduledTasks&format=csv&convertToUnicode=0&token_auth=c2a0c68752275b18010b1d93ae97b977&trigger=archivephp. Response was 'task,output
Piwik_PDFReports.dailySchedule,Time elapsed: 1.106s
Piwik_UserCountry_GeoIPAutoUpdater.update,ERROR: Piwik_UserCountry_GeoIPAutoUpdater: failed to downl
1 total errors during this script execution, please investigate and try and fix these errors
ERROR: 1 total errors during this script execution, please investigate and try and fix these errors. First error was: Got invalid response from API request: http://stats.thingelstad.com/index.php?module=API&method=CoreAdminHome.runScheduledTasks&format=csv&convertToUnicode=0&token_auth=c2a0c68752275b18010b1d93ae97b977&trigger=archivephp. Response was 'task,output
Piwik_PDFReports.dailySchedule,Time elapsed: 1.106s
Piwik_UserCountry_GeoIPAutoUpdater.update,ERROR: Piwik_UserCountry_GeoIPAutoUpdater: failed to downl
PHP Fatal error:  1 total errors during this script execution, please investigate and try and fix these errors. First error was: Got invalid response from API request: http://stats.thingelstad.com/index.php?module=API&method=CoreAdminHome.runScheduledTasks&format=csv&convertToUnicode=0&token_auth=c2a0c68752275b18010b1d93ae97b977&trigger=archivephp. Response was 'task,output
Piwik_PDFReports.dailySchedule,Time elapsed: 1.106s
Piwik_UserCountry_GeoIPAutoUpdater.update,ERROR: Piwik_UserCountry_GeoIPAutoUpdater: failed to downl in /path/to/piwik/public_html/misc/cron/archive.php on line 566

At first I thought the update of the city database failed, but that worked fine. Actually, Piwik was attempting to update the ISP data which I haven't provided a link for, and I don't think is available without paying.

Screenshot of my settings attached.

Keywords: GeoIP

@anonymous-matomo-user
Copy link
Author

Attachment:
screenshot.png

@anonymous-matomo-user
Copy link
Author

Crap. Just noticed that output had my auth token in it and I can't edit the post... ugh.

@anonymous-matomo-user
Copy link
Author

Changed my password and auth_token. Wont make the mistake of posting that again. :-\

@diosmosis
Copy link
Member

(In [7776]) Fixes #3678, use !empty instead of !== false when checking if GeoIP URL is saved.

@mattab
Copy link
Member

mattab commented Jan 18, 2013

Thanks for the report. when you open this URL in your browser with the correct token, what is the full errror message?

@anonymous-matomo-user
Copy link
Author

It looks like the issue is closed now. FWIW, this seems to have just happened the one time. It hasn't happened again.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug For errors / faults / flaws / inconsistencies etc.
Projects
None yet
Development

No branches or pull requests

3 participants