@CarlOrff opened this issue on November 11th 2014

After update to 2.9.0-b8 Piwik stopped tracking. In my logs the following error notice occured:

2014/11/10 17:58:31 [error] 4069#0: *127577 FastCGI sent in stderr: "PHP message: PHP Fatal error: Cannot redeclare geoip_country_code_by_name() in /var/www/vhosts/xxxxxxx/libs/MaxMindGeoIP/geoip.inc on line 1593" while reading response header from upstream

I could fix it by using an older version of geoip.inc.

@tsteur commented on November 11th 2014

Getting same error when trying to run the unit tests in PHP 5.3. Same for geoip_country_name_by_name, for constant GEOIP_DOMAIN_EDITION, ...

MaxMind GeoIP v1 seems to be outdated. Maybe it makes sense to work on #4487?

@mattab commented on November 12th 2014

@tsteur it's bad that the piwik is broken, then I guess we should revert the IPv6 pull request before release? or do you see a way to fix the php 5.3 behavior prior to release on Thursday?

@tsteur commented on November 12th 2014

Would probably revert for 2.9.0 and then try to add GeoIP v2 in next version in case this one works with PHP 5.3. I tried to patch the lib and already added like 10 !defined and !function_exists checks but would have to add way more. Even then I am not sure whether everything still works correct and once the fatals re function_exists are fixed I still get the error

Encountered PHP error when performing redundant tests on GeoIP isp database: 256: error traversing database - perhaps it is corrupt? on line 1783 of /home/vagrant/www/piwik/libs/MaxMindGeoIP/geoip.inc.
@mattab commented on November 12th 2014

@tsteur Ok thanks for the hint. would you be able to revert those commits by any c?hance

@tsteur commented on November 12th 2014

I think so, there is a button for this in GitHub UI ;) Edit: Done. See PR

@mattab commented on November 13th 2014

Would probably revert for 2.9.0 and then try to add GeoIP v2 in next version in case this one works with PHP 5.3.

+1 for trying geoip V2 it would be nice if this worked across all php versions! in issue #4487

@mattab commented on November 13th 2014

revert was successful

This issue was closed on November 13th 2014
Powered by GitHub Issue Mirror