• Resolved gilles24

    (@gilles24)


    Hello,
    Reports not working…
    Here is the copy of the system report.
    I specify that memory_limit is 2048 in php.ini

    • Matomo plugin version: 4.13.0
    • 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”:”..\/”}])
    • Writable temporary directory: Yes ($abs_path/wp-content/cache/matomo)
    • Matomo Version: 4.13.0
    • SiteID of the Matomo website: 1
    • Installed version of Matomo: 4.13.0 (Install date: 2023-01-15 18:55:50)
    • Outstanding Upgrades: 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: 2023-01-15 19:39:51
    • Website time: 2023-01-15 20:39:51 (Dates below are displayed in website time zone)
    • Sync users & sites: Next run: 2023-01-16 18:55:53 (22 hours 16 min) ( Last started: 2023-01-15 18:55:56 (-1 hours 43 min). Last ended: 2023-01-15 18:56:10 (-1 hours 43 min. Interval: daily)
    • Archive: Next run: 2023-01-15 20:55:54 (16 min 3s) ( Last started: 2023-01-15 19:55:59 (-43 min 52s). Last ended: 2023-01-15 19:56:15 (-43 min 36s. Interval: hourly)
    • Update GeoIP DB: Next run: 2023-02-14 18:55:54 (29 days 22 hours) ( Last started: 2023-01-15 18:56:12 (-1 hours 43 min). Last ended: 2023 -01-15 18:56:14 (-1 hours 43 mins. Interval: matomo_monthly)

    Mandatory checks

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

    Optional controls

    • 64-bit PHP binary: ok
    • Tracker status: ok
    • Memory limit: ok
    • Time zone: ok
    • Open URL: ok
    • PageSpeed is off: ok
    • GD > 2.x + FreeType (graphics): ok
    • Other extensions: ok
    • Other functions: ok
    • File system: ok
    • Last successful archive run: ok
    • Database capabilities: ok
    • Maximum packet size: ok
    • Geolocation: ok
    • Update via HTTPS: ok
    • Supports Async Archiving: Yes
    • Location provider ID: geoip2php
    • Rental 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 code position: footer
    • Track api endpoint: default
    • Track js endpoint: default
    • Version history: 4.13.0
      *Core version: 4.13.0
    • Last tracking settings update: 1673805499
    • Last settings update: 1673805578
    • Disable cookies: Yes

    Logs

    • archive_boot: 2023-01-15 19:56:10 (Matomo error: 8192: Required parameter $haystack follows optional parameter $needle in $abs_path/wp-content/plugins/wpb-woocommerce-custom-tab-manager-pro/ admin/meta-box/meta_box.php:423 => bootstrap.php:56; bootstrap.php:85; main.php:86; main.php:86; class-wp-hook.php:308; class-wp -hook.php:332; plugin.php:517; wp-settings.php:480; wp-config.php:36; wp-load.php:50; bootstrap.php:95; console:11;)
    • archive_boot: 2023-01-15 19:56:14 (Matomo error: 8192: Required parameter $haystack follows optional parameter $needle in $abs_path/wp-content/plugins/wpb-woocommerce-custom-tab-manager-pro/ admin/meta-box/meta_box.php:423 => bootstrap.php:56; bootstrap.php:85; main.php:86; main.php:86; class-wp-hook.php:308; class-wp -hook.php:332; plugin.php:517; wp-settings.php:480; wp-config.php:36; wp-load.php:50; bootstrap.php:95; console:11;)
    • Warning archive_main: 2023-01-15 19:56:15 (8 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:306; class-wp-hook.php:332; plugin.php:565; wp-cron. php:188;)
    • Warning archive_errors: 2023-01-15 19:56:15 (‘Got invalid response from API request: ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=day&date=2023-01-15&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

    The page I need help with: [log in to see the link]

Viewing 1 replies (of 1 total)
Viewing 1 replies (of 1 total)

The topic ‘Reports not working…’ is closed to new replies.