Problème d'archivage des données

Anideus · August 3, 2023, 10:27am

Bonjour à tous,
Je viens appeler à l’aide, car je m’arrache les cheveux sur un problème.
J’utilise Matomo sur WordPress depuis pas mal de temps, et je n’ai jamais eu aucun soucis.
Mais depuis 2 semaines, je n’ai plus aucune donnée qui remonte. Rien.
Seul fonctionne le suivi en temps réel, mais plus aucun rapport.
En désespoir de cause, j’ai tout désinstallé et réinstallé le plugin, mais toujours même problème.
Alors, si quelqu’un peut aider un noob comme moi, merci sincèrement.

Ci-dessous le rapport d’erreur, si ça peut aider.
Je spécifie être chez OVH en hébergement performance donc mutualisé.

				  # Errors

* Error Dernière exécution d'archivage réussie: error  (L'archivage ne s'est pas encore exécuté avec succès )

Matomo

Version de l’extension Matomo: 4.15.0
Config existe et est accessible en écriture.: Oui (“$abs_path/wp-content/uploads/matomo/config/config.ini.php” )
JS Tracker existe et est accessible en écriture.: Oui (“$abs_path/wp-content/uploads/matomo/matomo.js” )
Répertoires de l’extension: Yes ([{“pluginsPathAbsolute”:“$abs_path/wp-content/plugins/matomo/plugins”,“webrootDirRelativeToMatomo”:“…/”}])
Répertoire temporaire accessible en écriture: Yes ($abs_path/wp-content/cache/matomo)
Version de Matomo: 4.15.0
idSite du site web Matomo: 1
Version installée de Matomo: 4.15.0 (Install date: 2023-08-02 16:38:04)
Upgrades outstanding: No
Upgrade in progress: No

Endpoints

Matomo JavaScript Tracker URL: ($site_url/wp-content/uploads/matomo/matomo.js)
Matomo JavaScript Tracker - WP Rest API: ($site_url/wp-json/matomo/v1/hit/)
Matomo HTTP Tracking API: ($site_url/wp-content/plugins/matomo/app/matomo.php)
Matomo HTTP Tracking API - WP Rest API: ($site_url/wp-json/matomo/v1/hit/)

Crons

Heure du serveur: 2023-08-03 10:23:44
Heure du site web: 2023-08-03 12:23:44 (Les dates ci-dessous sont affichées dans le fuseau horaire du site web)
Sync users & sites: Next run: 2023-08-04 11:32:30 (23 heures 8 min) ( Last started: 2023-08-03 11:32:46 (-50 min 58s). Last ended: 2023-08-03 11:32:46 (-50 min 58s). Interval: daily)
Archive: Next run: 2023-08-03 12:32:30 (8 min 46s) ( Last started: 2023-08-03 10:33:33 (-1 heures 50 min). Last ended: 2023-08-03 10:33:39 (-1 heures 50 min). Interval: hourly)
Update GeoIP DB: Next run: 2023-08-26 11:32:30 (22 jours 23 heures) ( Last started: 2023-08-02 16:38:40 (-19 heures 45 min). Last ended: 2023-08-02 16:38:44 (-19 heures 45 min). Interval: matomo_monthly)

Contrôles obligatoires

Version PHP >= 7.2.5: ok
PDO extension: ok
PDO\MYSQL extension: ok
MYSQLI extension: ok
Autres extensions requises: ok
Fonctions requises: ok
Configuration PHP requise (php.ini): ok
Répertoires avec les droits d’accès en écriture: ok
Répertoires avec accès en écriture pour Gestionnaire de balises: ok

Contrôles facultatifs

Binaire PHP 64 bits: ok
État du traqueur: ok
Limite mémoire: ok
Fuseau horaire: ok
Ouvrir l’URL: ok
GD > 2.x + FreeType (graphics): ok
Autres extensions: ok
Autres fonctions: ok
Warning Système de fichiers: warning (Votre serveur utilise un système de fichier NFS. Cela signifie que Matomo va être très lent lors de l’utilisation des sessions basées sur des fichiers. )
Error Dernière exécution d’archivage réussie: error (L’archivage ne s’est pas encore exécuté avec succès )
Capacités de la base de données: ok
Warning Taille maximale des paquets: warning (Il est important de configurer une taille ‘max_allowed_packet’ dans votre base de données MySQL d’au moins 64MB. 32MB configuré en ce moment. )
Géolocalisation: ok
Mettre à jour via HTTPS: ok
Supports Async Archiving: Yes
Location provider ID: geoip2php
Location provider available: Yes
Location provider working: Yes
Had visit in last 5 days: Yes
Matomo URL: Yes ($site_url/wp-content/plugins/matomo/app/)

Matomo Settings

Track mode: default
Track codeposition: footer
Track api endpoint: restapi
Track js endpoint: default
Version history: 4.15.0
Core version: 4.15.0
Last tracking settings update: 1691043735
Last settings update: 1691043735
Track content: all
Track ecommerce: No
Track search: Yes
Show get started page: 0

Logs

Warning archive_main: 2023-08-03 09:33:37 (10 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:306; class-wp-hook.php:332; plugin.php:565; wp-cron.php:188;)
Warning archive_errors: 2023-08-03 09:33:37 (‘Got invalid response from API request: ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=day&date=2023-08-03&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-03&format=json&trigger=archivephp: ''’ ‘Got invalid response from API request: ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=day&date=2023-08-02&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-02&format=json&trigger=archivephp: ''’ ‘Got invalid response from API request: ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=month&date=2023-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’ ‘Error unserializing the following response from ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=month&date=2023-08-01&format=json&trigger=archivephp: ''’ ‘Got invalid response from API request: ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=week&date=2023-07-31&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=week&date=2023-07-31&format=json&trigger=archivephp: ''’ ‘Got invalid response from API request: ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=year&date=2023-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’ ‘Error unserializing the following response from ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=year&date=2023-01-01&format=json&trigger=archivephp: ''’ ‘10 total errors during this script execution, please investigate and try and fix these errors.’ => ScheduledTasks.php:345; class-wp-hook.php:306; class-wp-hook.php:332; plugin.php:565; wp-cron.php:188;)
Warning archive_main: 2023-08-03 09:56:45 (10 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:306; class-wp-hook.php:332; plugin.php:565; wp-cron.php:188;)
Warning archive_errors: 2023-08-03 09:56:45 (‘Got invalid response from API request: ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=day&date=2023-08-03&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-03&format=json&trigger=archivephp: ''’ ‘Got invalid response from API request: ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=day&date=2023-08-02&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-02&format=json&trigger=archivephp: ''’ ‘Got invalid response from API request: ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=month&date=2023-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’ ‘Error unserializing the following response from ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=month&date=2023-08-01&format=json&trigger=archivephp: ''’ ‘Got invalid response from API request: ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=week&date=2023-07-31&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=week&date=2023-07-31&format=json&trigger=archivephp: ''’ ‘Got invalid response from API request: ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=year&date=2023-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’ ‘Error unserializing the following response from ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=year&date=2023-01-01&format=json&trigger=archivephp: ''’ ‘10 total errors during this script execution, please investigate and try and fix these errors.’ => ScheduledTasks.php:345; class-wp-hook.php:306; class-wp-hook.php:332; plugin.php:565; wp-cron.php:188;)
Warning archive_main: 2023-08-03 10:33:39 (10 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:306; class-wp-hook.php:332; plugin.php:565; wp-cron.php:188;)
Warning archive_errors: 2023-08-03 10:33:39 (‘Got invalid response from API request: ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=day&date=2023-08-03&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-03&format=json&trigger=archivephp: ''’ ‘Got invalid response from API request: ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=day&date=2023-08-02&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-02&format=json&trigger=archivephp: ''’ ‘Got invalid response from API request: ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=month&date=2023-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’ ‘Error unserializing the following response from ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=month&date=2023-08-01&format=json&trigger=archivephp: ''’ ‘Got invalid response from API request: ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=week&date=2023-07-31&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=week&date=2023-07-31&format=json&trigger=archivephp: ''’ ‘Got invalid response from API request: ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=year&date=2023-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’ ‘Error unserializing the following response from ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=year&date=2023-01-01&format=json&trigger=archivephp: ''’ ‘10 total errors during this script execution, please investigate and try and fix these errors.’ => ScheduledTasks.php:345; class-wp-hook.php:306; class-wp-hook.php:332; plugin.php:565; wp-cron.php:188;)

WordPress

Home URL: $site_url
Site URL: $site_url
WordPress Version: 6.2.2
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: Yes
CONCATENATE_SCRIPTS: No
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: /%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

Akismet Anti-Spam: Spam Protection: 5.2
Better Recent Comments: 1.1.7
Breadcrumb NavXT: 7.2.0
Coming Soon Page, Maintenance Mode, Landing Pages & WordPress Website Builder by SeedProd: 6.15.13.1
Contact Form 7: 5.7.7
Contact Form 7 Image Captcha: 3.3.5
CookieYes | GDPR Cookie Consent: 3.1.1
Custom Fonts: 2.0.2
Elementor: 3.15.1
FileBird Lite: 5.5
GTM4WP: 1.16.2
Happy Elementor Addons: 3.8.5
HootKit: 2.0.13
Ko-fi Button: 1.3.4
Matomo Analytics - Ethical Stats. Powerful Insights.: 4.15.0
Max Mega Menu: 3.2.2
Menu Icons: 0.13.6
My Simple Space: 1.2.9
Photo Gallery: 1.8.17
Post Views Counter: 1.3.13
Redirection: 5.3.10
Royal Elementor Addons: 1.3.71
Sidebar Manager: 1.1.8
Site Kit by Google: 1.106.0
Social Feed Gallery: 4.1.6
UpdraftPlus - Backup/Restore: 2.23.7.0
W3 Total Cache: 2.3.3 (Réseau activé)
Wordfence Security: 7.10.3 (Réseau activé)
WP Crontrol: 1.15.3
WP phpMyAdmin: 5.2.1.02
WPS Cleaner: 1.6.8
WPS Hide Login: 1.9.8
Wp Social: 2.2.3
Yoast SEO: 20.12
Active Plugins: 34 (akismet better-recent-comments breadcrumb-navxt coming-soon contact-form-7-image-captcha contact-form-7 cookie-law-info custom-fonts duracelltomi-google-tag-manager elementor filebird google-site-kit happy-elementor-addons hootkit insta-gallery ko-fi-button matomo megamenu menu-icons my-simple-space photo-gallery post-views-counter redirection royal-elementor-addons sidebar-manager updraftplus w3-total-cache wordfence wordpress-seo wp-crontrol wp-phpmyadmin-extension wp-social wps-cleaner wps-hide-login)
Theme: magazine-news-byte-premium (magazine-news-byte-premium-child)

Server

Server Info: Apache
Apache AddHandler support: Pris en charge
PHP OS: Linux
PHP Version: 8.0.28
PHP SAPI: fpm-fcgi
PHP Binary Name: /images/stable64/usr/local/php8.0/sbin/php-fpm
Extension PHP Maxmind DB: Non chargé
PHP Error Reporting: After bootstrap: 4437
PHP Found Binary: /usr/local/php8.0/bin/php -q
Timezone: UTC
WP timezone: Europe/Paris
Locale: fr_FR
User Locale: fr_FR
Memory Limit: 512M (Au moins 128MB recommandé. En fonction de votre trafic, 256MB ou plus peuvent être nécessaires.)
WP Memory Limit: 40M
WP Max Memory Limit: 512M
Timezone version: 2022.6
Time: 1691058226
Max Execution Time: 165
Max Post Size: 130M
Max Upload Size: 134217728
Max Input Vars: 16000
Disabled PHP functions: Yes (_dyuweyrj4,_dyuweyrj4r,dl)
zlib.output_compression is off: Yes
Curl Version: 7.64.0, OpenSSL/1.1.1n
Suhosin installed: No

PHP cli

Version de PHP cli: 8.0.28
Prise en charge de MySQLi: ok

Database

MySQL Version: 5.7.42
Mysqli Connect: Yes
Force MySQL over Mysqli: No
DB Prefix: wor2738_
DB CHARSET: utf8
DB COLLATE:
SHOW ERRORS: No
SUPPRESS ERRORS: No
Uses Socket: No
Uses IPv6: No
Matomo tables found: 75
DB tables exist: Yes
Matomo users found: 2
Matomo sites found: 1
Permissions obligatoires: OK

Browser

Browser: (Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36)
Language: fr-fr,fr,en-us,en

heurteph-ei · August 10, 2023, 9:18am

Bonjour

Je ne suis pas expert dans Matomo pour WordPress, mais je jette quand même un coup d’oeil…

Piste 1

L’arrêt des traces est-il consécutif à la montée de version 4.15.0 ?

Piste 2

Peut-être une piste à étudier ?

Piste 3

L’erreur remontée pourrait probablement être la raison du problème. J’ai moi aussi rencontré un tel problème, et comme je ne pouvais pas modifier le fichier php.ini j’ai ajouté au fichiers PHP incriminé (/core/CronArchive/QueueConsumer.php, après la déclaration du namespace, et avant les déclarations use) la directive :

  ini_set('memory_limit', '256M');

Anideus · August 10, 2023, 9:43am

Bonjour,

Merci pour votre réponse !
De mémoire, cela a commencé à ne plus fonctionner d’un coup, le 19 juillet. Donc environ deux semaines après la sortie, je dirais.

Pour la taille “max_allowed_packet”, étant en mutualisé sur OVH, je ne peux rien modifier là-dedans, OVH m’ayant clairement fait un “no way”
Idem pour le fichier PHP.ini auquel je n’ai pas accès.
La seule solution selon OVH serait de passer sur VPS, mais n’y connaissant pas grand-chose je préfère éviter d’avoir à tout gérer seul.
Merci de votre aide, en tout cas.