Since I havent found a solution to the following within days of searching, i guess i give it a try and ask the piwik forums about this.
I guess it occured since i updated our installations to one of the previous versions (maybe 1.10, i guess. i did one or two piwik updates after the error started to occur, hoping it would fix the problem) that i get the following error message from the piwik archiving cronjob:
- The result of this error is that sometimes our customers get their PDF reports, and sometimes not. Sometimes it seems to work because e-mails with PDF documents are delivered, the error message though occurs every day.
- Archiving of stats work like a charm, everything else besides the scheduled tasks is executed just fine.
- There are no further errors, not inside the php logs, apache logs or system logs.
- The System is an up-to-date Debian 6 running Piwik 1.11.1. Cron archiving worked like a charm with archive.sh and later on with archive.php. Switching back to archive.sh solves the problem but i would like to continue using archive.php.
- Manually triggering the API request shows the following result inside the browser window: "No data available". I guess that there just arent any daily reports to generate since they should already have been generated by the daily cronjob.
- Memory limits are set to "1024M", which should be more than enough
I guess it occured since i updated our installations to one of the previous versions (maybe 1.10, i guess. i did one or two piwik updates after the error started to occur, hoping it would fix the problem) that i get the following error message from the piwik archiving cronjob:
[...] --------------------------- SCHEDULED TASKS Starting Scheduled tasks... ERROR: Got invalid response from API request: https://piwik.example.com/index.php?module=API&method=CoreAdminHome.runScheduledTasks&format=csv&convertToUnicode=0&token_auth=TOKEN&trigger=archivephp. Response was 'curl_exec: Empty reply from server' done --------------------------- SUMMARY OF ERRORS Error: Got invalid response from API request: https://piwik.example.com/index.php?module=API&method=CoreAdminHome.runScheduledTasks&format=csv&convertToUnicode=0&token_auth=TOKEN&trigger=archivephp. Response was 'curl_exec: Empty reply from server' 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: https://piwik.example.com/index.php?module=API&method=CoreAdminHome.runScheduledTasks&format=csv&convertToUnicode=0&token_auth=TOKEN&trigger=archivephp. Response was 'curl_exec: Empty reply from server' 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: https://piwik.example.com/index.php?module=API&method=CoreAdminHome.runScheduledTasks&format=csv&convertToUnicode=0&token_auth=TOKEN&trigger=archivephp. Response was 'curl_exec: Empty reply from server' in /export/apache/www/misc/cron/archive.php on line 576
- The result of this error is that sometimes our customers get their PDF reports, and sometimes not. Sometimes it seems to work because e-mails with PDF documents are delivered, the error message though occurs every day.
- Archiving of stats work like a charm, everything else besides the scheduled tasks is executed just fine.
- There are no further errors, not inside the php logs, apache logs or system logs.
- The System is an up-to-date Debian 6 running Piwik 1.11.1. Cron archiving worked like a charm with archive.sh and later on with archive.php. Switching back to archive.sh solves the problem but i would like to continue using archive.php.
- Manually triggering the API request shows the following result inside the browser window: "No data available". I guess that there just arent any daily reports to generate since they should already have been generated by the daily cronjob.
- Memory limits are set to "1024M", which should be more than enough