I have just upgraded to 4.10 from 4.05 and all my analytics Channel data and etc is one day behind. Attached is the screenshot.

Screen Shot 2020-12-22 at 23.14.482500×908 214 KB

1 post - 1 participant

Read full topic

After updating from 4.05 to 4.1 the widgets are not in a grid but instead are stacked vertically and full width. The side bar and navigation bar are also not formatted correctly.

There are no errors reported in System Check. In “Security” PHP it says “Unable to determine the latest version of PHP available.”

Initially I saw some orange error banners, but they disappeared before I could copy them.

These are the errors in the Error Log:

22-Dec-2020 17:57:20 UTC] Error in Matomo: Could not verify the security token on this form.
[22-Dec-2020 17:59:14 UTC] PHP Fatal error:  Uncaught Error: Class 'ComposerAutoloaderInit325cd015e07e1ce7b3e9f0c8bc735115' not found in /home/banancyb/public_html/piwik/vendor/autoload.php:7
Stack trace:
#0 /home/banancyb/public_html/piwik/core/bootstrap.php(44): require_once()
#1 /home/banancyb/public_html/piwik/index.php(19): require_once('/home/banancyb/...')
#2 {main}
  thrown in /home/banancyb/public_html/piwik/vendor/autoload.php on line 7
[22-Dec-2020 17:59:14 UTC] PHP Fatal error:  Uncaught Error: Class 'ComposerAutoloaderInit325cd015e07e1ce7b3e9f0c8bc735115' not found in /home/banancyb/public_html/piwik/vendor/autoload.php:7
Stack trace:
#0 /home/banancyb/public_html/piwik/core/bootstrap.php(44): require_once()
#1 /home/banancyb/public_html/piwik/index.php(19): require_once('/home/banancyb/...')
#2 {main}
  thrown in /home/banancyb/public_html/piwik/vendor/autoload.php on line 7
[22-Dec-2020 17:59:32 UTC] Error in Matomo: Protocol https not in list of allowed protocols: 
[22-Dec-2020 17:59:33 UTC] Error in Matomo: Protocol https not in list of allowed protocols:

Help would much appreciated. Thanks!

5 posts - 2 participants

Read full topic

Hello everyone,

running the archive web cronjob on a high traffic website with Matomo 4.1.0 the process raises errors and seems not to finish successfully.

Here’s what happens when running this process manually inside the browser (for better overview of the main error message, I skipped the middle of the output):

INFO CoreAdminHome[2020-12-22 17:05:56 UTC] [6f5e3] ---------------------------
INFO CoreAdminHome[2020-12-22 17:05:56 UTC] [6f5e3] INIT
INFO CoreAdminHome[2020-12-22 17:05:56 UTC] [6f5e3] Running Matomo 4.1.0 as Super User
INFO CoreAdminHome[2020-12-22 17:05:56 UTC] [6f5e3] ---------------------------
INFO CoreAdminHome[2020-12-22 17:05:56 UTC] [6f5e3] NOTES
INFO CoreAdminHome[2020-12-22 17:05:56 UTC] [6f5e3] - Async process archiving not supported, using curl requests.
INFO CoreAdminHome[2020-12-22 17:05:56 UTC] [6f5e3] - Reports for today will be processed at most every 1800 seconds. You can change this value in Matomo UI > Settings > General Settings.
INFO CoreAdminHome[2020-12-22 17:05:56 UTC] [6f5e3] - Archiving was last executed without error 6 Stunden 34 Minuten ago
INFO CoreAdminHome[2020-12-22 17:06:01 UTC] [6f5e3] ---------------------------
INFO CoreAdminHome[2020-12-22 17:06:01 UTC] [6f5e3] START
INFO CoreAdminHome[2020-12-22 17:06:01 UTC] [6f5e3] Starting Matomo reports archiving...
INFO CoreAdminHome[2020-12-22 17:06:06 UTC] [6f5e3] Start processing archives for site 1.
INFO CoreAdminHome[2020-12-22 17:06:06 UTC] [6f5e3] Will invalidate archived reports for today in site ID = 1's timezone (2020-12-22 00:00:00).
INFO CoreAdminHome[2020-12-22 17:06:06 UTC] [6f5e3] Will invalidate archived reports for yesterday in site ID = 1's timezone (2020-12-21 00:00:00).
...
INFO CoreAdminHome[2020-12-22 17:06:25 UTC] [6f5e3] Finished archiving for site 1, 22 API requests, Time elapsed: 19.322s [1 / 1 done]
INFO CoreAdminHome[2020-12-22 17:06:30 UTC] [6f5e3] Done archiving!
INFO CoreAdminHome[2020-12-22 17:06:30 UTC] [6f5e3] ---------------------------
INFO CoreAdminHome[2020-12-22 17:06:30 UTC] [6f5e3] SUMMARY
INFO CoreAdminHome[2020-12-22 17:06:30 UTC] [6f5e3] Processed 21 archives.
INFO CoreAdminHome[2020-12-22 17:06:30 UTC] [6f5e3] Total API requests: 22
INFO CoreAdminHome[2020-12-22 17:06:30 UTC] [6f5e3] done: 22 req, 28988 ms, 6 errors.
INFO CoreAdminHome[2020-12-22 17:06:30 UTC] [6f5e3] Time elapsed: 28.988s
INFO CoreAdminHome[2020-12-22 17:06:30 UTC] [6f5e3] ---------------------------
INFO CoreAdminHome[2020-12-22 17:06:30 UTC] [6f5e3] SCHEDULED TASKS
INFO CoreAdminHome[2020-12-22 17:06:30 UTC] [6f5e3] Starting Scheduled tasks...
INFO CoreAdminHome[2020-12-22 17:06:30 UTC] [6f5e3] Scheduler: executing task Piwik\Plugins\CustomJsTracker\Tasks.updateTracker...
INFO CoreAdminHome[2020-12-22 17:06:30 UTC] [6f5e3] Scheduler: finished. Time elapsed: 0.001s
INFO CoreAdminHome[2020-12-22 17:06:30 UTC] [6f5e3] Scheduler: executing task Piwik\Plugins\PrivacyManager\Tasks.deleteLogData...
INFO CoreAdminHome[2020-12-22 17:06:30 UTC] [6f5e3] Scheduler: finished. Time elapsed: 0.000s
INFO CoreAdminHome[2020-12-22 17:06:30 UTC] [6f5e3] Scheduler: executing task Piwik\Plugins\PrivacyManager\Tasks.anonymizePastData...
INFO CoreAdminHome[2020-12-22 17:06:30 UTC] [6f5e3] Scheduler: finished. Time elapsed: 0.000s
INFO CoreAdminHome[2020-12-22 17:06:30 UTC] [6f5e3] done
INFO CoreAdminHome[2020-12-22 17:06:30 UTC] [6f5e3] ---------------------------
INFO CoreAdminHome[2020-12-22 17:06:30 UTC] [6f5e3] ---------------------------
INFO CoreAdminHome[2020-12-22 17:06:30 UTC] [6f5e3] SUMMARY OF ERRORS
INFO CoreAdminHome[2020-12-22 17:06:30 UTC] [6f5e3] Error: Got invalid response from API request: ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=day&date=2020-12-22&format=json&segment=deviceType%253D%253Dtablet%252CdeviceType%253D%253Ddesktop&trigger=archivephp. Response was '{"result":"error","message":"Invalid 'log_visit.config_device_type' segment value tablet,deviceType==desktop"}'
INFO CoreAdminHome[2020-12-22 17:06:30 UTC] [6f5e3] Error: Got invalid response from API request: ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=week&date=2020-12-21&format=json&segment=deviceType%253D%253Dtablet%252CdeviceType%253D%253Ddesktop&trigger=archivephp. Response was '{"result":"error","message":"Invalid 'log_visit.config_device_type' segment value tablet,deviceType==desktop"}'
INFO CoreAdminHome[2020-12-22 17:06:30 UTC] [6f5e3] Error: Got invalid response from API request: ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=month&date=2020-12-01&format=json&segment=deviceType%253D%253Dtablet%252CdeviceType%253D%253Ddesktop&trigger=archivephp. Response was '{"result":"error","message":"Invalid 'log_visit.config_device_type' segment value tablet,deviceType==desktop"}'
INFO CoreAdminHome[2020-12-22 17:06:30 UTC] [6f5e3] Error: Got invalid response from API request: ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=year&date=2020-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 your web server's error Log file. As this core:archive command triggers PHP processes over HTTP, you can find the error message in your Matomo's web server error logs.
INFO CoreAdminHome[2020-12-22 17:06:30 UTC] [6f5e3] Error: Error unserializing the following response from ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=year&date=2020-01-01&format=json&trigger=archivephp: ''
INFO CoreAdminHome[2020-12-22 17:06:30 UTC] [6f5e3] Error: Got invalid response from API request: ?module=API&method=CoreAdminHome.archiveReports&idSite=1&period=year&date=2020-01-01&format=json&segment=deviceType%253D%253Dtablet%252CdeviceType%253D%253Ddesktop&trigger=archivephp. Response was '{"result":"error","message":"Invalid 'log_visit.config_device_type' segment value tablet,deviceType==desktop"}'
ERROR CoreAdminHome[2020-12-22 17:06:30 UTC] [6f5e3] 6 total errors during this script execution, please investigate and try and fix these errors.
ERROR API[2020-12-22 17:06:30 UTC] [6f5e3] Uncaught exception in API: /www/htdocs/w01xxxxx/web/core/CronArchive.php(605): 6 total errors during this script execution, please investigate and try and fix these errors.
  6 total errors during this script execution, please investigate and try and fix these errors.
Error: 6 total errors during this script execution, please investigate and try and fix these errors.

Usually this is being run as a web cronjob every 30 minutes.
Running the System check seems fine to me (except a few suggestions for data integrity which should not be an issue here):

# Mandatory checks

## PHP-Version >= 7.2.5: ✔ 7.4.10

## PDO Erweiterung: ✔ 

## PDO\MYSQL Erweiterung: ✔ 

## MYSQLI Erweiterung: ✔ 
## Weitere erforderliche Anforderungen: ✔ zlib ✔ SPL ✔ iconv ✔ json ✔ mbstring ✔ Reflection
## Erforderliche Funktionen: ✔ debug_backtrace ✔ eval ✔ hash ✔ gzcompress ✔ gzuncompress ✔ pack
## Benötigte PHP Konfiguration (php.ini): ✔ session.auto_start = 0 ✔ max_execution_time = 0 OR >= 30
## Verzeichnisse mit Schreibzugriff: ✔ $DOC_ROOT/tmp ✔ $DOC_ROOT/tmp/assets ✔ $DOC_ROOT/tmp/cache ✔ $DOC_ROOT/tmp/climulti ✔ $DOC_ROOT/tmp/latest ✔ $DOC_ROOT/tmp/logs ✔ $DOC_ROOT/tmp/sessions ✔ $DOC_ROOT/tmp/tcpdf ✔ $DOC_ROOT/tmp/templates_c

# Optional checks

## Dateiintegrität: ⚠ Warning: Der Datei-Integritätscheck ist fehlgeschlagen und hat ein paar Fehler gemeldet. Du solltest die Probleme beheben und diese Seite neuladen, bis sie keine Fehler mehr anzeigt.<br/><br/><pre style="overflow-x: scroll;max-width: 600px;">Es wurden unerwartete Dateien in Ihrer Matomo-Installation gefunden.<br/>--> Bitte löschen Sie diese Dateien, um Fehler zu vermeiden. <--<br/><br/>Zu löschende Datei: js/piwik-min.js<br/>Zu löschende Datei: js/piwik.js.orig<br/>Zu löschende Datei: wartung/backup.php<br/>Zu löschende Datei: usage/.htpasswd<br/><br/><br/>Um alle diese Dateien auf einmal zu löschen, kannst du folgenden Befehl ausführen:<br/>rm "$DOC_ROOT/js/piwik-min.js" "$DOC_ROOT/js/piwik.js.orig" "$DOC_ROOT/wartung/backup.php" "$DOC_ROOT/usage/.htpasswd"<br/><br/></pre>

## Tracker-Status: ✔ 
## Speicherlimit: ✔ 512M
## Zeitzone: ✔ 
## Öffnen einer URL: ✔ curl
## PageSpeed deaktiviert: ✔ 
## GD > 2.x + Freetype (graphics): ✔ 
## Andere Erweiterungen: ✔ json ✔ libxml ✔ dom ✔ SimpleXML
## Andere Funktionen: ✔ shell_exec ✔ set_time_limit ✔ mail ✔ parse_ini_file ✔ glob ✔ gzopen ✔ md5_file
## Dateisystem: ✔ 

## Cron einrichten - Prozesse via CLI steuern: nicht unterstützt (optional)
## Letzter erfolgreicher Abschluss der Archivierung: ✔ Der Archivierungsprozess wurde vor 07:35:58 erfolgreich abgeschlossen.
## Datenbankfähigkeiten: ✔ UTF8mb4 charset ✔ LOAD DATA INFILE ✔ CREATE TEMPORARY TABLES ✔ Changing transaction isolation level
## Maximale Packetgröße: ✔ 
## Erzwungene SSL Verbindung: ✔ 
## Standorterkennung: ✔ 
## Update über HTTPS: ✔ 
## Schreibbarer JavaScript-Tracker ("/matomo.js"): ✔ 

# Informational results

## Matomo Version: 4.1.0
## Matomo Update History: 3.14.1,
## Matomo Install Version: 3.8.0
## PHP_OS: Linux
## PHP_BINARY: /usr/sbin/php74-fpm
## PHP SAPI: fpm-fcgi
## Timezone Version: 0.system
## PHP Timezone: UTC
## PHP Time: 1608660441
## PHP Datetime: 2020-12-22 18:07:21
## PHP INI max_execution_time: 30
## PHP INI post_max_size: 200M
## PHP INI max_input_vars: 3000
## PHP INI zlib.output_compression: 
## Curl Version: 7.68.0, OpenSSL/1.1.1f
## Suhosin Installed: 0

## DB Prefix: matomo_
## DB Charset: utf8mb4
## DB Adapter: PDO\MYSQL
## MySQL Version: 10.5.6-MariaDB-1:10.5.6+maria~focal-log
## Num Tables: 156
## Browser Segment Archiving Enabled: 0
## Development Mode Enabled: 0
## Internet Enabled: 1
## Multi Server Environment: 0
## Custom User Path: 0
## Custom Include Path: 0

## Plugins Activated: API, Actions, Annotations, BulkTracking, Contents, CoreAdminHome, CoreConsole, CoreHome, CorePluginsAdmin, CoreUpdater, CoreVisualizations, CustomDimensions, CustomJsTracker, Dashboard, DevicePlugins, DevicesDetection, Diagnostics, Ecommerce, Events, Feedback, GeoIp2, Goals, Heartbeat, ImageGraph, Insights, Installation, Intl, IntranetMeasurable, LanguagesManager, Live, Login, Marketplace, MobileMessaging, Monolog, Morpheus, MultiSites, Overlay, PagePerformance, PrivacyManager, ProfessionalServices, Provider, Proxy, Referrers, Resolution, RssWidget, SEO, ScheduledReports, SegmentEditor, SitesManager, Tour, Transitions, TwoFactorAuth, UserCountry, UserCountryMap, UserId, UserLanguage, UsersManager, VisitFrequency, VisitTime, VisitorInterest, VisitsSummary, WebsiteMeasurable, Widgetize

## Plugins Deactivated: CustomVariables, DBStats, MobileAppMeasurable, TagManager

## Plugins Invalid: 

## Server Info: Apache

## Had visits in last 1 day: 1
## Had visits in last 3 days: 1
## Had visits in last 5 days: 1
## Archive Time Last Started: 1608660145
## Archive Time Last Finished: 1608633080
## Num invalidations: 1 queued, 0 in progress
## User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/87.0.4280.88 Safari/537.36
## Browser Language: de-de,de,en-us,en
## Anonymize Referrer: 
## Do Not Track enabled: 0

Any help to possibly get rid of these six errors with the response

Response was ‘{“result”:“error”,“message”:“Invalid ‘log_visit.config_device_type’ segment value tablet,deviceType==desktop”}’

is greatly appreciated.

Thank you for your help!

1 post - 1 participant

Read full topic

Recently migrated database, and found this error
Error in the log life
'Integrity constraint violation: 1062 Duplicate entry ‘0’ for key ‘PRIMARY’ In query: INSERT INTO matomo_log_action ’

1 post - 1 participant

Read full topic

Surfing in the settings, I came across the Security tab, sorted below the Diagnostics header. Once there, I was greeted by a reassuring message that something was amiss. It had a warm orangy-tinted background and carried just the right amount of urgency to do exactly as it said:

WARNING: PATH TO MATOMO/plugins/SecurityInfo/PhpSecInfo/Test/Application/php.php(39): Notice - Trying to access array offset on value of type bool - Matomo 4.1.0 - Please report this message in the Matomo forums: https://forum.matomo.org (please do a search first as it might have been reported already) (Module: SecurityInfo, Action: index, In CLI mode: false)

But maybe, I am just the conscientious kind of person.

Anyways. Thanks for the great product. If you need more info I’m happy to help.

1 post - 1 participant

Read full topic

PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 79956072196 bytes) in /XXXXX/htdocs/analytics/vendor/twig/twig/src/Extension/EscaperExtension.php on line 204

5 posts - 2 participants

Read full topic

Hello.

when trying to start up my matomo after installation I get the following message:

Capture1236×455 114 KB

I can’t seem to find the .ini file on my QNAP NAS to change what’s needed.

I hope anyone can help me!!

2 posts - 2 participants

Read full topic

Hello all,

I am at a loss and need your help . We have set up a new Matomo server at the beginning of the year. This is supposed to track SharePoint Onprem and SharePoint online pages. Since we only have modern sites in use, we downloaded the Matomo App. The tracking worked on both environments without any problems. This means that the app was installed via shell command and the site was tracked. Recently I noticed that I can install the app on the new Sharepoint Onine site, but it does not load. This means that in the developer tools of the browser you can see that Piwik is not loaded under the sources and nothing arrives at the Piwik server. With the pages at the beginning of the year everything is fine. These are also tracked. In the Onprem world, everything is also running perfectly. I downloaded the new app version from the Matomo page and deployed it in the App Catalog. However, this made no difference to the newly rolled out Sharepoint online page. Authorisation when installing the app is correct in any case. I cannot explain it to myself. Can it possibly be that MS has deposited new security? I hope someone can give me a tip.

1 post - 1 participant

Read full topic

* root@dab6a1398a2e:/var/www/html# ./console loginldap:synchronize-users --login=felipe.me@MYDOMAIN.it -vvv

* DEBUG [2020-12-23 14:57:59] 2527 UserSynchronizer::makeConfigured(): LDAP access synchronization not enabled.

* DEBUG [2020-12-23 14:57:59] 2527 UserSynchronizer::makeConfigured: configuring with defaultSitesWithViewAccess = all

* DEBUG [2020-12-23 14:57:59] 2527 UserSynchronizer::makeConfigured(): LDAP access synchronization not enabled.

* DEBUG [2020-12-23 14:57:59] 2527 UserSynchronizer::makeConfigured: configuring with defaultSitesWithViewAccess = all

* Synchronizing 'felipe.me@domain'... DEBUG [2020-12-23 14:57:59] 2527 Model\LdapUsers: start getUser() with [array]

* DEBUG [2020-12-23 14:57:59] 2527 Calling ldap_connect('ldaps :// 10.255.8.30', 3269)

* DEBUG [2020-12-23 14:57:59] 2527 ldap_connect result is [resource]

* WARNING [2020-12-23 14:57:59] 2527 /var/www/html/plugins/LoginLdap/Ldap/Client.php(91): Warning - ldap_bind(): Unable to bind to server: Can't contact LDAP server - Matomo 3.14.1 - Please report this message in the Matomo forums (please do a search first as it might have been reported already)

* DEBUG [2020-12-23 14:57:59] 2527 anonymous ldap_bind call finished; connection ok

* INFO [2020-12-23 14:57:59] 2527 LdapUsers::makeLdapClient: Using LDAP server ldaps

* 10.255.8.30:3269

* DEBUG [2020-12-23 14:57:59] 2527 Calling ldap_bind([resource], 'cn=LDAP_Linux,ou=Service Accounts,dc=iit,dc=local', <password[length=XX]>)

* WARNING [2020-12-23 14:57:59] 2527 /var/www/html/plugins/LoginLdap/Ldap/Client.php(146): Warning - ldap_bind(): Unable to bind to server: Can't contact LDAP server - Matomo 3.14.1 - Please report this message in the Matomo forums: (please do a search first as it might have been reported already)

* DEBUG [2020-12-23 14:57:59] 2527 ldap_bind result is '0'

* DEBUG [2020-12-23 14:57:59] 2527 Calling ldap_close([resource])

* DEBUG [2020-12-23 14:57:59] 2527 ldap_close returned true

* failed!



Synchronized 0 users!

Could not synchronize the following users in LDAP:
<myuser>		Could not bind as LDAP admin.

via ldapsearch and using ldaps 10.255.8.30:3269 and same credentials it works
I did add “TLS_REQCERT never” to /etc/ldap/ldap.conf
so it cant be a SSL Certificate problem

I am using matomo via official repo

I spent many hours in this problem… any help is welcome

1 post - 1 participant

Read full topic

Hello,

Find below message apperaing while updating through command line:
php /srv/data/web/vhosts/stat2.mosoft.fr/matomo/console core:update

After several attempts, due to timeout, I finally had this error message:

Executing UPDATE piwik_log_visit SET visitor_seconds_since_first = visitor_days_since_first * 86400,
                    visitor_seconds_since_order = visitor_days_since_order * 86400,
                    visitor_seconds_since_last = visitor_days_since_last * 86400;...
    [X] Critical Error during the update process:

    * /srv/data/web/vhosts/stat2.mosoft.fr/matomo/core/Updates/4.0.0-b1.php:
    Error trying to execute the migration 'UPDATE piwik_log_visit SET visitor_seconds_since_first = visitor_days_since_first * 86400,
                        visitor_seconds_since_order = visitor_days_since_order * 86400,
                        visitor_seconds_since_last = visitor_days_since_last * 86400;'.
    The error was: SQLSTATE[HY000]: General error: 1205 Lock wait timeout exceeded; try restarting transaction

    The above is the core error message. It should help explain the cause, but if you require further help please:

    * Check the [ Matomo FAQ ] which explains most common errors during update.
    * Ask your system administrator - they may be able to help you with the error which is most likely related to your server or MySQL setup.

    If you are an advanced user and encounter an error in the database upgrade:

    * identify and correct the source of the problem (e.g., memory_limit or max_execution_time)
    * execute the remaining queries in the update that failed
    * manually update the `option` table in your Matomo database, setting the value of version_core to the version of the failed update
    * re-run the updater (through the browser or command-line) to continue with the remaining updates
    * report the problem (and solution) so that Matomo can be improved
ERROR [2020-12-24 10:12:46] 82632  Uncaught exception: /srv/data/web/vhosts/stat2.mosoft.fr/matomo/plugins/CoreUpdater/Commands/Update.php(255): Matomo could not be updated! See above for more information.
Matomo could not be updated! See above for more information.



  [RuntimeException]
  Matomo could not be updated! See above for more information.

Thank you for your help

1 post - 1 participant

Read full topic

i am transferring matomo to another server and i have exported all tables in single files in order to keep the import controllable.
but my server seems to crash every time i import the matomo_log_link_visit_action table (it looses the SSH connection after like 15 Minutes). It is one of the biggest tables. the SQL-file has a size of 3.5 GB.

now i wonder if i have to give the data up and set up a new installation… or is there any possibilty to get this file imported?

1 post - 1 participant

Read full topic

I received this on my email from the matomo cron:
ERROR [2020-12-29 17:05:56] 1266411 Got invalid response from API request: ?module=API&method=CoreAdminHome.archiveReports&idSite=2&period=day&date=2020-12-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 | grep error_log

The memory_limit in my php.ini is at 512M, isn’t it already too much? Isn’t that enough for matomo?

1 post - 1 participant

Read full topic

Hello

As described in article Manual converting to utf8mb4 for Matomo-4.x I have converted all Matomo databases to utf8mb4 using phpMyAdmin.

I random checked some databases and found the following:
Collation set to: utf8mb4_general_ci
All character fields are configured with collation utf8mb4_general_ci
So it seems the change was done correctly on the DB level.

After the update I added

charset = “utf8mb4” in the [database] section of the Matomo configi.ini.php file.

After this change tracking is not working, I get an error message in the server log:
mod_fcgid: stderr: Error in Matomo (tracker): Set Charset failed: Can’t initialize character set utf8mb4 (path: /usr/share/mysql/charsets/)

When I remove the charset = “utf8mb4” config tracking is working again, but I am not comfortable with this setting.

Versions:
Matomo-Version: 4.1.0
MySQL-Version: 5.5.41-MariaDB-log
PHP-Version: 7.3.18

In addition to the manual update I tried to update the DB from the General Settings in the Matomo Settings area, but it seems that this job never started (no change in config file after waiting for days).

Could someone help with the error message and point me to the correct measures? The instance is hosted on a shared webhosting, so my possibilities to make settings is limited.

It would also be interesting to get a more detailed description of the manual process. Since I have no console access I cannot run ./console core:convert-to-utf8mb4 --show command as suggested in the FAQ.

Many thanks for suggestions!

1 post - 1 participant

Read full topic

What is a good or practicable way with Matomo to:

1. check if Matomo redis config is properly configured and working
2. get an idea of Redis’ performance gain, like a quick benchmark

Any advise?

Happy New Year & thanks!

1 post - 1 participant

Read full topic

Hi,
I was just trying to update my matomo installation and it lasts much longer than ever and it runs into a Proxy timeout. Now I see this:

grafik791×551 31.5 KB

matomo@server:~/www/matomo$ php console core:update

    *** Update ***

    [X] Critical Error during the update process:

    * Database matomo is empty. You must edit or remove your Matomo configuration file.

    The above is the core error message. It should help explain the cause, but if you require further help please:

    * Check the [ Matomo FAQ ] which explains most common errors during update. 
    * Ask your system administrator - they may be able to help you with the error which is most likely related to your server or MySQL setup.
Uncaught exception in /home/matomo/www/matomo/vendor/php-di/php-di/src/Container.php line 135:
No entry or class found for 'log.handlers'

I then added the Line Plugins[] = "Login" to my config.ini.php and was able to reload the web interface and now I am running the same upgrade step again. But it just tells me again “Service Unavailable” after a while.
Now it seems that I can run php console core:update also in the terminal which is executing now.

Is there anything I need to check after this? What could possible go wrong?

It is taking a very long time at step 354:
Executing ALTER TABLE `log_link_visit_action` ADD COLUMN `search_cat` VARCHAR(200) NULL, ADD COLUMN `search_count` INTEGER(10) UNSIGNED NULL, ADD COLUMN `time_dom_completion` MEDIUMINT(10) UNSIGNED NULL, ADD COLUMN `time_dom_processing` MEDIUMINT(10) UNSIGNED NULL, ADD COLUMN `time_network` MEDIUMINT(10) UNSIGNED NULL, ADD COLUMN `time_on_load` MEDIUMINT(10) UNSIGNED NULL, ADD COLUMN `time_server` MEDIUMINT(10) UNSIGNED NULL, ADD COLUMN `time_transfer` MEDIUMINT(10) UNSIGNED NULL;...

2 posts - 1 participant

Read full topic

Sometime between 1 December and 1 January, one of the updates broke the tooltip on the ‘Visits over time’ widget. It now reports ‘0s Avg. generation time’, which is a vast improvement on my normal 0.18s, but the server hasn’t changed, so the issue must be one of the matomo updates that arrived during December. I didn’t notice it in December because it said “0.18s Avg. generation time”, all month, but since the new month started, matomo informs me that all my pages are generated in 0 seconds. I think this is untrue.

System Summary

1 users
0 segments (0 pre-processed, 0 processed in real-time)
0 goals
0 tracking failures
1 websites
45 activated plugins
Matomo version: 4.1.0
MySQL version: 10.3.27-MariaDB-0+deb10u1
PHP version: 7.3.19-1~deb10u1

1 post - 1 participant

Read full topic

Hello Everyone,

I just setup a new dedicated server and decided to setup a brand new Matomo On-site server and switch all my sites over from the ‘proxy script’ to the default tracking script for several reasons that are irrelevant.

My first (roughly) 90 websites found and connected to my Matomo server just fine using all default settings for the WP-Matomo Integration plugin. All of my websites are Wordpress sites.

The last 25 websites I’ve tried to add have all failed with this error message:

WP-Matomo 1.0.23 was not able to connect to Matomo using your configuration

Firstly, the plugin is at version 1.0.24 so there’s a small issue there.
I have flushed all caches in server, website, browser and rebooted the server several times, tried fresh installs of the plugin, disabled all protection in Cloudflare to test and still no luck.

I enabled WP-Debug and got the following output on a fresh failure of WP-Matomo:

Notice: Undefined offset: 114 in /home/runcloud/webapps/sample-website/wp-content/plugins/wp-piwik/classes/WP_Piwik/Admin/Settings.php on line 140

Notice: Trying to access array offset on value of type null in /home/runcloud/webapps/sample-website/wp-content/plugins/wp-piwik/classes/WP_Piwik/Admin/Settings.php on line 140

Notice: Undefined offset: 114 in /home/runcloud/webapps/sample-website/wp-content/plugins/wp-piwik/classes/WP_Piwik/Admin/Settings.php on line 140

Notice: Trying to access array offset on value of type null in /home/runcloud/webapps/sample-website/wp-content/plugins/wp-piwik/classes/WP_Piwik/Admin/Settings.php on line 140

The “Undefined offset: 114” is the SiteID that isn’t getting passed to the Matomo server. Why would this happen after 90+ successful additions but now I can’t get 1 site to succeed?

I’m not much of a programmer, but thought I’d run this by the Gurus in here and see if anyone has any ideas?

TIA
James

1 post - 1 participant

Read full topic

A fatal error occurred

The following error just broke Matomo (v4.1.0):

Call to undefined function IP2Location\bcadd()
in /var/www/html/matomo/matomo/plugins/IP2Location/lib/IP2Location.php line 1540

with

IP2Location 4.0.2 deactivate

I’ve just purchased and download the IP2 location database and upload the file : DB1-IPV6-COUNTRY.BIN.ZIP

I’ve got this error message
Call to undefined function IP2Location\bcadd() in /var/www/html/matomo/matomo/plugins/IP2Location/lib/IP2Location.php 1540 using PHP 7.2.34

Maybe, can you please tell me where I can re-install the IP2location plugin ? ( I ca try to re instatll the plugin and add the IP2 location database )

Thanks and regards,

Steve

1 post - 1 participant

Read full topic

Hello,

I’ve configured my website to exclude some query parameters from the url.
Some parameters are excluded but it seems that the first parameter in the URL is not.
Example:
parameter excluded: “aggregation”
URL logged after having exclude the parameter:
https://site.com/#/accounts?aggregation=FOLDER

I can’t reproduce the issue with a classic static html page (without the angular # of the URL) it may be an issue with it ? How can I get pass through it ? (I can’t remove it)

1 post - 1 participant

Read full topic

After i changed my webspace provider i get the error " Error: Segment ‘campaignSource’ is not a supported segment." when i try to filter metrics…

The segment settings used to filter by newsletter clicks (using UTM-Parameters).
Before the server change it worked…

Does anybody know why this is happening?

1 post - 1 participant

Read full topic