Matomo Cron Error

Hi @aforumuser, what version of Matomo for WordPress are you using? If it’s not the latest, can you update to the latest?

Can you also post the system report from the Matomo Analytics > Diagnostics page?

Regarding the error in the log, that error occurs when the download for the free db-ip IP geolocation database fails (this database is used to tell where your visitors are from), in this case possibly due to db-ip.com. It’s not related to the message about report data not being processed yet.

Thanks for your reply. My plugin version is 5.1.2, which I think is the latest (I don’t see any option to upgrade it in WP). And here’s my system report below.

The same thing has happened today: I had reports and everything was fine all day, but some time this afternoon it seems to reset.

				  # Matomo

* Matomo Plugin Version: 5.1.2
* Config exists and is writable.: Yes ("$abs_path/wp-content/uploads/matomo/config/config.ini.php" )
* JS Tracker exists and is writable.: Yes ("$abs_path/wp-content/uploads/matomo/matomo.js" )
* Plugin directories: Yes ([{"pluginsPathAbsolute":"$abs_path\/wp-content\/plugins\/matomo\/plugins","webrootDirRelativeToMatomo":"..\/plugins"}])
* Tmp directory writable: Yes ($abs_path/wp-content/cache/matomo)
* Matomo Version: 5.1.0
* Matomo Blog idSite: 1
* Matomo Install Version: 5.1.0 (Install date: 2024-07-12 18:21:50)
* 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

* Server time: 2024-08-13 21:00:10
* Blog time: 2024-08-13 22:00:10 (Below dates are shown in blog timezone)
* Sync users & sites: Next run: 2024-08-14 10:40:43 (12 hours 40 min) ( Last started: 2024-08-13 10:45:03 (-11 hours 15 min). Last ended: 2024-08-13 10:45:03 (-11 hours 15 min). Interval: daily)
* Archive: Next run: 2024-08-13 22:21:52 (21 min 42s) ( Last started: 2024-08-13 21:25:03 (-35 min 7s). Last ended: 2024-08-13 21:25:13 (-34 min 57s). Interval: hourly)
* Update GeoIP DB: Next run: 2024-09-11 10:40:43 (28 days 12 hours) ( Last started: 2024-08-13 11:50:02 (-10 hours 10 min). Last ended: 2024-08-13 11:51:11 (-10 hours 8 min). Interval: matomo_monthly)

## Mandatory checks

* PHP version >= 7.2.5: 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 

## Optional checks

* 64-bit PHP Binary: ok 
* Tracker status: ok 
* Memory limit: ok 
* Time zone: ok 
* Open URL: ok 
* GD > 2.x + FreeType (graphics): ok 
* Other extensions: ok 
* Other functions: ok 
* Filesystem: ok 
* Last Successful Archiving Completion: ok 
* Database abilities: ok 
* Max Packet Size: ok 
* Geolocation: ok 
* Update over HTTPS: ok 
* Mobile Messaging SMS Provider: ok 
* Supports Async Archiving: Yes
* Async Archiving Disabled in Setting: No
* 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. <a  target="_blank">Learn more</a>)
* Warning Proxy header: HTTP_CF_CONNECTING_IP (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. <a  target="_blank">Learn more</a>)
* Had visit in last 5 days: Yes
* Matomo URL: Yes ($site_url/wp-content/plugins/matomo/app/)

## Matomo Settings

* Track mode: tagmanager
* Track ecommerce: Yes
* Track codeposition: footer
* Track api endpoint: default
* Track js endpoint: default
* Version history: 5.1.2, 5.1.1, 5.1.0
* Core version: 5.1.0
* Last tracking settings update: 1722110240
* Last settings update: 1722110240
* Disable cookies: Yes
* Mail history: 2024-08-13 06:25:13, 2024-08-12 06:25:12, 2024-08-11 06:25:13

## Logs

* update_geoip2: 2024-08-12 11:45:03 (GeoIP2AutoUpdater: failed to download 'https://download.db-ip.com/free/dbip-city-lite-2024-08.mmdb.gz' to '$abs_path/wp-content/cache/matomo/latest/DBIP-City.mmdb.gz.download': Error while fetching data: cURL error 28: Operation timed out after 3600000 milliseconds with 51059173 out of 51259198 bytes received => GeoIP2AutoUpdater.php:144; GeoIP2AutoUpdater.php:89; ScheduledTasks.php:259; class-wp-hook.php:322; class-wp-hook.php:348; plugin.php:565; wp-cron.php:191;)

# WordPress

* Home URL: $site_url
* Site URL: $site_url
* WordPress Version: 6.6.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: Yes
* FORCE_SSL_ADMIN: Yes
* WP_CACHE: Yes
* 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_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/2024/08
* Custom upload_path: 
* Custom upload_url_path: 
* Compatible content directory: Yes
* WP_Filesystem Initialized: Yes

# WordPress Plugins

* Create Block Theme: 2.3.0
* Custom Fonts: 2.1.6
* hc functions: 
* LiteSpeed Cache: 6.3.0.1
* Matomo Analytics - Ethical Stats. Powerful Insights.: 5.1.2
* Redirection: 5.5.0
* Spectra: 2.15.1
* UpdraftPlus - Backup/Restore: 1.24.4
* Wordfence Security: 7.11.7 (Network enabled)
* WPS Hide Login: 1.9.16.7
* Yoast Duplicate Post: 4.5
* Yoast SEO: 23.2
* Active Plugins: 12 (create-block-theme:2.3.0 custom-fonts:2.1.6 duplicate-post:4.5 hc-functions litespeed-cache:6.3.0.1 matomo:5.1.2 redirection:5.5.0 ultimate-addons-for-gutenberg:2.15.1 updraftplus:1.24.4 wordfence:7.11.7 wordpress-seo:23.2 wps-hide-login:1.9.16.7)
* Theme: twentytwentyfour (hc-theme)

# Server

* Server Info: LiteSpeed
* PHP OS: Linux
* PHP Version: 8.3.10
* PHP SAPI: litespeed
* PHP Binary Name: /usr/local/bin/lsphp
* PHP Maxmind DB extension: Not loaded
* PHP Error Reporting: 4437 After bootstrap: 4437
* PHP Found Binary: /opt/alt/php83/usr/bin/php -q
* Timezone: UTC
* WP timezone: Europe/London
* Locale: en_GB
* User Locale: en_GB
* Memory Limit: 1024M (At least 128MB recommended. Depending on your traffic 256MB or more may be needed.)
* WP Memory Limit: 512M
* WP Max Memory Limit: 1024M
* Timezone version: 2024.1
* Time: 1723582810
* Max Execution Time: 1500
* Max Post Size: 1024M
* Max Upload Size: 1073741824
* Max Input Vars: 2000
* Disabled PHP functions: No
* zlib.output_compression is off: Yes
* Curl Version: 7.87.0, OpenSSL/1.1.1w
* Suhosin installed: No

# PHP cli

* PHP CLI Version: 8.3.10
* MySQLi support: ok
* PHP CLI configuration: Configured correctly

# Database

* MySQL Version: 10.6.18
* Mysqli Connect: Yes
* Force MySQL over Mysqli: No
* DB Prefix: wpjp_
* DB CHARSET: utf8mb4
* DB COLLATE: 
* SHOW ERRORS: No
* SUPPRESS ERRORS: No
* Uses Socket: No
* Uses IPv6: No
* Matomo tables found: 59
* DB tables exist: Yes
* Matomo users found: 1
* Matomo sites found: 1
* Required permissions: OK

# Browser

* Browser:  (Mozilla/5.0 (Windows NT 10.0; rv:129.0) Gecko/20100101 Firefox/129.0)
* Language: en-gb,en

	

Hi @aforumuser, when data disappears, does it disappear for every day or just the latest available date (ie, today)? Do you see data for, for example, August 11th?

Hi @aforumuser, are you still experiencing an issue around this? (If so, can you answer my questions above?)

Hi, sorry for the delay, I was waiting for the issue to happen again, which it did this morning (Aug 20). Yes, I can see some of the previous days’ data when it happens.

The issue seems to be quite intermittent, and seems to resolve itself within a few hours. During that time, I can’t see any reports for the current day.

@aforumuser Is the time it happens at or around midnight UTC? And how is your WP cron set up?

• This reply was modified 3 months ago by dizzyatinnocraft.

Thanks for replying. It’s not the usual midnight reset. This can happen at random times in the day, even when reports have already been generated. For instance, I might check reports at 10am, but at 2pm I might see the message “reports haven’t been generated”, and all stats are reset to zero. Then maybe an hour or two later, it all comes back.

I’ve set up WPCron to run manually (I think it’s every 15 minutes).

@aforumuser That is a very odd problem, and the solution may be hard to track down… The next time it occurs, can you check the following:

• make note of the current time, and check in the System Report what time archiving last ran and make note of that time
• wait 15 minutes and see if archiving runs again, then check if there’s data
• if there isn’t data, and you’re ok with pausing archiving to investigate this, add define('MATOMO_DISABLE_WP_ARCHIVING', true); to your wp-config.php (before the /* That's all, stop editing! Happy publishing. */ line)
• then post the times you noted, whether running manually fixed it, and whether you paused archiving

Thanks @dizzyatinnocraft. That sounds reasonable – I’ll do that. Is it OK to leave this thread open in case it happens again soon? Otherwise feel free to close it and I’ll start a new thread if I need to. Thanks for your guidance.

@aforumuser yes it’s fine to leave this open. I’ll probably close it if I don’t hear anything in a week, but there’ll never be an issue with you creating a new issue.

Hi @dizzyatinnocraft ,

Matomo has collected some data today (Aug 23), but reports are now frozen on stats from earlier in the day.

• I’ve noticed this at13:04. Reports haven’t updated since then – they’re still frozen on the earlier stats.
• My CronJob is set to run every 5 minutes in CPanel.
• The Sys Report section is below, and I’ve temporarily paused archiving in WPConfig as per your note above. How long should I leave this off?

Thanks in advance!

Crons

• Server time: 2024-08-23 12:57:52
• Blog time: 2024-08-23 13:57:52 (Below dates are shown in blog timezone)
• Sync users & sites: Next run: 2024-08-24 10:40:43 (20 hours 42 min) ( Last started: 2024-08-23 10:45:02 (-3 hours 12 min). Last ended: 2024-08-23 10:45:03 (-3 hours 12 min). Interval: daily)
• Archive: Next run: 2024-08-23 14:21:52 (24 min 0s) ( Last started: 2024-08-23 13:25:03 (-32 min 49s). Last ended: 2024-08-23 13:25:13 (-32 min 39s). Interval: hourly)
• Update GeoIP DB: Next run: 2024-09-11 10:40:43 (18 days 20 hours) ( Last started: 2024-08-13 11:50:02 (-10 days 2 hours). Last ended: 2024-08-13 11:51:11 (-10 days 2 hours). Interval: matomo_monthly)

Quick update, the reports seem to have mostly caught-up with the visits I can see in the dashboard’s Visitors > Visits Log. That’s true of the current time, 15:28.

In case it’s useful, here’s the Cron section of Sys Report again:

Crons

• Server time: 2024-08-23 14:29:11
• Blog time: 2024-08-23 15:29:11 (Below dates are shown in blog timezone)
• Sync users & sites: Next run: 2024-08-24 10:40:43 (19 hours 11 min) ( Last started: 2024-08-23 10:45:02 (-4 hours 44 min). Last ended: 2024-08-23 10:45:03 (-4 hours 44 min). Interval: daily)
• Archive: Next run: 2024-08-23 16:21:52 (52 min 41s) ( Last started: 2024-08-23 15:25:03 (-4 min 8s). Last ended: 2024-08-23 15:25:03 (-4 min 8s). Interval: hourly)
• Update GeoIP DB: Next run: 2024-09-11 10:40:43 (18 days 19 hours) ( Last started: 2024-08-13 11:50:02 (-10 days 3 hours). Last ended: 2024-08-13 11:51:11 (-10 days 3 hours). Interval: matomo_monthly)

@aforumuser Is archiving still manually disabled? If so, I wouldn’t expect the visits to update. To look into this further, can you email me at dizzy (at) innocraft (dot) com? We’ll need to stop archiving until we can find the cause (otherwise archiving may run while investigating, work, and we won’t be able to inspect the broken state).

Also note, disabling archiving won’t make the data collected in the meantime disappear from reports, when re-enabling archiving, the older reports will be regenerated and there won’t be any missing data.

Thanks for your help. I’ll get in touch.