Hi,
although I’m not sure if the specific issues within these libraries are used within Matomo, it would help security posture to always use the most recent (stable) versions of libraries used by Matomo.
Can this be made part of the standard Matomo updates?
Kind regards,
Ties Voskamp
3 posts - 2 participants
After upgrading to Matomo v4 beta, we get the following errors, not often, but regularly a few times a day amount ~5000 visits:
[proxy_fcgi:error] [pid 2527369:tid 140305038833408] [client XX.YY.ZZ.AA:61674] AH01071: Got error 'PHP message: Error in Matomo (tracker): Error query: Mysqli statement execute error : Out of range value for column 'time_transfer' at row 1
In query: INSERT INTO matomo_log_link_visit_action (idvisit, idsite, idvisitor, idaction_url, idaction_url_ref, idaction_name_ref, server_time, idpageview, pageview_position, time_spent_ref_action, time_dom_processing, time_network, time_on_load, time_server, time_transfer, idaction_name) VALUES (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)
Parameters: array ( 0 => 92267, 1 => 1, 2 => '\x87\x97x\x1c\x90p\xf5\xb6', 3 => 3, 4 => 136, 5 => 135, 6 => '2020-10-03 17:11:52', 7 => 'b0hNhc', 8 => 4, 9 => 1389, 10 => 21, 11 => 91, 12 => NULL, 13 => 122, 14 => -212, 15 => 2, )', referer: https://XXX.YYY/
I guess some database tables have not been migrated correctly but the CLI says that all is up-to-date. I recognised before that tables from disabled plugins are not migrated but still accessed, causing errors. But at least for this table column time_transfer I cannot find the related plugin and the local + server time plugin is enabled anyway. Anyone has an idea?
1 post - 1 participant
Missing file: /var/www/matomo/plugins/CustomVariables/.github/workflows/translations.yml
Missing file: /var/www/matomo/plugins/CustomVariables/plugin.json
Missing file: /var/www/matomo/plugins/CustomVariables/README.md
Missing file: /var/www/matomo/plugins/Provider/.github/workflows/translations.yml
Missing file: /var/www/matomo/plugins/Provider/plugin.json
Missing file: /var/www/matomo/plugins/Provider/README.md
Missing file: /var/www/matomo/plugins/Provider/screenshots/Report.png
From what I found, both plugins have been removed from core and as well the Provider plugin seems to not work anymore (I cannot the Provider info in the UI anymore). Strangely, after I uninstalled those plugins, the integrity check misses the above files.
This PR seems to be somehow related? https://github.com/matomo-org/matomo/pull/16415
4 posts - 2 participants
Since update to Matomo v4 beta, when changing the Times plugins data view from vertical bars to simple table, every attempt to change it back to vertical bars (or cake or anything else) causes this error:
[proxy_fcgi:error] [pid 2527367:tid 140304871044864] [client 123.456.789.123:9448] AH01071: Got error 'PHP message: Error in Matomo: Setting parameters rows_to_display is not allowed. Please report this bug to the Matomo team.', referer: https://mydomain.com/matomo/index.php?module=CoreHome&action=index&idSite=1&period=range&date=last7
The view changes, but when I browse to another tap and back to “Times”, both views are reverted to simple tables.
I should probably open a new issue, but additionally I cannot remove any metric from any (not just Times plugin) plot. I can select an additional metric, but hitting the tick icon does not remove the metric anymore.
1 post - 1 participant
一般設定から
ブラウザに表示されたレポートをアーカイブする→いいえにチェック
約 X 秒ごとにレポートをアーカイブする→3600
に変更したら、critical issues が検知されましたというエラーがでました
core:archive コンソールコマンドを呼び出すcrontabを設定したこと、およびアーカイブが失敗した場合に電子メールでエラーを受信するように MAILTO を設定したことを確認してください。 手動でレポートをアーカイブするために console コマンドを実行してみることもできます： /home/XXXXX（サーバー名）/XXXXXXX.com（サイトドメイン）/public_html/matomo --matomo-domain=XXXXX.com（サイトドメイン） core:archive
というのが赤く出ているのですが、どうしればいいのでしょうか？
2 posts - 2 participants
Hi,
This is an example output for our archiving:
DEBUG [2020-10-04 08:03:18] 1 process_new_segments_from set to segment_creation_time, oldest date to process is 2020-08-26
DEBUG [2020-10-04 08:03:18] 1 Start date of archiving request period (2015-10-12) is older than configured oldest date to process for the segment.
DEBUG [2020-10-04 08:03:18] 1 Archiving request date range changed to 2020-08-26,2020-10-04 w/ period week.
INFO [2020-10-04 08:03:19] 1 Will pre-process for website id = 1, period = week, date = last260
First, " Start date of archiving request period (2015-10-12)". Where does this date come from? There is no data from that date - our Matomo setup for this client were setup in march 2019 - and no old logs have been imported.
And “Archiving request date range changed to 2020-08-26,2020-10-04” <= this does not make sense together with the rest of the debug output.
1 post - 1 participant
Hallo zusammen,
ich habe folgendes Problem mit der durchschnittlichen Verweildauer.
Wenn ich in die Datenanalyse einsteige, ziehe ich mir immer Seiten heraus, die z.B. eine hohe Absprungrate haben und eine hohe Verweildauer. In dieses Muster fallen meistens Seiten, mit denen sich der Nutzer beschäftigt - aber ihn keine weiteren Themen mehr interessieren. Klassisch News-Artikel - Interesse - lesen - und weg.
Die durchschnittliche Veweildauer pro URL wird in Matomo aber anders berechnet als in Google Analytics. In Google Analytics werden die Absprünge nicht in den Durchschnitt einbezogen. Bei Abspüngen wird ja im Default die Verweildauer auf 00:00:00 gesetzt. Ich habe hier nun mal folgenden Screenshot:
Ich habe mir also Segmente angelegt und die Besucher gesplittet. Die Visits die abgesprungen sind (5 Einstiege), zeigen die 0 Sekunden an. Die Besucher die weiter navigiert oder halt durch navigiert sind, haben eine Dauer von 1:30 erzeugt (24 Aufrufe).
Gehe ich nun über alle Besucher, ist die durchschnittliche Dauer auch 1:30.
Sprich die Dauer der 24 Ansichten entspricht der Dauer der 29 Ansichten.
Matomo
Gleiches habe ich nun in Matomo durchgespielt.
Dazu habe ich mir eine Seite herausgepickt und im Besucherlog die Daten betrachtet.
Hier habe ich also in der Summe eine Verweildauer von 63 Sekunden
Diese wird nun durch 7 geteilt und es kommt ein Wert von 9 Sekunden heraus.
In der Berechnung werden also die Besucher die abgesprungen sind mit einkalkuliert.
Auf diesem Screenshot sieht man, dass bei den Seitenaufrufen mit Verweildauer im Schnitt 12 Sekunden vorhanden sind. Über alle Besucher habe ich nur 9.
Ich hätte eigentlich erwartet, dass diese beiden Werte gleich sind.
Das ist jetzt nur exemplarisch. Ich kann gerne noch andere Bespiele aufzeigen.
@Lukas @peterbo
Habe ich einen Denkfehler ?
1 post - 1 participant
Hallo,
wir haben seit längerem das Problem das Nutzer nach der Nutzung von Administrationsseiten abgemeldet werden. Richten sich die Nutzer zum Beispiel einen Mailversand ein werden sie nach dem Speichern abgemeldet und aufgefordert sich neu anzumelden. Das geschieht Browser unabhängig und immer mit der Fehlermeldung Time Out wegen Inaktivität.
Wir nutzen das LDAP Plugin und hatten damit bisher keine Probleme.
Kennt jemand das Problem bzw. weiß woran das liegen könnte?
VG Ortwin
1 post - 1 participant
I have been trying to get Matomo to work in my angular project, and it seems to be doing everything right at first, triggering trackPageView and delivering the information to our matomo overview, but when I change page and it calls trackPageView again, the script never terminates, and I can’t figure out why.
In the amtomo.min.js it reaches “push: af ()” and never gets any further.
I am using angular 6 and ngx-matomo 0.1.4.
I am having the same issue when I try accessing window[’_paq’] directly instead of going through ngx-matomo
Please let me know which other information you might need to help troubleshoot this issue.
8 posts - 2 participants
Hi there,
I want to combine two matomo installation into a combined system, I’ve already found some migration docs and plugins but have not been clear here.
Situation:
We have currently two installation (olddomain.com/piwik and newdomain.com/matomo) both systems are productive. In the old installation we still have a few important websites, so I want to move the websites - including all history data - to the new installation.
The change of the embedded code is not the issue, but we need the historical data also in the new matomo installation.
Thanks for your help in advance.
Michael
2 posts - 2 participants
When a user is logged out in our system, we do expect Matomo to reset its context, so when you log in with another user, new context is tracked.
This is well documented to use resetUserId.
But it seems for me, customDimensions are still stored and will be send after, if not overridden on login.
For this use case it would be nice to offer a similar war to resetAllCustomDimensions, so I dont need to list all dimensions, as its error prone with existing
_paq.push([‘deleteCustomDimension’, customDimensionId]);
Is it correct, that resetting dimensions makes sense from your point of view the same way resetUserId does?
1 post - 1 participant
I’m trying a fresh installation of Matomo 4 beta2.
The following error pops up during database creation
My default collation is utf8_unicode_ci, matomo creates tables as utf8mb4_general_ci. The engine used is InnoDB.
Some settings:
innodb_large_prefix ON
innodb_file_format Barracuda
innodb_file_format_check ON
innodb_file_format_max Barracuda
innodb_file_per_table ON
The installscript does not complain about my environment.
Any suggestions?
1 post - 1 participant
Hi,
I am currently struggling with some events that appear in Matomo from an earlier version of the Tag Manager.
I took over an existing website and the tracking from Tag Manager.
But due to some weird tags and variables I deleted the existing tags and variables and rolled out a new version which is currently only collecting pageviews.
But still I can see every day events incoming from one of the early tracking setup.
Does it mean that there is somehow still the old container version cached or the page is not re-loaded and some bot traffic is pushing the events?
In general I would say the amount of old / deprecated events already decreased but somehow it is not clearing up…
1 post - 1 participant
Hello everyone,
Trying to set up Matomo for use with virtual trade show booth tracking. I’m trying to establish a way to get the visitors name and email through a simple Bootstrap Modal that pops up when you visit. I see the User ID docs make this sound possible but I’ve also been trying to dust off my minimal coding skills so can’t figure out exactly how to make it work.
The form is part of the page but can anyone provide the code necessary to make that form push the name and email to the Matomo visitor record? Possibly have the email be the user ID and their name be a custom variable?
Thanks in advance!
1 post - 1 participant
Described at https://matomo.org/faq/how-to/#faq_187, you should force new visit AFTER user was logged in. As different user will be redirected to different home pages, It would be easier for us to call it everytime the login page is opened and after login on any page rendered we trigger setUserId afterwards.
To track the userId, we make use of customDimension userId as well, because with the described flow, the userId will be a random one in Matomo and not the one sent to Matomo, at the same time it matches 1:1 to the one, which is sent afterwards.
Does this flow and solution is recommended as well, or is there any issue with it?
Btw. it whould be nice to attach some flow diagram about possible options how to setup matomo for user logged-in applications. Right now, information is spreaded across multiple documentation pages.
1 post - 1 participant
I have the following set up as a cron job as per Matomo documentation.
php xxx.xxx.ca/console core:archive --url=https://traffic.umintmed.ca/ > matomo_archive_log
For the last few days I intermittently get errors from this.
Sometimes the errors are just a single
sh: fork: retry: Resource temporarily unavailable
and sometimes there are two.
What do I do to fix this?
At least once there was a lot more info:
ERROR [2020-10-07 00:05:09] 17403 Error unserializing the following response from ?module=API&method=API.get&idSite=1&period=month&date=last2&format=php&trigger=archivephp: sh: fork: retry: Resource temporarily unavailable a:2:{s:7:"2020-09";a:64:{s:16:"nb_uniq_visitors";d:81;s:9:"nb_visits";d:82;s:8:"nb_users";i:0;s:10:"nb_actions";d:105;s:11:"max_actions";d:6;s:12:"bounce_count";d:71;s:16:"sum_visit_length";d:3002;s:13:"nb_visits_new";d:78;s:14:"nb_actions_new";d:98;s:20:"nb_uniq_visitors_new";d:78;s:12:"nb_users_new";i:0;s:15:"max_actions_new";d:6;s:15:"bounce_rate_new";s:3:"87%";s:24:"nb_actions_per_visit_new";d:1.3;s:20:"avg_time_on_site_new";d:33;s:19:"nb_visits_returning";d:4;s:20:"nb_actions_returning";d:7;s:26:"nb_uniq_visitors_returning";d:4;s:18:"nb_users_returning";i:0;s:21:"max_actions_returning";d:4;s:21:"bounce_rate_returning";s:3:"75%";s:30:"nb_actions_per_visit_returning";d:1.8;s:26:"avg_time_on_site_returning";d:116;s:35:"Referrers_visitorsFromSearchEngines";i:60;s
:36:"Referrers_visitorsFromSocialNetworks";i:0;s:33:"Referrers_visitorsFromDirectEntry";i:4;s:30:"Referrers_visitorsFromWebsites";i:18;s:31:"Referrers_visitorsFromCampaigns";i:0;s:31:"Referrers_distinctSearchEngines";d:2;s:32:"Referrers_distinctSocialNetworks";i:0;s:26:"Referrers_distinctKeywords";d:2;s:26:"Referrers_distinctWebsites";d:3;s:30:"Referrers_distinctWebsitesUrls";d:11;s:27:"Referrers_distinctCampaigns";i:0;s:41:"Referrers_visitorsFromDirectEntry_percent";s:2:"4%";s:43:"Referrers_visitorsFromSearchEngines_percent";s:3:"56%";s:39:"Referrers_visitorsFromCampaigns_percent";s:2:"0%";s:44:"Referrers_visitorsFromSocialNetworks_percent";s:2:"0%";s:38:"Referrers_visitorsFromWebsites_percent";s:3:"17%";s:14:"nb_conversions";i:0;s:19:"nb_visits_converted";i:0;s:7:"revenue";i:0;s:15:"conversion_rate";s:2:"0%";s:24:"nb_conversions_new_visit";i:0;s:29:"nb_visits_converted_new_visit";i:0;s:17:"revenue_new_visit";i:0;s:25:"conversion_rate_new_visit";s:2:"0%";s:30:"nb_conversions_return
ing_visit";i:0;s:35:"nb_visits_converted_returning_visit";i:0;s:23:"revenue_returning_visit";i:0;s:31:"conversion_rate_returning_visit";s:2:"0%";s:12:"nb_pageviews";d:104;s:17:"nb_uniq_pageviews";d:101;s:12:"nb_downloads";i:0;s:17:"nb_uniq_downloads";i:0;s:11:"nb_outlinks";i:0;s:16:"nb_uniq_outlinks";i:0;s:11:"nb_searches";d:1;s:11:"nb_keywords";d:1;s:28:"nb_hits_with_time_generation";d:97;s:19:"avg_time_generation";d:0.912;s:11:"bounce_rate";s:3:"87%";s:20:"nb_actions_per_visit";d:1.3;s:16:"avg_time_on_site";d:37;}s:7:"2020-10";a:64:{s:16:"nb_uniq_visitors";d:26;s:9:"nb_visits";d:26;s:8:"nb_users";i:0;s:10:"nb_actions";d:31;s:11:"max_actions";d:3;s:12:"bounce_count";d:22;s:16:"sum_visit_length";d:222;s:13:"nb_visits_new";d:25;s:14:"nb_actions_new";d:28;s:20:"nb_uniq_visitors_new";d:25;s:12:"nb_users_new";i:0;s:15:"max_actions_new";d:2;s:15:"bounce_rate_new";s:3:"88%";s:24:"nb_actions_per_visit_new";d:1.1;s:20:"avg_time_on_site_new";d:4;s:19:"nb_visits_returning";d:1;s:20:"nb_action
s_returning";d:3;s:26:"nb_uniq_visitors_returning";d:1;s:18:"nb_users_returning";i:0;s:21:"max_actions_returning";d:3;s:21:"bounce_rate_returning";s:2:"0%";s:30:"nb_actions_per_visit_returning";d:3;s:26:"avg_time_on_site_returning";d:133;s:35:"Referrers_visitorsFromSearchEngines";i:12;s:36:"Referrers_visitorsFromSocialNetworks";i:0;s:33:"Referrers_visitorsFromDirectEntry";i:12;s:30:"Referrers_visitorsFromWebsites";i:2;s:31:"Referrers_visitorsFromCampaigns";i:0;s:31:"Referrers_distinctSearchEngines";d:2;s:32:"Referrers_distinctSocialNetworks";i:0;s:26:"Referrers_distinctKeywords";d:1;s:26:"Referrers_distinctWebsites";d:1;s:30:"Referrers_distinctWebsitesUrls";d:2;s:27:"Referrers_distinctCampaigns";i:0;s:41:"Referrers_visitorsFromDirectEntry_percent";s:3:"11%";s:43:"Referrers_visitorsFromSearchEngines_percent";s:3:"11%";s:39:"Referrers_visitorsFromCampaigns_percent";s:2:"0%";s:44:"Referrers_visitorsFromSocialNetworks_percent";s:2:"0%";s:38:"Referrers_visitorsFromWebsites_percent";s:2:"
2%";s:14:"nb_conversions";i:0;s:19:"nb_visits_converted";i:0;s:7:"revenue";i:0;s:15:"conversion_rate";s:2:"0%";s:24:"nb_conversions_new_visit";i:0;s:29:"nb_visits_converted_new_visit";i:0;s:17:"revenue_new_visit";i:0;s:25:"conversion_rate_new_visit";s:2:"0%";s:30:"nb_conversions_returning_visit";i:0;s:35:"nb_visits_converted_returning_visit";i:0;s:23:"revenue_returning_visit";i:0;s:31:"conversion_rate_returning_visit";s:2:"0%";s:12:"nb_pageviews";d:31;s:17:"nb_uniq_pageviews";d:30;s:12:"nb_downloads";i:0;s:17:"nb_uniq_downloads";i:0;s:11:"nb_outlinks";i:0;s:16:"nb_uniq_outlinks";i:0;s:11:"nb_searches";i:0;s:11:"nb_keywords";i:0;s:28:"nb_hits_with_time_generation";d:30;s:19:"avg_time_generation";d:1.08;s:11:"bounce_rate";s:3:"85%";s:20:"nb_actions_per_visit";d:1.2;s:16:"avg_time_on_site";d:9;}}
ERROR [2020-10-07 00:05:30] 17403 Got invalid response from API request: ?module=API&method=API.get&idSite=4&period=month&date=last2&format=php&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 [2020-10-07 00:05:36] 17403 2 total errors during this script execution, please investigate and try and fix these errors.
ERROR [2020-10-07 00:05:36] 17403 Uncaught exception: /home/xxx/xxx.xxx.ca/core/CronArchive.php(606): 2 total errors during this script execution, please investigate and try and fix these errors.
2 total errors during this script execution, please investigate and try and fix these errors.
#0 /home/xxx/xxx.xxx.ca/core/CronArchive.php(599): Piwik\CronArchive->logFatalError('2 total errors ...')
#1 /home/xxx/xxx.xxx.ca/core/CronArchive.php(331): Piwik\CronArchive->end()
#2 /home/xxx/xxx.xxx.ca/core/Access.php(635): Piwik\CronArchive->Piwik\{closure}()
#3 /home/xxx/xxx.xxx.ca/core/CronArchive.php(335): Piwik\Access::doAsSuperUser(Object(Closure))
#4 /home/xxx/xxx.xxx.ca/plugins/CoreConsole/Commands/CoreArchiver.php(27): Piwik\CronArchive->main()
#5 /home/xxx/xxx.xxx.ca/vendor/symfony/console/Symfony/Component/Console/Command/Command.php(257): Piwik\Plugins\CoreConsole\Commands\CoreArchiver->execute(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#6 /home/xxx/xxx.xxx.ca/vendor/symfony/console/Symfony/Component/Console/Application.php(874): Symfony\Component\Console\Command\Command->run(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#7 /home/xxx/xxx.xxx.ca/vendor/symfony/console/Symfony/Component/Console/Application.php(195): Symfony\Component\Console\Application->doRunCommand(Object(Piwik\Plugins\CoreConsole\Commands\CoreArchiver), Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#8 [internal function]: Symfony\Component\Console\Application->doRun(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#9 /home/xxx/xxx.xxx.ca/core/Console.php(140): call_user_func(Array, Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#10 /home/xxx/xxx.xxx.ca/core/Access.php(644): Piwik\Console->Piwik\{closure}()
#11 /home/xxx/xxx.xxx.ca/core/Console.php(141): Piwik\Access::doAsSuperUser(Object(Closure))
#12 /home/xxx/xxx.xxx.ca/core/Console.php(93): Piwik\Console->doRunImpl(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#13 /home/xxx/xxx.xxx.ca/vendor/symfony/console/Symfony/Component/Console/Application.php(126): Piwik\Console->doRun(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#14 /home/xxx/xxx.xxx.ca/console(32): Symfony\Component\Console\Application->run()
#15 {main}
[Exception]
2 total errors during this script execution, please investigate and try and fix these errors.
core:archive [--url="..."] [--force-all-websites] [--force-all-periods[="..."]] [--force-timeout-for-periods[="..."]] [--skip-idsites[="..."]] [--skip-all-segments] [--force-idsites[="..."]] [--skip-segments-today] [--force-periods[="..."]] [--force-date-last-n="..."] [--force-date-range[="..."]] [--force-idsegments="..."] [--concurrent-requests-per-website[="..."]] [--concurrent-archivers[="..."]] [--disable-scheduled-tasks] [--accept-invalid-ssl-certificate] [--php-cli-options[="..."]]
1 post - 1 participant
Matomo 3.14.1
PHP 7.4.11
ERROR [2020-10-07 08:52:24] 2560 Uncaught exception: /opt/matomo/matomo/core/Segment.php(184): Segment ‘dimension4’ is not a supported segment.
Segment ‘dimension4’ is not a supported segment.
#0 /opt/matomo/matomo/core/Segment.php(227): Piwik\Segment->getSegmentByName(‘dimension4’)
#1 /opt/matomo/matomo/core/Segment.php(204): Piwik\Segment->getExpressionsWithUnionsResolved(Array)
#2 /opt/matomo/matomo/core/Segment.php(137): Piwik\Segment->initializeSegment(‘dimension4==4.1…’, Array)
#3 /opt/matomo/matomo/core/CronArchive.php(1004): Piwik\Segment->__construct(‘dimension4==4.1…’, Array)
#4 /opt/matomo/matomo/core/CronArchive.php(2029): Piwik\CronArchive->isThereAValidArchiveForPeriod(‘8’, ‘day’, ‘last2’, ‘dimension4==4.1…’)
#5 [internal function]: Piwik\CronArchive->Piwik{closure}()
#6 /opt/matomo/matomo/core/Archiver/Request.php(45): call_user_func(Object(Closure))
#7 /opt/matomo/matomo/core/CliMulti.php(137): Piwik\Archiver\Request->start()
#8 /opt/matomo/matomo/core/CliMulti.php(418): Piwik\CliMulti->start(Array)
#9 /opt/matomo/matomo/core/CliMulti.php(94): Piwik\CliMulti->requestUrls(Array)
#10 /opt/matomo/matomo/core/CronArchive.php(1179): Piwik\CliMulti->request(Array)
#11 /opt/matomo/matomo/core/CronArchive.php(973): Piwik\CronArchive->archiveReportsFor(‘8’, ‘day’, ‘last2’, true, Object(Piwik\Timer), 11160, 39285)
#12 /opt/matomo/matomo/core/CronArchive.php(730): Piwik\CronArchive->processArchiveDays(‘8’, ‘1602053598’, true, Object(Piwik\Timer))
#13 /opt/matomo/matomo/core/CronArchive.php(519): Piwik\CronArchive->archiveSingleSite(‘8’, 0)
#14 /opt/matomo/matomo/core/CronArchive.php(329): Piwik\CronArchive->run()
#15 /opt/matomo/matomo/core/Access.php(635): Piwik\CronArchive->Piwik{closure}()
#16 /opt/matomo/matomo/core/CronArchive.php(335): Piwik\Access::doAsSuperUser(Object(Closure))
#17 /opt/matomo/matomo/plugins/CoreConsole/Commands/CoreArchiver.php(27): Piwik\CronArchive->main()
#18 /opt/matomo/matomo/vendor/symfony/console/Symfony/Component/Console/Command/Command.php(257): Piwik\Plugins\CoreConsole\Commands\CoreArchiver->execute(nent\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#19 /opt/matomo/matomo/vendor/symfony/console/Symfony/Component/Console/Application.php(874): Symfony\Component\Console\Command\Command->run(Object(Symfonynput\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#20 /opt/matomo/matomo/vendor/symfony/console/Symfony/Component/Console/Application.php(195): Symfony\Component\Console\Application->doRunCommand(Object(Piole\Commands\CoreArchiver), Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#21 [internal function]: Symfony\Component\Console\Application->doRun(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\O)
#22 /opt/matomo/matomo/core/Console.php(140): call_user_func(Array, Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Out
#23 /opt/matomo/matomo/core/Access.php(644): Piwik\Console->Piwik{closure}()
#24 /opt/matomo/matomo/core/Console.php(141): Piwik\Access::doAsSuperUser(Object(Closure))
#25 /opt/matomo/matomo/core/Console.php(93): Piwik\Console->doRunImpl(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\O)
#26 /opt/matomo/matomo/vendor/symfony/console/Symfony/Component/Console/Application.php(126): Piwik\Console->doRun(Object(Symfony\Component\Console\Input\Amfony\Component\Console\Output\ConsoleOutput))
#27 /opt/matomo/matomo/console(32): Symfony\Component\Console\Application->run()
#28 {main}
[Exception]
Segment ‘dimension4’ is not a supported segment.
1 post - 1 participant
Thank you for Matomo:) I am using the on-premise version.
Annotations provide us with very useful insight into the ‘visits over time.’
Is there a way to include annotations into the export results (I use JSON)?
Thanks & regards,
Erik
1 post - 1 participant
Da der Provider bei dem ich bislang Matomo für meine 5 Webprojekte installiert hatte sein Geschäft aufgibt, habe ich Matomo nun auf einem anderen Server installiert.
Bei einer wirklich großen Joomla Seite (klassik-resampled. de) und zwei einfachen HTML-Seiten (robert-kahn. de und beethoven.resampled. de) war das überhaupt kein Problem.
Die Seite
http://composer.resampled.de
mit einigen hundert html-Seiten und
die eigentlich sehr schlichte
http://s-fahl.de
mit gerade mal 4 html Seiten
bekommen dagegen neuerdings keine Verbindung zu Matomo hin, obwohl alle Seiten auf dem selbven Webspace bei dem selben Provder liegen. und ich wie bei drei den funkionierenden auch bei den nicht funktionierenden überall den in Matomo ausgegebenen neuen Tracking code an die Stelle des vorherigen Pwik/Matomo Tracking code gesetzt habe.
Bei diesen beiden Seiten sagt Matomo momentan nur
“Es wurden bisher noch keine Daten gesammelt, untenstehendes Setup beachten”
Das ist insofern eigenartig, als alle 5 Webseiten bis gestern von der Matomo-Installation auf dem alten server problemlos getrackt wurden.
Vielleicht mag ja der eine oder andere da mal im Quelltext nachsehen ob ihm was einfällt, wo das Problem liegen könnte.
4 posts - 2 participants
