Uncaught exception: /matomo/core/CronArchive.php(599) Got invalid response from API request:

Support & Bugs
1

My cronjob recently started emailing me these errors every hour. (I think it was after I upgraded to the latest version, but I’m not 100% sure on the chronology).

php /home/public/stats/matomo/console core:archive
--url=https://www.matomo.matomo/stats/matomo/ >/dev/null

completed at 2021-08-16 17:03:19 UTC after 2 minutes, 57 seconds and
produced the following output:

ERROR [2021-08-16 17:01:23] 21407  Got invalid response from API request:
?module=API&method=CoreAdminHome.archiveReports&idSite=4&period=day&date=2021-08-16&format=json&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 [2021-08-16 17:01:23] 21407  Error unserializing the following
response from
?module=API&method=CoreAdminHome.archiveReports&idSite=4&period=day&date=2021-08-16&format=json&trigger=archivephp:
''
ERROR [2021-08-16 17:02:14] 21407  Got invalid response from API request:
?module=API&method=CoreAdminHome.archiveReports&idSite=6&period=week&date=2021-08-16&format=json&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 [2021-08-16 17:02:14] 21407  Error unserializing the following
response from
?module=API&method=CoreAdminHome.archiveReports&idSite=6&period=week&date=2021-08-16&format=json&trigger=archivephp:
''
ERROR [2021-08-16 17:03:17] 21407  4 total errors during this script
execution, please investigate and try and fix these errors.
ERROR [2021-08-16 17:03:17] 21407  Uncaught exception:
/home/public/stats/matomo/core/CronArchive.php(599): 4 total errors during
this script execution, please investigate and try and fix these errors.
[Query: , CLI mode: 1]
 
  [Exception]
  4 total errors during this script execution, please investigate and try
and fix these errors.

I enabled the Matomo log, but it does not log any warnings, only ~4MB worth of INFO entries.
Running the same command on my host via SSH completes normally without any errors at all. But the cron job consistently sends me the same errors every hour.

1 Like
2

Here’s some possibly relevant output from my site’s error log:

Error Log: 
[Wed Aug 11 23:11:55.935073 2021] [authz_core:error] [pid 10683:tid 34386219520] [client 208.94.116.209:0] AH01630: client denied by server configuration: /fs9e/wpmu/public/stats/matomo/config/config.ini.php
[Wed Aug 11 23:11:55.986717 2021] [authz_core:error] [pid 10683:tid 34386208000] [client 208.94.116.209:0] AH01630: client denied by server configuration: /fs9e/wpmu/public/stats/matomo/tmp/
[Wed Aug 11 23:11:56.026906 2021] [authz_core:error] [pid 10683:tid 34386208000] [client 208.94.116.209:0] AH01630: client denied by server configuration: /fs9e/wpmu/public/stats/matomo/tmp/empty
[Wed Aug 11 23:11:56.059296 2021] [authz_core:error] [pid 10683:tid 34386548224] [client 208.94.116.209:0] AH01630: client denied by server configuration: /fs9e/wpmu/public/stats/matomo/tmp/cache/tracker/matomocache_general.php
[Wed Aug 11 23:11:56.083352 2021] [authz_core:error] [pid 10683:tid 34387104512] [client 208.94.116.209:0] AH01630: client denied by server configuration: /fs9e/wpmu/public/stats/matomo/lang/en.json
[Wed Aug 11 23:12:06.408337 2021] [authz_core:error] [pid 10683:tid 34386223360] [client 208.94.116.209:0] AH01630: client denied by server configuration: /fs9e/wpmu/public/stats/matomo/config/config.ini.php
[Wed Aug 11 23:12:06.431680 2021] [authz_core:error] [pid 10683:tid 34386223360] [client 208.94.116.209:0] AH01630: client denied by server configuration: /fs9e/wpmu/public/stats/matomo/tmp/
[Wed Aug 11 23:12:06.451956 2021] [authz_core:error] [pid 10683:tid 34386223360] [client 208.94.116.209:0] AH01630: client denied by server configuration: /fs9e/wpmu/public/stats/matomo/tmp/empty
[Wed Aug 11 23:12:06.474805 2021] [authz_core:error] [pid 10683:tid 34386223360] [client 208.94.116.209:0] AH01630: client denied by server configuration: /fs9e/wpmu/public/stats/matomo/tmp/cache/tracker/matomocache_general.php
[Wed Aug 11 23:12:06.495863 2021] [authz_core:error] [pid 10683:tid 34386223360] [client 208.94.116.209:0] AH01630: client denied by server configuration: /fs9e/wpmu/public/stats/matomo/lang/en.json
[Wed Aug 11 23:15:12.025184 2021] [authz_core:error] [pid 10683:tid 34385076224] [client 208.94.116.209:0] AH01630: client denied by server configuration: /fs9e/wpmu/public/stats/matomo/config/config.ini.php
[Wed Aug 11 23:15:12.071460 2021] [authz_core:error] [pid 10683:tid 34385402368] [client 208.94.116.209:0] AH01630: client denied by server configuration: /fs9e/wpmu/public/stats/matomo/tmp/
[Wed Aug 11 23:15:12.110577 2021] [authz_core:error] [pid 10683:tid 34385415168] [client 208.94.116.209:0] AH01630: client denied by server configuration: /stats/matomo/tmp/empty
[Wed Aug 11 23:15:12.138305 2021] [authz_core:error] [pid 10683:tid 34385415168] [client 208.94.116.209:0] AH01630: client denied by server configuration: /stats/matomo/tmp/cache/tracker/matomocache_general.php
[Wed Aug 11 23:15:12.161954 2021] [authz_core:error] [pid 10683:tid 34385415168] [client 208.94.116.209:0] AH01630: client denied by server configuration: /stats/matomo/lang/en.json
[Fri Aug 13 14:53:24.536480 2021] [authz_core:error] [pid 22804:tid 34382665728] [client 208.94.116.209:0] AH01630: client denied by server configuration: /stats/matomo/config/config.ini.php
[Fri Aug 13 14:53:24.557781 2021] [authz_core:error] [pid 22804:tid 34382665728] [client 208.94.116.209:0] AH01630: client denied by server configuration: /stats/matomo/tmp/
[Fri Aug 13 14:53:24.580378 2021] [authz_core:error] [pid 22804:tid 34382665728] [client 208.94.116.209:0] AH01630: client denied by server configuration: /stats/matomo/tmp/empty
[Fri Aug 13 14:53:24.604950 2021] [authz_core:error] [pid 22804:tid 34382665728] [client 208.94.116.209:0] AH01630: client denied by server configuration: /stats/matomo/lang/en.json
[Fri Aug 13 16:37:30.955391 2021] [authz_core:error] [pid 67780:tid 34386224640] [client 208.94.116.209:0] AH01630: client denied by server configuration: /stats/matomo/config/config.ini.php
[Fri Aug 13 16:37:30.983906 2021] [authz_core:error] [pid 67780:tid 34386206720] [client 208.94.116.209:0] AH01630: client denied by server configuration: /stats/matomo/tmp/
[Fri Aug 13 16:37:31.013316 2021] [authz_core:error] [pid 67780:tid 34386206720] [client 208.94.116.209:0] AH01630: client denied by server configuration: /stats/matomo/tmp/empty
[Fri Aug 13 16:37:31.045401 2021] [authz_core:error] [pid 67780:tid 34386206720] [client 208.94.116.209:0] AH01630: client denied by server configuration: /stats/matomo/tmp/cache/tracker/matomocache_general.php
[Fri Aug 13 16:37:31.078975 2021] [authz_core:error] [pid 67780:tid 34386210560] [client 208.94.116.209:0] AH01630: client denied by server configuration: /stats/matomo/lang/en.json
[Fri Aug 13 16:38:04.871221 2021] [authz_core:error] [pid 67780:tid 34386208000] [client 208.94.116.209:0] AH01630: client denied by server configuration: /stats/matomo/config/config.ini.php
[Fri Aug 13 16:38:04.896504 2021] [authz_core:error] [pid 67780:tid 34386208000] [client 208.94.116.209:0] AH01630: client denied by server configuration: /stats/matomo/tmp/
[Fri Aug 13 16:38:04.918783 2021] [authz_core:error] [pid 67780:tid 34386208000] [client 208.94.116.209:0] AH01630: client denied by server configuration: /stats/matomo/tmp/empty
[Fri Aug 13 16:38:04.944455 2021] [authz_core:error] [pid 67780:tid 34386208000] [client 208.94.116.209:0] AH01630: client denied by server configuration: /stats/matomo/tmp/cache/tracker/matomocache_general.php
[Fri Aug 13 16:38:04.966623 2021] [authz_core:error] [pid 67780:tid 34386208000] [client 208.94.116.209:0] AH01630: client denied by server configuration: /stats/matomo/lang/en.json
[Fri Aug 13 16:49:57.536789 2021] [authz_core:error] [pid 67780:tid 34385656832] [client 208.94.116.209:0] AH01630: client denied by server configuration: /stats/matomo/config/config.ini.php
[Fri Aug 13 16:49:57.562465 2021] [authz_core:error] [pid 67780:tid 34385650432] [client 208.94.116.209:0] AH01630: client denied by server configuration: /stats/matomo/tmp/
[Fri Aug 13 16:49:57.591863 2021] [authz_core:error] [pid 67780:tid 34385655552] [client 208.94.116.209:0] AH01630: client denied by server configuration: /stats/matomo/tmp/empty
[Fri Aug 13 16:49:57.625672 2021] [authz_core:error] [pid 67780:tid 34385655552] [client 208.94.116.209:0] AH01630: client denied by server configuration: /stats/matomo/tmp/cache/tracker/matomocache_general.php
[Fri Aug 13 16:49:57.669515 2021] [authz_core:error] [pid 67780:tid 34385655552] [client 208.xx.xxx.xxx:0] AH01630: client denied by server configuration: /stats/matomo/lang/en.json
[Sat Aug 14 16:14:47.213393 2021] [authz_core:error] [pid 29750:tid 34386296320] [client 208.xx.xxx.xxx:0] AH01630: client denied by server configuration: /stats/matomo/config/config.ini.php
[Sat Aug 14 16:14:47.236705 2021] [authz_core:error] [pid 29750:tid 34385970176] [client 208.xx.xxx.xxx:0] AH01630: client denied by server configuration: /stats/matomo/tmp/
[Sat Aug 14 16:14:47.262020 2021] [authz_core:error] [pid 29750:tid 34386296320] [client 208.xx.xxx.xxx:0] AH01630: client denied by server configuration: /stats/matomo/tmp/empty
[Sat Aug 14 16:14:47.289638 2021] [authz_core:error] [pid 29750:tid 34386296320] [client 208.xx.xxx.xxx:0] AH01630: client denied by server configuration: /stats/matomo/tmp/cache/tracker/matomocache_general.php
[Sat Aug 14 16:14:47.319077 2021] [authz_core:error] [pid 29750:tid 34386296320] [client 208.xx.xxx.xxx:0] AH01630: client denied by server configuration: /stats/matomo/lang/en.json
[Sat Aug 14 16:53:33.664508 2021] [authz_core:error] [pid 29750:tid 34382750208] [client 208.xx.xxx.xxx:0] AH01630: client denied by server configuration: /stats/matomo/config/config.ini.php
[Sat Aug 14 16:53:33.704337 2021] [authz_core:error] [pid 29750:tid 34382750208] [client 208.xx.xxx.xxx:0] AH01630: client denied by server configuration: /stats/matomo/tmp/
[Sat Aug 14 16:53:33.739483 2021] [authz_core:error] [pid 29750:tid 34382750208] [client 208.xx.xxx.xxx:0] AH01630: client denied by server configuration: /stats/matomo/tmp/empty
[Sat Aug 14 16:53:33.784035 2021] [authz_core:error] [pid 29750:tid 34382750208] [client 208.xx.xxx.xxx:0] AH01630: client denied by server configuration: /stats/matomo/tmp/cache/tracker/matomocache_general.php
[Sat Aug 14 16:53:33.831317 2021] [authz_core:error] [pid 29750:tid 34382750208] [client 208.xx.xxx.xxx:0] AH01630: client denied by server configuration: /stats/matomo/lang/en.json
[Sat Aug 14 16:53:34.695378 2021] [authz_core:error] [pid 29750:tid 34382737408] [client 208.xx.xxx.xxx:0] AH01630: client denied by server configuration: /stats/matomo/config/config.ini.php
[Sat Aug 14 16:53:34.717230 2021] [authz_core:error] [pid 29750:tid 34385077504] [client 208.xx.xxx.xxx:0] AH01630: client denied by server configuration: /stats/matomo/tmp/
[Sat Aug 14 16:53:34.738537 2021] [authz_core:error] [pid 29750:tid 34385077504] [client 208.xx.xxx.xxx:0] AH01630: client denied by server configuration: /stats/matomo/tmp/empty
[Sat Aug 14 16:53:34.762621 2021] [authz_core:error] [pid 29750:tid 34385077504] [client 208.xx.xxx.xxx:0] AH01630: client denied by server configuration: /stats/matomo/tmp/cache/tracker/matomocache_general.php
[Sat Aug 14 16:53:34.784473 2021] [authz_core:error] [pid 29750:tid 34385077504] [client 208.xx.xxx.xxx:0] AH01630: client denied by server configuration: /stats/matomo/lang/en.json

I already tried increasing memory_limit, but that didn’t help.

1 Like
3

Any tips? My email inbox is filling up with error messages. :frowning:

4

Hi,

I don’t know what is the error, but I can give a bit of context that might help you find it:

This is the actual error: During archiving (which runs with php-cli executed from your cronjob) the cli programm makes requests to the Matomo API (which are then handled by the PHP your webserver uses). The archiving cli expects to get back useful data from the API and continue with that but instead it only receives '' (probably because something failed) and exits the archiving.

This is unrelated and just Matomo testing if this file is protected by your webserver and your webserver denying this request as it should.

1 Like
5

Thanks, @Lukas for your help. I kinda figured as much, but it’s good to hear from someone who knows a little better how Matomo works. :slight_smile:

The problem is that I have no way to further diagnose this issue, because my logs won’t show any errors. :frowning: Both the system log and the matomo log are clear. Running the command manually doesn’t cause any errors either. I’m not sure what to do next!

Maybe this will help: I tried running my cron job without >/dev/null so that it would log the entire output. Here’s the log:

Matomo Email Log (complete) 
Hello,

Your scheduled task "matomo" on site xxxx:

php /home/public/stats/matomo/console core:archive
--url=https://www.matomo.matomo.com/stats/matomo/

completed at 2021-08-15 00:04:31 UTC after 3 minutes, 59 seconds and
produced the following output:

INFO [2021-08-15 00:00:39] 80800  ---------------------------
INFO [2021-08-15 00:00:39] 80800  INIT
INFO [2021-08-15 00:00:39] 80800  Running Matomo 4.4.1 as Super User
INFO [2021-08-15 00:00:39] 80800  ---------------------------
INFO [2021-08-15 00:00:39] 80800  NOTES
INFO [2021-08-15 00:00:40] 80800  - Async process archiving supported,
using CliMulti.
INFO [2021-08-15 00:00:40] 80800  - Reports for today will be processed at
most every 900 seconds. You can change this value in Matomo UI > Settings >
General Settings.
INFO [2021-08-15 00:00:40] 80800  - Archiving was last executed without
error 7 hours 27 min ago
INFO [2021-08-15 00:00:42] 80800  ---------------------------
INFO [2021-08-15 00:00:42] 80800  START
INFO [2021-08-15 00:00:42] 80800  Starting Matomo reports archiving...
INFO [2021-08-15 00:00:46] 80800  Start processing archives for site 1.
INFO [2021-08-15 00:00:46] 80800    Will invalidate archived reports for
today in site ID = 1's timezone (2021-08-14 00:00:00).
INFO [2021-08-15 00:00:47] 80800    Will invalidate archived reports for
yesterday in site ID = 1's timezone (2021-08-13 00:00:00).
INFO [2021-08-15 00:00:54] 80800  Archived website id 1, period = day, date
= 2021-08-14, segment = '', 7 visits found. Time elapsed: 6.523s
INFO [2021-08-15 00:01:00] 80800  Archived website id 1, period = week,
date = 2021-08-09, segment = '', 81 visits found. Time elapsed: 5.257s
INFO [2021-08-15 00:01:04] 80800  Archived website id 1, period = month,
date = 2021-08-01, segment = '', 184 visits found. Time elapsed: 3.854s
INFO [2021-08-15 00:01:10] 80800  Archived website id 1, period = year,
date = 2021-01-01, segment = '', 3205 visits found. Time elapsed: 5.200s
INFO [2021-08-15 00:01:10] 80800  Finished archiving for site 1, 4 API
requests, Time elapsed: 23.531s [1 / 11 done]
INFO [2021-08-15 00:01:11] 80800  Start processing archives for site 2.
INFO [2021-08-15 00:01:11] 80800    Will invalidate archived reports for
today in site ID = 2's timezone (2021-08-14 00:00:00).
INFO [2021-08-15 00:01:11] 80800    Will invalidate archived reports for
yesterday in site ID = 2's timezone (2021-08-13 00:00:00).
INFO [2021-08-15 00:01:16] 80800  Archived website id 2, period = day, date
= 2021-08-14, segment = '', 1 visits found. Time elapsed: 5.099s
INFO [2021-08-15 00:01:22] 80800  Archived website id 2, period = week,
date = 2021-08-09, segment = '', 59 visits found. Time elapsed: 5.795s
INFO [2021-08-15 00:01:27] 80800  Archived website id 2, period = month,
date = 2021-08-01, segment = '', 60 visits found. Time elapsed: 4.684s
ERROR [2021-08-15 00:01:35] 80800  Got invalid response from API request:
?module=API&method=CoreAdminHome.archiveReports&idSite=2&period=year&date=2021-01-01&format=json&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
INFO [2021-08-15 00:01:35] 80800  ''
ERROR [2021-08-15 00:01:35] 80800  Error unserializing the following
response from
?module=API&method=CoreAdminHome.archiveReports&idSite=2&period=year&date=2021-01-01&format=json&trigger=archivephp:
''
INFO [2021-08-15 00:01:35] 80800  Finished archiving for site 2, 4 API
requests, Time elapsed: 23.950s [2 / 11 done]
INFO [2021-08-15 00:01:35] 80800  Start processing archives for site 3.
INFO [2021-08-15 00:01:35] 80800    Will invalidate archived reports for
today in site ID = 3's timezone (2021-08-14 00:00:00).
INFO [2021-08-15 00:01:40] 80800  Archived website id 3, period = day, date
= 2021-08-14, segment = '', 1 visits found. Time elapsed: 4.522s
INFO [2021-08-15 00:01:47] 80800  Archived website id 3, period = week,
date = 2021-08-09, segment = '', 9 visits found. Time elapsed: 7.276s
INFO [2021-08-15 00:01:51] 80800  Archived website id 3, period = month,
date = 2021-08-01, segment = '', 38 visits found. Time elapsed: 3.893s
INFO [2021-08-15 00:01:56] 80800  Archived website id 3, period = year,
date = 2021-01-01, segment = '', 859 visits found. Time elapsed: 4.963s
INFO [2021-08-15 00:01:56] 80800  Finished archiving for site 3, 4 API
requests, Time elapsed: 21.401s [3 / 11 done]
INFO [2021-08-15 00:01:56] 80800  Start processing archives for site 4.
INFO [2021-08-15 00:01:56] 80800    Will invalidate archived reports for
today in site ID = 4's timezone (2021-08-14 00:00:00).
INFO [2021-08-15 00:01:56] 80800    Will invalidate archived reports for
yesterday in site ID = 4's timezone (2021-08-13 00:00:00).
INFO [2021-08-15 00:02:01] 80800  Archived website id 4, period = day, date
= 2021-08-14, segment = '', 10 visits found. Time elapsed: 4.798s
INFO [2021-08-15 00:02:07] 80800  Archived website id 4, period = week,
date = 2021-08-09, segment = '', 93 visits found. Time elapsed: 5.310s
ERROR [2021-08-15 00:02:12] 80800  Got invalid response from API request:
?module=API&method=CoreAdminHome.archiveReports&idSite=4&period=month&date=2021-08-01&format=json&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
INFO [2021-08-15 00:02:12] 80800  ''
ERROR [2021-08-15 00:02:12] 80800  Error unserializing the following
response from
?module=API&method=CoreAdminHome.archiveReports&idSite=4&period=month&date=2021-08-01&format=json&trigger=archivephp:
''
INFO [2021-08-15 00:02:19] 80800  Archived website id 4, period = year,
date = 2021-01-01, segment = '', 4579 visits found. Time elapsed: 6.427s
INFO [2021-08-15 00:02:19] 80800  Finished archiving for site 4, 4 API
requests, Time elapsed: 22.172s [4 / 11 done]
INFO [2021-08-15 00:02:19] 80800  Start processing archives for site 5.
INFO [2021-08-15 00:02:19] 80800  Finished archiving for site 5, 0 API
requests, Time elapsed: 0.023s [5 / 11 done]
INFO [2021-08-15 00:02:19] 80800  Start processing archives for site 6.
INFO [2021-08-15 00:02:19] 80800    Will invalidate archived reports for
today in site ID = 6's timezone (2021-08-14 00:00:00).
INFO [2021-08-15 00:02:19] 80800    Will invalidate archived reports for
yesterday in site ID = 6's timezone (2021-08-13 00:00:00).
INFO [2021-08-15 00:02:23] 80800  Archived website id 6, period = day, date
= 2021-08-14, segment = '', 3 visits found. Time elapsed: 3.920s
INFO [2021-08-15 00:02:30] 80800  Archived website id 6, period = week,
date = 2021-08-09, segment = '', 66 visits found. Time elapsed: 6.483s
INFO [2021-08-15 00:02:37] 80800  Archived website id 6, period = month,
date = 2021-08-01, segment = '', 129 visits found. Time elapsed: 6.273s
INFO [2021-08-15 00:02:45] 80800  Archived website id 6, period = year,
date = 2021-01-01, segment = '', 774 visits found. Time elapsed: 8.124s
INFO [2021-08-15 00:02:45] 80800  Finished archiving for site 6, 4 API
requests, Time elapsed: 26.501s [6 / 11 done]
INFO [2021-08-15 00:02:46] 80800  Start processing archives for site 7.
INFO [2021-08-15 00:02:46] 80800    Will invalidate archived reports for
today in site ID = 7's timezone (2021-08-14 00:00:00).
INFO [2021-08-15 00:02:46] 80800    Will invalidate archived reports for
yesterday in site ID = 7's timezone (2021-08-13 00:00:00).
INFO [2021-08-15 00:02:50] 80800  Archived website id 7, period = day, date
= 2021-08-14, segment = '', 9 visits found. Time elapsed: 4.624s
INFO [2021-08-15 00:02:55] 80800  Archived website id 7, period = week,
date = 2021-08-09, segment = '', 49 visits found. Time elapsed: 4.710s
INFO [2021-08-15 00:03:01] 80800  Archived website id 7, period = month,
date = 2021-08-01, segment = '', 159 visits found. Time elapsed: 5.063s
INFO [2021-08-15 00:03:06] 80800  Archived website id 7, period = year,
date = 2021-01-01, segment = '', 3703 visits found. Time elapsed: 4.919s
INFO [2021-08-15 00:03:06] 80800  Finished archiving for site 7, 4 API
requests, Time elapsed: 20.029s [7 / 11 done]
INFO [2021-08-15 00:03:06] 80800  Start processing archives for site 8.
INFO [2021-08-15 00:03:06] 80800    Will invalidate archived reports for
today in site ID = 8's timezone (2021-08-14 00:00:00).
INFO [2021-08-15 00:03:06] 80800    Will invalidate archived reports for
yesterday in site ID = 8's timezone (2021-08-13 00:00:00).
INFO [2021-08-15 00:03:10] 80800  Archived website id 8, period = day, date
= 2021-08-14, segment = '', 9 visits found. Time elapsed: 4.564s
INFO [2021-08-15 00:03:19] 80800  Archived website id 8, period = week,
date = 2021-08-09, segment = '', 77 visits found. Time elapsed: 8.427s
INFO [2021-08-15 00:03:31] 80800  Archived website id 8, period = month,
date = 2021-08-01, segment = '', 199 visits found. Time elapsed: 12.150s
ERROR [2021-08-15 00:03:40] 80800  Got invalid response from API request:
?module=API&method=CoreAdminHome.archiveReports&idSite=8&period=year&date=2021-01-01&format=json&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
INFO [2021-08-15 00:03:40] 80800  ''
ERROR [2021-08-15 00:03:40] 80800  Error unserializing the following
response from
?module=API&method=CoreAdminHome.archiveReports&idSite=8&period=year&date=2021-01-01&format=json&trigger=archivephp:
''
INFO [2021-08-15 00:03:40] 80800  Finished archiving for site 8, 4 API
requests, Time elapsed: 33.935s [8 / 11 done]
INFO [2021-08-15 00:03:40] 80800  Start processing archives for site 9.
INFO [2021-08-15 00:03:40] 80800    Will invalidate archived reports for
today in site ID = 9's timezone (2021-08-14 00:00:00).
INFO [2021-08-15 00:03:40] 80800    Will invalidate archived reports for
yesterday in site ID = 9's timezone (2021-08-13 00:00:00).
INFO [2021-08-15 00:03:45] 80800  Archived website id 9, period = day, date
= 2021-08-14, segment = '', 5 visits found. Time elapsed: 4.882s
INFO [2021-08-15 00:03:52] 80800  Archived website id 9, period = week,
date = 2021-08-09, segment = '', 57 visits found. Time elapsed: 7.354s
INFO [2021-08-15 00:03:58] 80800  Archived website id 9, period = month,
date = 2021-08-01, segment = '', 109 visits found. Time elapsed: 5.920s
INFO [2021-08-15 00:04:03] 80800  Archived website id 9, period = year,
date = 2021-01-01, segment = '', 2209 visits found. Time elapsed: 4.919s
INFO [2021-08-15 00:04:03] 80800  Finished archiving for site 9, 4 API
requests, Time elapsed: 23.675s [9 / 11 done]
INFO [2021-08-15 00:04:04] 80800  Start processing archives for site 10.
INFO [2021-08-15 00:04:04] 80800    Will invalidate archived reports for
today in site ID = 10's timezone (2021-08-14 00:00:00).
INFO [2021-08-15 00:04:04] 80800    Will invalidate archived reports for
yesterday in site ID = 10's timezone (2021-08-13 00:00:00).
INFO [2021-08-15 00:04:10] 80800  Archived website id 10, period = day,
date = 2021-08-14, segment = '', 4 visits found. Time elapsed: 6.527s
INFO [2021-08-15 00:04:17] 80800  Archived website id 10, period = week,
date = 2021-08-09, segment = '', 36 visits found. Time elapsed: 6.161s
INFO [2021-08-15 00:04:21] 80800  Archived website id 10, period = month,
date = 2021-08-01, segment = '', 56 visits found. Time elapsed: 4.401s
INFO [2021-08-15 00:04:28] 80800  Archived website id 10, period = year,
date = 2021-01-01, segment = '', 522 visits found. Time elapsed: 6.599s
INFO [2021-08-15 00:04:28] 80800  Finished archiving for site 10, 4 API
requests, Time elapsed: 24.404s [10 / 11 done]
INFO [2021-08-15 00:04:28] 80800  Start processing archives for site 11.
INFO [2021-08-15 00:04:28] 80800  Finished archiving for site 11, 0 API
requests, Time elapsed: 0.013s [11 / 11 done]
INFO [2021-08-15 00:04:28] 80800  Done archiving!
INFO [2021-08-15 00:04:28] 80800  ---------------------------
INFO [2021-08-15 00:04:28] 80800  SUMMARY
INFO [2021-08-15 00:04:28] 80800  Processed 33 archives.
INFO [2021-08-15 00:04:28] 80800  Total API requests: 36
INFO [2021-08-15 00:04:28] 80800  done: 36 req, 226355 ms, 6 errors.
INFO [2021-08-15 00:04:28] 80800  Time elapsed: 226.355s
INFO [2021-08-15 00:04:28] 80800  ---------------------------
INFO [2021-08-15 00:04:28] 80800  SCHEDULED TASKS
INFO [2021-08-15 00:04:29] 80800  Starting Scheduled tasks... 
INFO [2021-08-15 00:04:29] 80800  Scheduler: executing task
Piwik\Plugins\CoreAdminHome\Tasks.invalidateOutdatedArchives...
INFO [2021-08-15 00:04:29] 80800  Browser triggered archiving disabled,
archives will be invalidated during core:archive.
INFO [2021-08-15 00:04:29] 80800  Scheduler: finished. Time elapsed: 0.000s
INFO [2021-08-15 00:04:29] 80800  Scheduler: executing task
Piwik\Plugins\CoreAdminHome\Tasks.deleteOldFingerprintSalts...
INFO [2021-08-15 00:04:29] 80800  Scheduler: finished. Time elapsed: 0.035s
INFO [2021-08-15 00:04:29] 80800  Scheduler: executing task
Piwik\Plugins\CoreAdminHome\Tasks.purgeOutdatedArchives...
INFO [2021-08-15 00:04:29] 80800  Purging archives in 68 archive tables.
INFO [2021-08-15 00:04:29] 80800  deleteArchivesWithPeriod:
matomo_archive_numeric_2018_12 with period = 5 and date = 2021-08-14
00:00:00
INFO [2021-08-15 00:04:29] 80800  deleteArchivesWithPeriod:
matomo_archive_numeric_2019_01 with period = 5 and date = 2021-08-14
00:00:00
INFO [2021-08-15 00:04:29] 80800  deleteArchivesWithPeriod:
matomo_archive_numeric_2019_02 with period = 5 and date = 2021-08-14
00:00:00
INFO [2021-08-15 00:04:29] 80800  deleteArchivesWithPeriod:
matomo_archive_numeric_2019_03 with period = 5 and date = 2021-08-14
00:00:00
INFO [2021-08-15 00:04:29] 80800  deleteArchivesWithPeriod:
matomo_archive_numeric_2019_04 with period = 5 and date = 2021-08-14
00:00:00
INFO [2021-08-15 00:04:29] 80800  deleteArchivesWithPeriod:
matomo_archive_numeric_2019_05 with period = 5 and date = 2021-08-14
00:00:00
INFO [2021-08-15 00:04:29] 80800  deleteArchivesWithPeriod:
matomo_archive_numeric_2019_06 with period = 5 and date = 2021-08-14
00:00:00
INFO [2021-08-15 00:04:29] 80800  deleteArchivesWithPeriod:
matomo_archive_numeric_2019_07 with period = 5 and date = 2021-08-14
00:00:00
INFO [2021-08-15 00:04:29] 80800  deleteArchivesWithPeriod:
matomo_archive_numeric_2019_08 with period = 5 and date = 2021-08-14
00:00:00
INFO [2021-08-15 00:04:29] 80800  deleteArchivesWithPeriod:
matomo_archive_numeric_2019_09 with period = 5 and date = 2021-08-14
00:00:00
INFO [2021-08-15 00:04:29] 80800  deleteArchivesWithPeriod:
matomo_archive_numeric_2019_10 with period = 5 and date = 2021-08-14
00:00:00
INFO [2021-08-15 00:04:29] 80800  deleteArchivesWithPeriod:
matomo_archive_numeric_2019_11 with period = 5 and date = 2021-08-14
00:00:00
INFO [2021-08-15 00:04:29] 80800  deleteArchivesWithPeriod:
matomo_archive_numeric_2019_12 with period = 5 and date = 2021-08-14
00:00:00
INFO [2021-08-15 00:04:29] 80800  deleteArchivesWithPeriod:
matomo_archive_numeric_2020_01 with period = 5 and date = 2021-08-14
00:00:00
INFO [2021-08-15 00:04:29] 80800  deleteArchivesWithPeriod:
matomo_archive_numeric_2020_02 with period = 5 and date = 2021-08-14
00:00:00
INFO [2021-08-15 00:04:29] 80800  deleteArchivesWithPeriod:
matomo_archive_numeric_2020_03 with period = 5 and date = 2021-08-14
00:00:00
INFO [2021-08-15 00:04:29] 80800  deleteArchivesWithPeriod:
matomo_archive_numeric_2020_04 with period = 5 and date = 2021-08-14
00:00:00
INFO [2021-08-15 00:04:29] 80800  deleteArchivesWithPeriod:
matomo_archive_numeric_2020_05 with period = 5 and date = 2021-08-14
00:00:00
INFO [2021-08-15 00:04:29] 80800  deleteArchivesWithPeriod:
matomo_archive_numeric_2020_06 with period = 5 and date = 2021-08-14
00:00:00
INFO [2021-08-15 00:04:29] 80800  deleteArchivesWithPeriod:
matomo_archive_numeric_2020_07 with period = 5 and date = 2021-08-14
00:00:00
INFO [2021-08-15 00:04:29] 80800  deleteArchivesWithPeriod:
matomo_archive_numeric_2020_08 with period = 5 and date = 2021-08-14
00:00:00
INFO [2021-08-15 00:04:29] 80800  deleteArchivesWithPeriod:
matomo_archive_numeric_2020_09 with period = 5 and date = 2021-08-14
00:00:00
INFO [2021-08-15 00:04:29] 80800  deleteArchivesWithPeriod:
matomo_archive_numeric_2020_10 with period = 5 and date = 2021-08-14
00:00:00
INFO [2021-08-15 00:04:29] 80800  deleteArchivesWithPeriod:
matomo_archive_numeric_2020_11 with period = 5 and date = 2021-08-14
00:00:00
INFO [2021-08-15 00:04:29] 80800  deleteArchivesWithPeriod:
matomo_archive_numeric_2020_12 with period = 5 and date = 2021-08-14
00:00:00
INFO [2021-08-15 00:04:29] 80800  deleteArchivesWithPeriod:
matomo_archive_numeric_2021_01 with period = 5 and date = 2021-08-14
00:00:00
INFO [2021-08-15 00:04:30] 80800  deleteArchivesWithPeriod:
matomo_archive_numeric_2021_02 with period = 5 and date = 2021-08-14
00:00:00
INFO [2021-08-15 00:04:30] 80800  deleteArchivesWithPeriod:
matomo_archive_numeric_2021_03 with period = 5 and date = 2021-08-14
00:00:00
INFO [2021-08-15 00:04:30] 80800  deleteArchivesWithPeriod:
matomo_archive_numeric_2021_04 with period = 5 and date = 2021-08-14
00:00:00
INFO [2021-08-15 00:04:30] 80800  deleteArchivesWithPeriod:
matomo_archive_numeric_2021_05 with period = 5 and date = 2021-08-14
00:00:00
INFO [2021-08-15 00:04:30] 80800  deleteArchivesWithPeriod:
matomo_archive_numeric_2021_06 with period = 5 and date = 2021-08-14
00:00:00
INFO [2021-08-15 00:04:30] 80800  deleteArchivesWithPeriod:
matomo_archive_numeric_2021_07 with period = 5 and date = 2021-08-14
00:00:00
INFO [2021-08-15 00:04:30] 80800  deleteArchivesWithPeriod:
matomo_archive_numeric_2021_08 with period = 5 and date = 2021-08-14
00:00:00
INFO [2021-08-15 00:04:30] 80800  deleteArchivesWithPeriod:
matomo_archive_numeric_2021_09 with period = 5 and date = 2021-08-14
00:00:00
INFO [2021-08-15 00:04:30] 80800  Scheduler: finished. Time elapsed: 1.735s
INFO [2021-08-15 00:04:30] 80800  Scheduler: executing task
Piwik\Plugins\Login\Tasks.cleanupBruteForceLogs...
INFO [2021-08-15 00:04:30] 80800  Scheduler: finished. Time elapsed: 0.002s
INFO [2021-08-15 00:04:30] 80800  Scheduler: executing task
Piwik\Plugins\TwoFactorAuth\Tasks.cleanupTwoFaCodesUsedRecently...
INFO [2021-08-15 00:04:30] 80800  Scheduler: finished. Time elapsed: 0.001s
INFO [2021-08-15 00:04:30] 80800  Scheduler: executing task
Piwik\Plugins\UsersManager\Tasks.cleanupExpiredTokens...
INFO [2021-08-15 00:04:30] 80800  Scheduler: finished. Time elapsed: 0.001s
INFO [2021-08-15 00:04:30] 80800  Scheduler: executing task
Piwik\Plugins\UsersManager\Tasks.setUserDefaultReportPreference...
INFO [2021-08-15 00:04:30] 80800  Scheduler: finished. Time elapsed: 0.006s
INFO [2021-08-15 00:04:30] 80800  Scheduler: executing task
Piwik\Plugins\CustomJsTracker\Tasks.updateTracker...
INFO [2021-08-15 00:04:30] 80800  Scheduler: finished. Time elapsed: 0.003s
INFO [2021-08-15 00:04:30] 80800  Scheduler: executing task
Piwik\Plugins\CoreAdminHome\Tasks.purgeInvalidatedArchives...
INFO [2021-08-15 00:04:30] 80800  Scheduler: finished. Time elapsed: 0.077s
INFO [2021-08-15 00:04:30] 80800  Scheduler: executing task
Piwik\Plugins\CoreAdminHome\Tasks.purgeInvalidationsForDeletedSites...
INFO [2021-08-15 00:04:30] 80800  Scheduler: finished. Time elapsed: 0.002s
INFO [2021-08-15 00:04:30] 80800  Scheduler: executing task
Piwik\Plugins\PrivacyManager\Tasks.deleteReportData...
INFO [2021-08-15 00:04:30] 80800  Scheduler: finished. Time elapsed: 0.008s
INFO [2021-08-15 00:04:30] 80800  Scheduler: executing task
Piwik\Plugins\PrivacyManager\Tasks.deleteLogData...
INFO [2021-08-15 00:04:30] 80800  Scheduler: finished. Time elapsed: 0.000s
INFO [2021-08-15 00:04:30] 80800  Scheduler: executing task
Piwik\Plugins\PrivacyManager\Tasks.anonymizePastData...
INFO [2021-08-15 00:04:30] 80800  Scheduler: finished. Time elapsed: 0.002s
INFO [2021-08-15 00:04:30] 80800  Scheduler: executing task
Piwik\Plugins\CoreAdminHome\Tasks.cleanupTrackingFailures...
INFO [2021-08-15 00:04:30] 80800  Scheduler: finished. Time elapsed: 0.005s
INFO [2021-08-15 00:04:30] 80800  Scheduler: executing task
Piwik\Plugins\CoreUpdater\Tasks.sendNotificationIfUpdateAvailable...
INFO [2021-08-15 00:04:30] 80800  Scheduler: finished. Time elapsed: 0.003s
INFO [2021-08-15 00:04:30] 80800  Scheduler: executing task
Piwik\Plugins\Marketplace\Tasks.clearAllCacheEntries...
INFO [2021-08-15 00:04:31] 80800  Scheduler: finished. Time elapsed: 0.052s
INFO [2021-08-15 00:04:31] 80800  Scheduler: executing task
Piwik\Plugins\Marketplace\Tasks.sendNotificationIfUpdatesAvailable...
INFO [2021-08-15 00:04:31] 80800  Scheduler: finished. Time elapsed: 0.028s
INFO [2021-08-15 00:04:31] 80800  done
INFO [2021-08-15 00:04:31] 80800  ---------------------------
INFO [2021-08-15 00:04:31] 80800  ---------------------------
INFO [2021-08-15 00:04:31] 80800  SUMMARY OF ERRORS
INFO [2021-08-15 00:04:31] 80800  Error: Got invalid response from API
request:
?module=API&method=CoreAdminHome.archiveReports&idSite=2&period=year&date=2021-01-01&format=json&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
INFO [2021-08-15 00:04:31] 80800  Error: Error unserializing the following
response from
?module=API&method=CoreAdminHome.archiveReports&idSite=2&period=year&date=2021-01-01&format=json&trigger=archivephp:
''
INFO [2021-08-15 00:04:31] 80800  Error: Got invalid response from API
request:
?module=API&method=CoreAdminHome.archiveReports&idSite=4&period=month&date=2021-08-01&format=json&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
INFO [2021-08-15 00:04:31] 80800  Error: Error unserializing the following
response from
?module=API&method=CoreAdminHome.archiveReports&idSite=4&period=month&date=2021-08-01&format=json&trigger=archivephp:
''
INFO [2021-08-15 00:04:31] 80800  Error: Got invalid response from API
request:
?module=API&method=CoreAdminHome.archiveReports&idSite=8&period=year&date=2021-01-01&format=json&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
INFO [2021-08-15 00:04:31] 80800  Error: Error unserializing the following
response from
?module=API&method=CoreAdminHome.archiveReports&idSite=8&period=year&date=2021-01-01&format=json&trigger=archivephp:
''
ERROR [2021-08-15 00:04:31] 80800  6 total errors during this script
execution, please investigate and try and fix these errors.
ERROR [2021-08-15 00:04:31] 80800  Uncaught exception:
/home/public/stats/matomo/core/CronArchive.php(599): 6 total errors during
this script execution, please investigate and try and fix these errors.
[Query: , CLI mode: 1]
       
  [Exception]                                                              
                     
  6 total errors during this script execution, please investigate and try
and fix these errors.

My takeaway from this is that the errors are intermittent. Most of the job completes successfully, but there are a few requests that fail. I don’t know why they fail though; that’s the problem.

6

Hi,

One quick idea:

Could you try accessing the URLs that are failing in your browser? You might need to add &token_auth= and the token_auth of an admin user for it to work. For me it returns proper JSON like {"idarchives":["385"],"nb_visits":"4"}.

7

It works to access those URLs from my browser (with an auth token). What does that mean? :thinking:

8

I just enabled verbose logging with -vv in the command, so after it runs next, I’ll see if that will give me any additional information.

9

Here’s the verbose error log.

Error log (verbose) 
Your scheduled task "matomo" on site xxx:

php /home/public/stats/matomo/console core:archive
--url=https://www.xxx.com/stats/matomo/ -vv

completed at 2021-08-18 23:03:47 UTC after 3 minutes, 19 seconds and
produced the following output:

INFO [2021-08-18 23:00:33] 54158  ---------------------------
INFO [2021-08-18 23:00:33] 54158  INIT
INFO [2021-08-18 23:00:33] 54158  Running Matomo 4.4.1 as Super User
INFO [2021-08-18 23:00:33] 54158  ---------------------------
INFO [2021-08-18 23:00:33] 54158  NOTES
INFO [2021-08-18 23:00:34] 54158  - Async process archiving supported,
using CliMulti.
INFO [2021-08-18 23:00:34] 54158  - Reports for today will be processed at
most every 900 seconds. You can change this value in Matomo UI > Settings >
General Settings.
INFO [2021-08-18 23:00:34] 54158  - Archiving was last executed without
error 33 min 3s ago
INFO [2021-08-18 23:00:34] 54158  ---------------------------
INFO [2021-08-18 23:00:34] 54158  START
INFO [2021-08-18 23:00:34] 54158  Starting Matomo reports archiving...
DEBUG [2021-08-18 23:00:35] 54158  Applying queued rearchiving...
INFO [2021-08-18 23:00:35] 54158  Start processing archives for site 1.
DEBUG [2021-08-18 23:00:35] 54158  Checking for queued invalidations...
INFO [2021-08-18 23:00:35] 54158    Will invalidate archived reports for
today in site ID = 1's timezone (2021-08-18 00:00:00).
INFO [2021-08-18 23:00:35] 54158    Will invalidate archived reports for
yesterday in site ID = 1's timezone (2021-08-17 00:00:00).

[truncated]

INFO [2021-08-18 23:01:35] 54158  Archived website id 4, period = month,
date = 2021-08-01, segment = '', 362 visits found. Time elapsed: 5.505s
DEBUG [2021-08-18 23:01:35] 54158  No usable archive exists (ts_archived of
existing = 2021-08-18 22:25:13, now = 2021-08-18 23:01:35).
DEBUG [2021-08-18 23:01:35] 54158  Processing invalidation: [idinvalidation
= 39504, idsite = 4, period = year(2021-01-01 - 2021-12-31), name = done,
segment = ].
DEBUG [2021-08-18 23:01:35] 54158  No next invalidated archive.
DEBUG [2021-08-18 23:01:35] 54158  Starting archiving for
?module=API&method=CoreAdminHome.archiveReports&idSite=4&period=year&date=2021-01-01&format=json&trigger=archivephp
DEBUG [2021-08-18 23:01:35] 54158  Running command:
/usr/local/php/7.4.21-nfsn1/bin/php -q  /home/public/stats/matomo/console
climulti:request -q --matomo-domain='www.xxx.com' --superuser
'module=API&method=CoreAdminHome.archiveReports&idSite=4&period=year&date=2021-01-01&format=json&trigger=archivephp&pid=0cbf3ed5a8a831a97dfdd5c3dda37df4a50f0d099665cbb3f1e5e89b4842cfefc3d437a31ef628b99dd139a553c2f48b8abf0&runid=54158'
>
/home/public/stats/matomo/tmp/climulti/0cbf3ed5a8a831a97dfdd5c3dda37df4a50f0d099665cbb3f1e5e89b4842cfefc3d437a31ef628b99dd139a553c2f48b8abf0.output
2>&1 &
ERROR [2021-08-18 23:01:37] 54158  Got invalid response from API request:
?module=API&method=CoreAdminHome.archiveReports&idSite=4&period=year&date=2021-01-01&format=json&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
INFO [2021-08-18 23:01:37] 54158  ''
ERROR [2021-08-18 23:01:37] 54158  Error unserializing the following
response from
?module=API&method=CoreAdminHome.archiveReports&idSite=4&period=year&date=2021-01-01&format=json&trigger=archivephp:
''
DEBUG [2021-08-18 23:01:37] 54158  No next invalidated archive.
INFO [2021-08-18 23:01:37] 54158  Finished archiving for site 4, 4 API
requests, Time elapsed: 18.898s [4 / 11 done]
INFO [2021-08-18 23:01:37] 54158  Start processing archives for site 5.
INFO [2021-08-18 23:01:37] 54158  Finished archiving for site 5, 0 API
requests, Time elapsed: 0.024s [5 / 11 done]
INFO [2021-08-18 23:01:37] 54158  Start processing archives for site 6.
DEBUG [2021-08-18 23:01:37] 54158  Checking for queued invalidations...
INFO [2021-08-18 23:01:37] 54158    Will invalidate archived reports for
today in site ID = 6's timezone (2021-08-18 00:00:00).
INFO [2021-08-18 23:01:37] 54158    Will invalidate archived reports for
yesterday in site ID = 6's timezone (2021-08-17 00:00:00).

[truncated]

INFO [2021-08-18 23:02:09] 54158  Archived website id 7, period = week,
date = 2021-08-16, segment = '', 27 visits found. Time elapsed: 5.985s
DEBUG [2021-08-18 23:02:09] 54158  No usable archive exists (ts_archived of
existing = 2021-08-18 22:25:48, now = 2021-08-18 23:02:09).
DEBUG [2021-08-18 23:02:09] 54158  Processing invalidation: [idinvalidation
= 39511, idsite = 7, period = month(2021-08-01 - 2021-08-31), name = done,
segment = ].
DEBUG [2021-08-18 23:02:09] 54158  Found archive with intersecting period
with others in concurrent batch, skipping until next batch: [idinvalidation
= 39512, idsite = 7, period = year(2021-01-01 - 2021-12-31), name = done,
segment = ]
DEBUG [2021-08-18 23:02:09] 54158  No next invalidated archive.
DEBUG [2021-08-18 23:02:09] 54158  Starting archiving for
?module=API&method=CoreAdminHome.archiveReports&idSite=7&period=month&date=2021-08-01&format=json&trigger=archivephp
DEBUG [2021-08-18 23:02:09] 54158  Running command:
/usr/local/php/7.4.21-nfsn1/bin/php -q  /home/public/stats/matomo/console
climulti:request -q --matomo-domain='www.xxx.com' --superuser
'module=API&method=CoreAdminHome.archiveReports&idSite=7&period=month&date=2021-08-01&format=json&trigger=archivephp&pid=eb1919605d97b7df1cac575a317ee10675b5352187d0830697ac57e795fe6c1e63a886c904047aa7543434dfa5116c9187f80&runid=54158'
>
/home/public/stats/matomo/tmp/climulti/eb1919605d97b7df1cac575a317ee10675b5352187d0830697ac57e795fe6c1e63a886c904047aa7543434dfa5116c9187f80.output
2>&1 &
ERROR [2021-08-18 23:02:13] 54158  Got invalid response from API request:
?module=API&method=CoreAdminHome.archiveReports&idSite=7&period=month&date=2021-08-01&format=json&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
INFO [2021-08-18 23:02:13] 54158  ''
ERROR [2021-08-18 23:02:13] 54158  Error unserializing the following
response from
?module=API&method=CoreAdminHome.archiveReports&idSite=7&period=month&date=2021-08-01&format=json&trigger=archivephp:
''
DEBUG [2021-08-18 23:02:13] 54158  No usable archive exists (ts_archived of
existing = 2021-08-18 22:25:55, now = 2021-08-18 23:02:13).
DEBUG [2021-08-18 23:02:13] 54158  Processing invalidation: [idinvalidation
= 39512, idsite = 7, period = year(2021-01-01 - 2021-12-31), name = done,
segment = ].
DEBUG [2021-08-18 23:02:13] 54158  No next invalidated archive.
DEBUG [2021-08-18 23:02:13] 54158  Starting archiving for
?module=API&method=CoreAdminHome.archiveReports&idSite=7&period=year&date=2021-01-01&format=json&trigger=archivephp
DEBUG [2021-08-18 23:02:13] 54158  Running command:
/usr/local/php/7.4.21-nfsn1/bin/php -q  /home/public/stats/matomo/console
climulti:request -q --matomo-domain='www.xxx.com' --superuser
'module=API&method=CoreAdminHome.archiveReports&idSite=7&period=year&date=2021-01-01&format=json&trigger=archivephp&pid=ba279f9494671f2952930ae9f869739a11f1f8d6142e7c233b03970ba157ef3caefb0a0448cc2930e27da8224801e1bd5a290&runid=54158'
>
/home/public/stats/matomo/tmp/climulti/ba279f9494671f2952930ae9f869739a11f1f8d6142e7c233b03970ba157ef3caefb0a0448cc2930e27da8224801e1bd5a290.output
2>&1 &
INFO [2021-08-18 23:02:20] 54158  Archived website id 7, period = year,
date = 2021-01-01, segment = '', 3741 visits found. Time elapsed: 6.173s
DEBUG [2021-08-18 23:02:20] 54158  No next invalidated archive.
INFO [2021-08-18 23:02:20] 54158  Finished archiving for site 7, 4 API
requests, Time elapsed: 20.676s [7 / 11 done]
INFO [2021-08-18 23:02:21] 54158  Start processing archives for site 8.
DEBUG [2021-08-18 23:02:21] 54158  Checking for queued invalidations...
INFO [2021-08-18 23:02:21] 54158    Will invalidate archived reports for
today in site ID = 8's timezone (2021-08-18 00:00:00).
INFO [2021-08-18 23:02:21] 54158    Will invalidate archived reports for
yesterday in site ID = 8's timezone (2021-08-17 00:00:00).
DEBUG [2021-08-18 23:02:21] 54158    Found usable archive for [idSite = 8,
period = day 2021-08-17,2021-08-17, segment = , plugin = , report = ],
skipping invalidation.

[truncated]

INFO [2021-08-18 23:03:16] 54158  Archived website id 10, period = week,
date = 2021-08-16, segment = '', 8 visits found. Time elapsed: 5.891s
DEBUG [2021-08-18 23:03:16] 54158  No usable archive exists (ts_archived of
existing = 2021-08-18 22:27:06, now = 2021-08-18 23:03:16).
DEBUG [2021-08-18 23:03:16] 54158  Processing invalidation: [idinvalidation
= 39523, idsite = 10, period = month(2021-08-01 - 2021-08-31), name = done,
segment = ].
DEBUG [2021-08-18 23:03:16] 54158  Found archive with intersecting period
with others in concurrent batch, skipping until next batch: [idinvalidation
= 39524, idsite = 10, period = year(2021-01-01 - 2021-12-31), name = done,
segment = ]
DEBUG [2021-08-18 23:03:16] 54158  No next invalidated archive.
DEBUG [2021-08-18 23:03:16] 54158  Starting archiving for
?module=API&method=CoreAdminHome.archiveReports&idSite=10&period=month&date=2021-08-01&format=json&trigger=archivephp
DEBUG [2021-08-18 23:03:17] 54158  Running command:
/usr/local/php/7.4.21-nfsn1/bin/php -q  /home/public/stats/matomo/console
climulti:request -q --matomo-domain='www.xxx.com' --superuser
'module=API&method=CoreAdminHome.archiveReports&idSite=10&period=month&date=2021-08-01&format=json&trigger=archivephp&pid=225b88a65080ab0ff7c5fa6d090a2ad45104f77e08924923c5ba6333d533fd8df88d4f85d5d976df3bad792d63284f5d69e20&runid=54158'
>
/home/public/stats/matomo/tmp/climulti/225b88a65080ab0ff7c5fa6d090a2ad45104f77e08924923c5ba6333d533fd8df88d4f85d5d976df3bad792d63284f5d69e20.output
2>&1 &
INFO [2021-08-18 23:03:23] 54158  Archived website id 10, period = month,
date = 2021-08-01, segment = '', 71 visits found. Time elapsed: 6.070s
DEBUG [2021-08-18 23:03:23] 54158  No usable archive exists (ts_archived of
existing = 2021-08-18 22:27:10, now = 2021-08-18 23:03:23).
DEBUG [2021-08-18 23:03:23] 54158  Processing invalidation: [idinvalidation
= 39524, idsite = 10, period = year(2021-01-01 - 2021-12-31), name = done,
segment = ].
DEBUG [2021-08-18 23:03:23] 54158  No next invalidated archive.
DEBUG [2021-08-18 23:03:23] 54158  Starting archiving for
?module=API&method=CoreAdminHome.archiveReports&idSite=10&period=year&date=2021-01-01&format=json&trigger=archivephp
DEBUG [2021-08-18 23:03:24] 54158  Running command:
/usr/local/php/7.4.21-nfsn1/bin/php -q  /home/public/stats/matomo/console
climulti:request -q --matomo-domain='www.xxx.com' --superuser
'module=API&method=CoreAdminHome.archiveReports&idSite=10&period=year&date=2021-01-01&format=json&trigger=archivephp&pid=9f2993fe52b1d104ad74c319b89b33a237e6b6462afd9298856c5736030ae07df429c6c133b55cad7ab4077f9754c8e497130&runid=54158'
>
/home/public/stats/matomo/tmp/climulti/9f2993fe52b1d104ad74c319b89b33a237e6b6462afd9298856c5736030ae07df429c6c133b55cad7ab4077f9754c8e497130.output
2>&1 &
ERROR [2021-08-18 23:03:28] 54158  Got invalid response from API request:
?module=API&method=CoreAdminHome.archiveReports&idSite=10&period=year&date=2021-01-01&format=json&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
INFO [2021-08-18 23:03:28] 54158  ''
ERROR [2021-08-18 23:03:28] 54158  Error unserializing the following
response from
?module=API&method=CoreAdminHome.archiveReports&idSite=10&period=year&date=2021-01-01&format=json&trigger=archivephp:
''
DEBUG [2021-08-18 23:03:28] 54158  No next invalidated archive.
INFO [2021-08-18 23:03:28] 54158  Finished archiving for site 10, 4 API
requests, Time elapsed: 23.459s [10 / 11 done]
INFO [2021-08-18 23:03:28] 54158  Start processing archives for site 11.
DEBUG [2021-08-18 23:03:28] 54158  Checking for queued invalidations...
INFO [2021-08-18 23:03:28] 54158    Will invalidate archived reports for
today in site ID = 11's timezone (2021-08-18 00:00:00).
INFO [2021-08-18 23:03:28] 54158    Will invalidate archived reports for
yesterday in site ID = 11's timezone (2021-08-17 00:00:00).
DEBUG [2021-08-18 23:03:28] 54158    Found usable archive for [idSite = 11,
period = day 2021-08-17,2021-08-17, segment = , plugin = , report = ],
skipping invalidation.
DEBUG [2021-08-18 23:03:28] 54158  Done invalidating
DEBUG [2021-08-18 23:03:28] 54158  No usable archive exists (ts_archived of
existing = 2021-08-18 22:27:16, now = 2021-08-18 23:03:28).
DEBUG [2021-08-18 23:03:28] 54158  Processing invalidation: [idinvalidation
= 39525, idsite = 11, period = day(2021-08-18 - 2021-08-18), name = done,
segment = ].
DEBUG [2021-08-18 23:03:28] 54158  Found archive with intersecting period
with others in concurrent batch, skipping until next batch: [idinvalidation
= 39526, idsite = 11, period = week(2021-08-16 - 2021-08-22), name = done,
segment = ]
DEBUG [2021-08-18 23:03:28] 54158  Found archive with intersecting period
with others in concurrent batch, skipping until next batch: [idinvalidation
= 39527, idsite = 11, period = month(2021-08-01 - 2021-08-31), name = done,
segment = ]
DEBUG [2021-08-18 23:03:28] 54158  Found archive with intersecting period
with others in concurrent batch, skipping until next batch: [idinvalidation
= 39528, idsite = 11, period = year(2021-01-01 - 2021-12-31), name = done,
segment = ]
DEBUG [2021-08-18 23:03:28] 54158  No next invalidated archive.
DEBUG [2021-08-18 23:03:28] 54158  Starting archiving for
?module=API&method=CoreAdminHome.archiveReports&idSite=11&period=day&date=2021-08-18&format=json&trigger=archivephp
DEBUG [2021-08-18 23:03:29] 54158  Running command:
/usr/local/php/7.4.21-nfsn1/bin/php -q  /home/public/stats/matomo/console
climulti:request -q --matomo-domain='www.xxx.com' --superuser
'module=API&method=CoreAdminHome.archiveReports&idSite=11&period=day&date=2021-08-18&format=json&trigger=archivephp&pid=cc434a7bac4606aab63a3d7fe082b57b7c37ce182818d483cb3ceaea4884abf28a183e79e70611588cb9d9ca530753a218e50&runid=54158'
>
/home/public/stats/matomo/tmp/climulti/cc434a7bac4606aab63a3d7fe082b57b7c37ce182818d483cb3ceaea4884abf28a183e79e70611588cb9d9ca530753a218e50.output
2>&1 &
INFO [2021-08-18 23:03:31] 54158  Archived website id 11, period = day,
date = 2021-08-18, segment = '', 1 visits found. Time elapsed: 2.222s
DEBUG [2021-08-18 23:03:31] 54158  No usable archive exists (ts_archived of
existing = 2021-08-18 22:27:19, now = 2021-08-18 23:03:31).
DEBUG [2021-08-18 23:03:31] 54158  Processing invalidation: [idinvalidation
= 39526, idsite = 11, period = week(2021-08-16 - 2021-08-22), name = done,
segment = ].
DEBUG [2021-08-18 23:03:31] 54158  Found archive with intersecting period
with others in concurrent batch, skipping until next batch: [idinvalidation
= 39527, idsite = 11, period = month(2021-08-01 - 2021-08-31), name = done,
segment = ]
DEBUG [2021-08-18 23:03:31] 54158  Found archive with intersecting period
with others in concurrent batch, skipping until next batch: [idinvalidation
= 39528, idsite = 11, period = year(2021-01-01 - 2021-12-31), name = done,
segment = ]
DEBUG [2021-08-18 23:03:31] 54158  No next invalidated archive.
DEBUG [2021-08-18 23:03:31] 54158  Starting archiving for
?module=API&method=CoreAdminHome.archiveReports&idSite=11&period=week&date=2021-08-16&format=json&trigger=archivephp
DEBUG [2021-08-18 23:03:31] 54158  Running command:
/usr/local/php/7.4.21-nfsn1/bin/php -q  /home/public/stats/matomo/console
climulti:request -q --matomo-domain='www.xxx.com' --superuser
'module=API&method=CoreAdminHome.archiveReports&idSite=11&period=week&date=2021-08-16&format=json&trigger=archivephp&pid=293be55e0886fe3f608309e02000a984ede5d126e98460da59b1246434c980b58d7470d8b6a950e1acfbcfe559beacb6329e0&runid=54158'
>
/home/public/stats/matomo/tmp/climulti/293be55e0886fe3f608309e02000a984ede5d126e98460da59b1246434c980b58d7470d8b6a950e1acfbcfe559beacb6329e0.output
2>&1 &
INFO [2021-08-18 23:03:35] 54158  Archived website id 11, period = week,
date = 2021-08-16, segment = '', 4 visits found. Time elapsed: 4.595s
DEBUG [2021-08-18 23:03:35] 54158  No usable archive exists (ts_archived of
existing = 2021-08-18 22:27:25, now = 2021-08-18 23:03:35).
DEBUG [2021-08-18 23:03:36] 54158  Processing invalidation: [idinvalidation
= 39527, idsite = 11, period = month(2021-08-01 - 2021-08-31), name = done,
segment = ].
DEBUG [2021-08-18 23:03:36] 54158  Found archive with intersecting period
with others in concurrent batch, skipping until next batch: [idinvalidation
= 39528, idsite = 11, period = year(2021-01-01 - 2021-12-31), name = done,
segment = ]
DEBUG [2021-08-18 23:03:36] 54158  No next invalidated archive.
DEBUG [2021-08-18 23:03:36] 54158  Starting archiving for
?module=API&method=CoreAdminHome.archiveReports&idSite=11&period=month&date=2021-08-01&format=json&trigger=archivephp
DEBUG [2021-08-18 23:03:36] 54158  Running command:
/usr/local/php/7.4.21-nfsn1/bin/php -q  /home/public/stats/matomo/console
climulti:request -q --matomo-domain='www.xxx.com' --superuser
'module=API&method=CoreAdminHome.archiveReports&idSite=11&period=month&date=2021-08-01&format=json&trigger=archivephp&pid=134d99df828354c79a7020aaf93a7e31a589578f630515424392dcd2403ab58275067840bec3b6633ee85d701018f73e99230&runid=54158'
>
/home/public/stats/matomo/tmp/climulti/134d99df828354c79a7020aaf93a7e31a589578f630515424392dcd2403ab58275067840bec3b6633ee85d701018f73e99230.output
2>&1 &
INFO [2021-08-18 23:03:40] 54158  Archived website id 11, period = month,
date = 2021-08-01, segment = '', 7 visits found. Time elapsed: 4.810s
DEBUG [2021-08-18 23:03:40] 54158  No usable archive exists (ts_archived of
existing = 2021-08-18 22:27:31, now = 2021-08-18 23:03:40).
DEBUG [2021-08-18 23:03:40] 54158  Processing invalidation: [idinvalidation
= 39528, idsite = 11, period = year(2021-01-01 - 2021-12-31), name = done,
segment = ].
DEBUG [2021-08-18 23:03:40] 54158  No next invalidated archive.
DEBUG [2021-08-18 23:03:40] 54158  Starting archiving for
?module=API&method=CoreAdminHome.archiveReports&idSite=11&period=year&date=2021-01-01&format=json&trigger=archivephp
DEBUG [2021-08-18 23:03:41] 54158  Running command:
/usr/local/php/7.4.21-nfsn1/bin/php -q  /home/public/stats/matomo/console
climulti:request -q --matomo-domain='www.xxx.com' --superuser
'module=API&method=CoreAdminHome.archiveReports&idSite=11&period=year&date=2021-01-01&format=json&trigger=archivephp&pid=e57aa555eb995dc6192711e294cf115a39569bd6b0c9e7b6bf2bf34c9b77fbcbd1b1ab7b39c113b798c6ec6c5cab37cdfa9c0&runid=54158'
>
/home/public/stats/matomo/tmp/climulti/e57aa555eb995dc6192711e294cf115a39569bd6b0c9e7b6bf2bf34c9b77fbcbd1b1ab7b39c113b798c6ec6c5cab37cdfa9c0.output
2>&1 &
INFO [2021-08-18 23:03:46] 54158  Archived website id 11, period = year,
date = 2021-01-01, segment = '', 7 visits found. Time elapsed: 5.619s
DEBUG [2021-08-18 23:03:46] 54158  No next invalidated archive.
INFO [2021-08-18 23:03:46] 54158  Finished archiving for site 11, 4 API
requests, Time elapsed: 17.889s [11 / 11 done]
DEBUG [2021-08-18 23:03:46] 54158  No more sites left to archive, stopping.
INFO [2021-08-18 23:03:46] 54158  Done archiving!
INFO [2021-08-18 23:03:46] 54158  ---------------------------
INFO [2021-08-18 23:03:46] 54158  SUMMARY
INFO [2021-08-18 23:03:46] 54158  Processed 33 archives.
INFO [2021-08-18 23:03:46] 54158  Total API requests: 36
INFO [2021-08-18 23:03:46] 54158  done: 36 req, 191957 ms, 6 errors.
INFO [2021-08-18 23:03:46] 54158  Time elapsed: 191.957s
INFO [2021-08-18 23:03:46] 54158  ---------------------------
INFO [2021-08-18 23:03:46] 54158  SCHEDULED TASKS
DEBUG [2021-08-18 23:03:46] 54158  25 scheduled tasks loaded
INFO [2021-08-18 23:03:46] 54158  Starting Scheduled tasks... 
DEBUG [2021-08-18 23:03:46] 54158  Executing tasks with priority 0:
DEBUG [2021-08-18 23:03:46] 54158  Executing tasks with priority 1:
DEBUG [2021-08-18 23:03:46] 54158  Executing tasks with priority 2:
DEBUG [2021-08-18 23:03:46] 54158  Executing tasks with priority 3:
DEBUG [2021-08-18 23:03:46] 54158  Executing tasks with priority 4:
DEBUG [2021-08-18 23:03:46] 54158  Executing tasks with priority 5:
DEBUG [2021-08-18 23:03:46] 54158  Executing tasks with priority 6:
DEBUG [2021-08-18 23:03:46] 54158  Task
Piwik\Plugins\CustomJsTracker\Tasks.updateTracker is scheduled to run again
for 2021-08-19.
INFO [2021-08-18 23:03:46] 54158  Scheduler: executing task
Piwik\Plugins\CustomJsTracker\Tasks.updateTracker...
INFO [2021-08-18 23:03:46] 54158  Scheduler: finished. Time elapsed: 0.003s
DEBUG [2021-08-18 23:03:46] 54158  Executing tasks with priority 7:
DEBUG [2021-08-18 23:03:46] 54158  Executing tasks with priority 8:
DEBUG [2021-08-18 23:03:46] 54158  Executing tasks with priority 9:
DEBUG [2021-08-18 23:03:46] 54158  Task
Piwik\Plugins\PrivacyManager\Tasks.deleteLogData is scheduled to run again
for 2021-08-19.
INFO [2021-08-18 23:03:46] 54158  Scheduler: executing task
Piwik\Plugins\PrivacyManager\Tasks.deleteLogData...
INFO [2021-08-18 23:03:46] 54158  Scheduler: finished. Time elapsed: 0.000s
DEBUG [2021-08-18 23:03:46] 54158  Task
Piwik\Plugins\PrivacyManager\Tasks.anonymizePastData is scheduled to run
again for 2021-08-19.
INFO [2021-08-18 23:03:46] 54158  Scheduler: executing task
Piwik\Plugins\PrivacyManager\Tasks.anonymizePastData...
INFO [2021-08-18 23:03:46] 54158  Scheduler: finished. Time elapsed: 0.002s
DEBUG [2021-08-18 23:03:46] 54158  Executing tasks with priority 10:
DEBUG [2021-08-18 23:03:46] 54158  Executing tasks with priority 11:
DEBUG [2021-08-18 23:03:46] 54158  Executing tasks with priority 12:
INFO [2021-08-18 23:03:46] 54158  done
INFO [2021-08-18 23:03:46] 54158  ---------------------------
INFO [2021-08-18 23:03:46] 54158  ---------------------------
INFO [2021-08-18 23:03:46] 54158  SUMMARY OF ERRORS
INFO [2021-08-18 23:03:46] 54158  Error: Got invalid response from API
request:
?module=API&method=CoreAdminHome.archiveReports&idSite=4&period=year&date=2021-01-01&format=json&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
INFO [2021-08-18 23:03:46] 54158  Error: Error unserializing the following
response from
?module=API&method=CoreAdminHome.archiveReports&idSite=4&period=year&date=2021-01-01&format=json&trigger=archivephp:
''
INFO [2021-08-18 23:03:46] 54158  Error: Got invalid response from API
request:
?module=API&method=CoreAdminHome.archiveReports&idSite=7&period=month&date=2021-08-01&format=json&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
INFO [2021-08-18 23:03:46] 54158  Error: Error unserializing the following
response from
?module=API&method=CoreAdminHome.archiveReports&idSite=7&period=month&date=2021-08-01&format=json&trigger=archivephp:
''
INFO [2021-08-18 23:03:46] 54158  Error: Got invalid response from API
request:
?module=API&method=CoreAdminHome.archiveReports&idSite=10&period=year&date=2021-01-01&format=json&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
INFO [2021-08-18 23:03:46] 54158  Error: Error unserializing the following
response from
?module=API&method=CoreAdminHome.archiveReports&idSite=10&period=year&date=2021-01-01&format=json&trigger=archivephp:
''
ERROR [2021-08-18 23:03:46] 54158  6 total errors during this script
execution, please investigate and try and fix these errors.
ERROR [2021-08-18 23:03:46] 54158  Uncaught exception:
/home/public/stats/matomo/core/CronArchive.php(599): 6 total errors during
this script execution, please investigate and try and fix these errors.
[Query: , CLI mode: 1]
DEBUG [2021-08-18 23:03:47] 54158  Loaded plugins: CorePluginsAdmin,
CoreAdminHome, CoreHome, WebsiteMeasurable, IntranetMeasurable,
Diagnostics, CoreVisualizations, Proxy, API, Widgetize, Transitions,
LanguagesManager, Actions, Dashboard, MultiSites, Referrers, UserLanguage,
DevicesDetection, Goals, Ecommerce, SEO, Events, UserCountry, GeoIp2,
VisitsSummary, VisitFrequency, VisitTime, VisitorInterest, RssWidget,
Feedback, Monolog, Login, TwoFactorAuth, UsersManager, SitesManager,
Installation, CoreUpdater, CoreConsole, ScheduledReports, UserCountryMap,
Live, PrivacyManager, ImageGraph, Annotations, MobileMessaging, Overlay,
SegmentEditor, Insights, Morpheus, Contents, BulkTracking, Resolution,
DevicePlugins, Heartbeat, Intl, Marketplace, ProfessionalServices, UserId,
CustomJsTracker, Tour, PagePerformance, CustomDimensions

  [Exception]                                                              
                     
  6 total errors during this script execution, please investigate and try
and fix these errors.  
Exception trace:
 () at /home/public/stats/matomo/core/CronArchive.php:599
 Piwik\CronArchive->logFatalError() at
/home/public/stats/matomo/core/CronArchive.php:592
 Piwik\CronArchive->end() at
/home/public/stats/matomo/core/CronArchive.php:265
 Piwik\CronArchive->Piwik\{closure}() at
/home/public/stats/matomo/core/Access.php:664
 Piwik\Access::doAsSuperUser() at
/home/public/stats/matomo/core/CronArchive.php:269
 Piwik\CronArchive->main() at
/home/public/stats/matomo/plugins/CoreConsole/Commands/CoreArchiver.php:32
 Piwik\Plugins\CoreConsole\Commands\CoreArchiver->execute() at
/home/public/stats/matomo/vendor/symfony/console/Symfony/Component/Console/Command/Command.php:257
 Symfony\Component\Console\Command\Command->run() at
/home/public/stats/matomo/vendor/symfony/console/Symfony/Component/Console/Application.php:874
 Symfony\Component\Console\Application->doRunCommand() at
/home/public/stats/matomo/vendor/symfony/console/Symfony/Component/Console/Application.php:195
 Symfony\Component\Console\Application->doRun() at n/a:n/a
 call_user_func() at /home/public/stats/matomo/core/Console.php:130
 Piwik\Console->Piwik\{closure}() at
/home/public/stats/matomo/core/Access.php:673
 Piwik\Access::doAsSuperUser() at
/home/public/stats/matomo/core/Console.php:131
 Piwik\Console->doRunImpl() at
/home/public/stats/matomo/core/Console.php:82
 Piwik\Console->doRun() at
/home/public/stats/matomo/vendor/symfony/console/Symfony/Component/Console/Application.php:126
 Symfony\Component\Console\Application->run() at
/home/public/stats/matomo/console:32

Here’s the summary at the end. Is this any help in figuring out what the issue may be?

6 total errors during this script execution, please investigate and try
and fix these errors.  
Exception trace:
 () at /home/public/stats/matomo/core/CronArchive.php:599
 Piwik\CronArchive->logFatalError() at
/home/public/stats/matomo/core/CronArchive.php:592
 Piwik\CronArchive->end() at
/home/public/stats/matomo/core/CronArchive.php:265
 Piwik\CronArchive->Piwik\{closure}() at
/home/public/stats/matomo/core/Access.php:664
 Piwik\Access::doAsSuperUser() at
/home/public/stats/matomo/core/CronArchive.php:269
 Piwik\CronArchive->main() at
/home/public/stats/matomo/plugins/CoreConsole/Commands/CoreArchiver.php:32
 Piwik\Plugins\CoreConsole\Commands\CoreArchiver->execute() at
/home/public/stats/matomo/vendor/symfony/console/Symfony/Component/Console/Command/Command.php:257
 Symfony\Component\Console\Command\Command->run() at
/home/public/stats/matomo/vendor/symfony/console/Symfony/Component/Console/Application.php:874
 Symfony\Component\Console\Application->doRunCommand() at
/home/public/stats/matomo/vendor/symfony/console/Symfony/Component/Console/Application.php:195
 Symfony\Component\Console\Application->doRun() at n/a:n/a
 call_user_func() at /home/public/stats/matomo/core/Console.php:130
 Piwik\Console->Piwik\{closure}() at
/home/public/stats/matomo/core/Access.php:673
 Piwik\Access::doAsSuperUser() at
/home/public/stats/matomo/core/Console.php:131
 Piwik\Console->doRunImpl() at
/home/public/stats/matomo/core/Console.php:82
 Piwik\Console->doRun() at
/home/public/stats/matomo/vendor/symfony/console/Symfony/Component/Console/Application.php:126
 Symfony\Component\Console\Application->run() at
/home/public/stats/matomo/console:32
10

My inbox is still filling up with emails every hour from Matomo. :frowning: @matthieu any ideas what I can do next to find out what Matomo’s problem is?

11

One month later I have 568 emails in my inbox, and I’m no closer to knowing what the problem is, or how I can fix it. Any ideas? Anyone? I’m happy to provide additional logs, debugs, whatever; I just need to get this fixed!

12

As I was talking with a friend about this issue, I did a little sleuthing and discovered that all of these errors started occurring the same day that I upgraded to Matomo version: 4.4.1. Now I’d like to downgrade to the previous version, (4.3.1, I guess) to test whether or not the errors will go away. I checked through the release notes of both 4.4.1 and 4.3.1 and didn’t see any major DB structure changes between them, so am I correct in assuming that I can basically just overwrite my current installation with the older version? (with backups beforehand, of course).

13

You are right that there was no database upgrades between the two releases:

So in theory downgrading should indeed just be overwriting the files with the ones from https://builds.matomo.org/

The only thing is that you might need to update the database version field:

UPDATE matomo_option set option_value = '4.3.1' where option_value = '4.4.1';

But I won’t promise anything and recommend backups before.

1 Like
14

Thanks for the quick reply; you saved me from having to ask what to do when Matomo throws an error that it had already been upgraded to 4.4.1… :slight_smile: Everything seems to be working OK so far. Matomo reports that it’s now running 4.3.1. I’ll have to wait for the scheduled cron job to run in order to find out whether the problem is fixed.

15

Well, downgrading to 4.3.1 stopped the flood of error messages! Now the question is “what caused the newer version to start throwing errors?” I don’t know, but I hope someone can figure it out! I checked out CronArchive.php on Github, and the only thing that seems to have changed between versions is the removal of “Common::” from the file. But I have no idea whether that’s relevant to my problem or not.

16

As I mentioned before the error isn’t in CronArchive.php, but instead CronArchive.php makes a request to the Matomo API, but doesn’t get a response and fails.
So without knowing how this API request fails, I have no idea how to find out what was going wrong.

This is the list of changes between the versions, if it helps you in any way: https://github.com/matomo-org/matomo/compare/4.3.1...4.4.1

17

Oh, right… :slight_smile: Thanks for the diff. I looked through it, but didn’t see anything that caught my attention.
So what’s next? Someone from my webhost made this suggestion, but I’m not really sure how to go about it. :confused:

the next step would probably be to start injecting your own logging into the Matomo files around the functions identified by the stack traces, looking for values that don’t seem right (particularly if you can make requests to the same calls that succeed, you could do something like logging all the function arguments and then diffing between the working and failing calls). Keep a backup of any modified files, obviously.

18

@Lukas I see that Matomo 4.5.0 has been released. I’d like to upgrade to see if it fixes my problem, but it seems that there is a database change.

ALTER TABLE 'matomo_session' CHANGE 'data' 'data' MEDIUMTEXT;

Will that be an issue if for some reason I need to downgrade again?

19

Update: I did upgrade to Matomo 4.5.0, but the errors keep coming. :confused:

20

Just a note that this issue was finally resolved in Github issue #18090.

1 Like