Closed paulrouf closed 1 year ago
@paulrouf Thanks for creating this report. Based on the error message it seems that your archiving isn't running for some reason. You may need to check if you archiving cron is still running correctly. Maybe increasing the memory limit might help. Otherwise there are a couple of FAQ in our knowledge base like https://matomo.org/faq/on-premise/how-to-set-up-auto-archiving-of-your-reports/ that might help to check if it set up correctly. If you aren't able to get it running, maybe try to get some help on our forums. We aren't able to provide this type of support on GitHub, as we are using this issue tracker for bug reports and feature requests only.
No data showing since many month. Here is the system report (only partial as too long to paste here) Anyone can help ? thanks!!
Matomo
Endpoints
Crons
Contrôles obligatoires
Contrôles facultatifs
Matomo Settings
Logs
Warning archive_main: 2023-08-30 12:19:54 (516 total errors during this script execution, please investigate and try and fix these errors. => CronArchive.php:631; CronArchive.php:624; CronArchive.php:278; Access.php:670; CronArchive.php:282; ScheduledTasks.php:332; class-wp-hook.php:308; class-wp-hook.php:334; plugin.php:565; wp-cron.php:191;)
Warning archive_errors: 2023-08-30 12:19:54 ('Got invalid response from API request: ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=day&date=2023-08-30&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 unserializing the following response from ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=day&date=2023-08-30&format=json&trigger=archivephp: \'\'' 'Got invalid response from API request: ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=day&date=2023-08-29&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 |
WordPress
Home URL: $site_url
Site URL: $site_url
WordPress Version: 6.3.1
Number of blogs: 1
Multisite Enabled: No
Network Enabled: No
WP_DEBUG: No
WP_DEBUG_DISPLAY: Yes
WP_DEBUG_LOG: No
DISABLE_WP_CRON: -
FORCE_SSL_ADMIN: Yes
WP_CACHE: No
CONCATENATE_SCRIPTS: -
COMPRESS_SCRIPTS: -
COMPRESS_CSS: -
ENFORCE_GZIP: -
WP_LOCAL_DEV: -
WP_CONTENT_URL: $site_url/wp-content
WP_CONTENT_DIR: $abs_path/wp-content
UPLOADS: -
BLOGUPLOADDIR: -
DIEONDBERROR: -
WPLANG: -
ALTERNATE_WP_CRON: -
WP_CRON_LOCK_TIMEOUT: 60
WP_DISABLE_FATAL_ERROR_HANDLER: -
MATOMO_SUPPORT_ASYNC_ARCHIVING: -
MATOMO_TRIGGER_BROWSER_ARCHIVING: -
MATOMO_ENABLE_TAG_MANAGER: -
MATOMO_SUPPRESS_DB_ERRORS: -
MATOMO_ENABLE_AUTO_UPGRADE: -
MATOMO_DEBUG: -
MATOMO_SAFE_MODE: -
MATOMO_GLOBAL_UPLOAD_DIR: -
MATOMO_LOGIN_REDIRECT: -
Permalink Structure: /%category%/%postname%
Possibly uses symlink: No
Upload base url: $site_url/wp-content/uploads
Upload base dir: $abs_path/wp-content/uploads
Upload url: $site_url/wp-content/uploads/2023/08
Custom upload_path:
Custom upload_url_path:
Compatible content directory: Yes
WordPress Plugins
Server
PHP cli
Database
Browser