@bcooksley wrote:
Since the Piwik 3.0.0 upgrade we've been seeing the following error messages, for varying siteIds. It doesn't happen on every cron run, and subsequent cron runs often complete successfully. There is no trend which indicates why the issue is being triggered. I've no idea if data is being lost (I certainly hope it is not!)
ERROR [2017-01-08 05:05:04] Got invalid response from API request: ?module=API&method=API.get&idSite=&period=day&date=last52&format=php&trigger=archivephp. The response was empty. This usually means a server error. A solution to this error is generally to increase the value of 'memory_limit' in your php.ini file. For more information and the error message please check in your PHP CLI error log file. As this core:archive command triggers PHP processes over the CLI, you can find where PHP CLI logs are stored by running this command: php -i | grep error_log
ERROR [2017-01-08 05:05:04] Empty or invalid response '' for website id , Time elapsed: 1.703s, skipping
ERROR [2017-01-08 05:05:04] 2 total errors during this script execution, please investigate and try and fix these errors.We're running on Ubuntu 14.04, using PHP 5.5.9-1ubuntu4.20. I've attempted to gather error logs, but none are being generated. This makes me think that Piwik is wrong, and that no error is actually occurring. Prior to the upgrade we never had any issues with Piwik's cronjob.
Posts: 1
Participants: 1