“Archive” process can’t work

adding the full diag report

# Matomo

* Version de l’extension Matomo: 4.10.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.10.0
* idSite du site web Matomo: 1
* Version installée de Matomo: 4.10.0 (Install date: 2022-08-02 14:58:34)
* 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: 2022-08-04 15:16:43
* Heure du site web: 2022-08-04 16:16:43 (Les dates ci-dessous sont affichées dans le fuseau horaire du site web)
* Sync users & sites: Next run: 2022-08-05 14:34:00 (22 hours 17 min) ( Last started: 2022-08-04 15:25:48 (-50 min 55s). Last ended: 2022-08-04 15:25:48 (-50 min 55s). Interval: daily)
* Archive: Next run: 2022-08-04 16:34:00 (17 min 17s) ( Last started: 2022-08-04 15:34:06 (-42 min 37s). Last ended: 2022-08-04 15:34:14 (-42 min 29s). Interval: hourly)
* Update GeoIP DB: Next run: 2022-09-03 14:34:00 (29 days 22 hours) ( Last started: 2022-08-04 14:34:14 (-1 hours 42 min). Last ended: 2022-08-04 14:34:19 (-1 hours 42 min). Interval: matomo_monthly)

## Contrôles obligatoires

* PHP version >= : ok 
* PDO extension: ok 
* PDO\MYSQL extension: ok 
* MYSQLI extension: ok 
* Other required extensions: ok 
* Required functions: ok 
* Required PHP configuration (php.ini): ok 
* Directories with write access: ok 
* Directories with write access for Tag Manager: ok 

## Contrôles facultatifs

* 64-bit PHP Binary: ok 
* Tracker status: ok 
* Memory limit: ok 
* Time zone: ok 
* Open URL: ok 
* PageSpeed is turned off: ok 
* GD > 2.x + FreeType (graphics): ok 
* Other extensions: ok 
* Other functions: ok 
* Filesystem: ok 
* Warning Last Successful Archiving Completion: warning  (Archiving last ran successfully on Tuesday, August 2, 2022 16:58:52 which is 1 days 22:17:50 ago )
* Database abilities: ok 
* Warning Max Packet Size: warning  (It is recommended to configure a 'max_allowed_packet' size in your MySQL database of at least 64MB. Configured is currently 32MB. )
* Geolocation: ok 
* Update over HTTPS: ok 
* Supports Async Archiving: Yes
* Location provider ID: geoip2php
* Location provider available: Yes
* Location provider working: Yes
* Warning Proxy header: HTTP_X_FORWARDED_FOR (A proxy header is set which means you maybe need to configure a proxy header in the Advanced settings to make location reporting work. If the location in your reports is detected correctly, you can ignore this warning. Learn more: https://matomo.org/faq/wordpress/how-do-i-fix-the-proxy-header-warning-in-the-matomo-for-wordpress-system-report/)
* 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: default
* Track js endpoint: default
* Version history: 4.10.0
* Core version: 4.10.0
* Last tracking settings update: 1659620449
* Last settings update: 1659620449
* Show get started page: 0
* Track ecommerce: No
* Track search: Yes
* Track 404: Yes
* Track crossdomain linking: Yes
* Track feed: Yes
* Track feed addcampaign: Yes
* Track heartbeat: 15
* Track jserrors: Yes
* Delete all data uninstall: No
* Mail history: 2022-08-04 02:02:15, 2022-08-02 21:00:44

## Logs

* Warning archive_main: 2022-08-04 15:34:14 (12 total errors during this script execution, please investigate and try and fix these errors. => CronArchive.php:625; CronArchive.php:618; CronArchive.php:280; Access.php:670; CronArchive.php:284; ScheduledTasks.php:332; class-wp-hook.php:305; class-wp-hook.php:331; plugin.php:524; wp-cron.php:138;)
* Warning archive_errors: 2022-08-04 15:34:14 ('Got invalid response from API request: ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=day&date=2022-08-04&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=2022-08-04&format=json&trigger=archivephp: \'\'' 'Got invalid response from API request: ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=day&date=2022-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=2022-08-03&format=json&trigger=archivephp: \'\'' 'Got invalid response from API request: ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=day&date=2022-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=2022-08-02&format=json&trigger=archivephp: \'\'' 'Got invalid response from API request: ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=week&date=2022-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=week&date=2022-08-01&format=json&trigger=archivephp: \'\'' 'Got invalid response from API request: ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=month&date=2022-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=2022-08-01&format=json&trigger=archivephp: \'\'' 'Got invalid response from API request: ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=year&date=2022-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=2022-01-01&format=json&trigger=archivephp: \'\'' '12 total errors during this script execution, please investigate and try and fix these errors.' => ScheduledTasks.php:345; class-wp-hook.php:305; class-wp-hook.php:331; plugin.php:524; wp-cron.php:138;)
* Warning archive_main: 2022-08-04 16:04:36 (12 total errors during this script execution, please investigate and try and fix these errors. => CronArchive.php:625; CronArchive.php:618; CronArchive.php:280; Access.php:661; CronArchive.php:284; ScheduledTasks.php:332; SystemReport.php:157; SystemReport.php:222; class-wp-hook.php:307; class-wp-hook.php:331; plugin.php:476; admin.php:259;)
* Warning archive_errors: 2022-08-04 16:04:36 ('Got invalid response from API request: ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=day&date=2022-08-04&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=2022-08-04&format=json&trigger=archivephp: \'\'' 'Got invalid response from API request: ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=day&date=2022-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=2022-08-03&format=json&trigger=archivephp: \'\'' 'Got invalid response from API request: ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=day&date=2022-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=2022-08-02&format=json&trigger=archivephp: \'\'' 'Got invalid response from API request: ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=week&date=2022-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=week&date=2022-08-01&format=json&trigger=archivephp: \'\'' 'Got invalid response from API request: ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=month&date=2022-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=2022-08-01&format=json&trigger=archivephp: \'\'' 'Got invalid response from API request: ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=year&date=2022-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=2022-01-01&format=json&trigger=archivephp: \'\'' '12 total errors during this script execution, please investigate and try and fix these errors.' => ScheduledTasks.php:345; SystemReport.php:157; SystemReport.php:222; class-wp-hook.php:307; class-wp-hook.php:331; plugin.php:476; admin.php:259;)
* Warning archive_main: 2022-08-04 16:13:55 (12 total errors during this script execution, please investigate and try and fix these errors. => CronArchive.php:625; CronArchive.php:618; CronArchive.php:280; Access.php:661; CronArchive.php:284; ScheduledTasks.php:332; SystemReport.php:157; SystemReport.php:222; class-wp-hook.php:307; class-wp-hook.php:331; plugin.php:476; admin.php:259;)
* Warning archive_errors: 2022-08-04 16:13:55 ('Got invalid response from API request: ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=day&date=2022-08-04&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=2022-08-04&format=json&trigger=archivephp: \'\'' 'Got invalid response from API request: ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=day&date=2022-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=2022-08-03&format=json&trigger=archivephp: \'\'' 'Got invalid response from API request: ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=day&date=2022-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=2022-08-02&format=json&trigger=archivephp: \'\'' 'Got invalid response from API request: ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=week&date=2022-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=week&date=2022-08-01&format=json&trigger=archivephp: \'\'' 'Got invalid response from API request: ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=month&date=2022-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=2022-08-01&format=json&trigger=archivephp: \'\'' 'Got invalid response from API request: ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=year&date=2022-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=2022-01-01&format=json&trigger=archivephp: \'\'' '12 total errors during this script execution, please investigate and try and fix these errors.' => ScheduledTasks.php:345; SystemReport.php:157; SystemReport.php:222; class-wp-hook.php:307; class-wp-hook.php:331; plugin.php:476; admin.php:259;)

# WordPress

* Home URL: $site_url
* Site URL: $site_url
* WordPress Version: 6.0.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: /%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/2022/08
* Custom upload_path: 
* Custom upload_url_path: 
* Compatible content directory: Yes

# WordPress Plugins

* ActivityPub: 0.13.4
* Akismet Anti-Spam: 5.0
* Beautiful and responsive cookie consent: 2.9.0
* Better Click To Tweet: 5.10.2
* CodeBard's Patron Button and Widgets for Patreon: 2.1.5
* Code Snippets: 3.2.0
* Enhanced Media Library: 2.8.9
* Getwid: 1.8.2
* Gutenberg: 13.8.0
* Login LockDown: v1.8.1
* Matomo Analytics - Ethical Stats. Powerful Insights.: 4.10.0
* NodeInfo: 1.0.6
* Performance Lab: 1.3.0
* Read Meter - Reading Time & Progress Bar for WordPress.: 1.0.6
* Redirection: 5.3.1
* Semantic-Linkbacks: 3.11.1
* Site Kit by Google: 1.80.0
* Smush: 3.10.3 (Network enabled)
* W3 Total Cache: 2.2.3 (Network enabled)
* WebFinger: 3.2.5
* Webmention: 4.0.8
* WebP Express: 0.25.5 (Network enabled)
* WP-Optimize - Clean, Compress, Cache: 3.2.6
* WPCode - Insert Headers, Footers, and Code Snippets: 2.0.1
* WP Crontrol: 1.14.0
* WP Database Backup: 5.8.3
* WPForms Lite: 1.7.5.5
* WP to Buffer: 3.8.2
* Yoast Duplicate Post: 4.5
* Yoast SEO: 19.4
* Active Plugins: 12 (akismet duplicate-post enhanced-media-library insert-headers-and-footers login-lockdown matomo redirection wordpress-seo wp-crontrol wp-database-backup wp-to-buffer wpforms-lite)
* Theme: twentytwenty (twentytwenty)

# Server

* Server Info: Apache
* PHP OS: Linux
* PHP Version: 7.4.25
* PHP SAPI: fpm-fcgi
* PHP Binary Name: php-fpm
* PHP Error Reporting: 0 After bootstrap: 0
* PHP Found Binary: php -q
* Timezone: UTC
* WP timezone: Africa/Porto-Novo
* Locale: fr_FR
* User Locale: en_US
* Memory Limit: 256M (At least 128MB recommended. Depending on your traffic 256MB or more may be needed.)
* WP Memory Limit: 40M
* WP Max Memory Limit: 256M
* Timezone version: 2021.1
* Time: 1659626204
* Max Execution Time: 180
* Max Post Size: 128M
* Max Upload Size: 134217728
* Max Input Vars: 2500
* Disabled PHP functions: No
* zlib.output_compression is off: Yes
* Curl Version: 7.52.1, OpenSSL/1.0.2u
* Suhosin installed: No

# Database

* MySQL Version: 5.7.23
* Mysqli Connect: Yes
* Force MySQL over Mysqli: No
* DB Prefix: yrc_
* 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; rv:103.0) Gecko/20100101 Firefox/103.0)
* Language: fr,fr-fr,en-us,en

@mattmary thx for your answer. Will keep it in mind, as I’m changing optics…
I installed Matomo on premise on 1 of my subdomains, connected the WWW blog to it via the other plugin and so far it seems to work.
Just added a 2nd low traffic site and about to add the last 2 and see how it goes.
My idea is that instead of having Matomo x 4 on my shared hosting, I’d only 1 instance running – might be wrong in thinking so, but at least WWW has stats coming in…
At least this setup was comfortable with 192MB of memory limit. But now it asks for a bigger packet size “It is recommended to configure a ‘max_allowed_packet’ size in your MySQL database of at least 64MB. Configured is currently 32MB.” Not sure I’m allowed to change the value. Will check.
Sincerely
DJM