Hilfe! Matomo zeigt die Visits in den Graphen nicht mehr an aber sie werden im Visits Log aufgezeichnet

Hallo!

Hier passiert gerade etwas sehr, sehr seltsames: Seit 5 Jahren läuft mein Matomo wunderbar durch. Updates usw. alles kein Problem. Aus heiterem Himmel (ja, heute schneit es ja mal nicht) zeigt Matomo zwar überall die Besuche in den Visits Logs an aber die Graphen für Visits im Dashboard sind alle 0 seit 48 Stunden. Woran kann das liegen? Tracking failures gibt es keine. Es wird ja auch erfolgreich alles im Visitor Log angezeigt. Der cron für die Archivierung läuft auch durch.

INFO CoreAdminHome[2021-02-10 09:03:35 UTC] [c1ac6] ---------------------------
INFO CoreAdminHome[2021-02-10 09:03:35 UTC] [c1ac6] INIT
INFO CoreAdminHome[2021-02-10 09:03:35 UTC] [c1ac6] Running Matomo 4.1.1 as Super User
INFO CoreAdminHome[2021-02-10 09:03:35 UTC] [c1ac6] ---------------------------
INFO CoreAdminHome[2021-02-10 09:03:35 UTC] [c1ac6] NOTES
INFO CoreAdminHome[2021-02-10 09:03:35 UTC] [c1ac6] - Async process archiving not supported, using curl requests.
INFO CoreAdminHome[2021-02-10 09:03:35 UTC] [c1ac6] - Reports for today will be processed at most every 150 seconds. You can change this value in Matomo UI > Settings > General Settings.
INFO CoreAdminHome[2021-02-10 09:03:35 UTC] [c1ac6] - Archiving was last executed without error 2 min 15s ago
INFO CoreAdminHome[2021-02-10 09:03:36 UTC] [c1ac6] - Continuing ongoing archiving run by pulling from shared idSite queue.
INFO CoreAdminHome[2021-02-10 09:03:36 UTC] [c1ac6] ---------------------------
INFO CoreAdminHome[2021-02-10 09:03:36 UTC] [c1ac6] START
INFO CoreAdminHome[2021-02-10 09:03:36 UTC] [c1ac6] Starting Matomo reports archiving...
INFO CoreAdminHome[2021-02-10 09:03:41 UTC] [c1ac6] Start processing archives for site 13.
INFO CoreAdminHome[2021-02-10 09:03:41 UTC] [c1ac6] Will invalidate archived reports for today in site ID = 13's timezone (2021-02-10 00:00:00).
INFO CoreAdminHome[2021-02-10 09:03:41 UTC] [c1ac6] LOAD DATA INFILE failed... Error was: 
    Try #1: LOAD DATA INFILE : SQLSTATE[28000]: Invalid authorization specification: 1045 Access denied for user 'd026d7ba'@'%' (using password: YES)[28000],
    Try #2: LOAD DATA LOCAL INFILE : SQLSTATE[HY000]: General error: 4166 The used command is not allowed because the MariaDB server or client has disabled the local infile capability
INFO CoreAdminHome[2021-02-10 09:03:41 UTC] [c1ac6] LOAD DATA INFILE failed... Error was: 
    Try #1: LOAD DATA INFILE : SQLSTATE[28000]: Invalid authorization specification: 1045 Access denied for user 'd026d7ba'@'%' (using password: YES)[28000],
    Try #2: LOAD DATA LOCAL INFILE : SQLSTATE[HY000]: General error: 4166 The used command is not allowed because the MariaDB server or client has disabled the local infile capability
INFO CoreAdminHome[2021-02-10 09:03:41 UTC] [c1ac6] Will invalidate archived reports for yesterday in site ID = 13's timezone (2021-02-09 00:00:00).
INFO CoreAdminHome[2021-02-10 09:03:41 UTC] [c1ac6] Archived website id 13, period = day, date = 2021-02-10, segment = '', 3 visits found. Time elapsed: 0.462s
INFO CoreAdminHome[2021-02-10 09:03:42 UTC] [c1ac6] Archived website id 13, period = week, date = 2021-02-08, segment = '', 14 visits found. Time elapsed: 0.520s
INFO CoreAdminHome[2021-02-10 09:03:42 UTC] [c1ac6] Archived website id 13, period = month, date = 2021-02-01, segment = '', 80 visits found. Time elapsed: 0.475s
INFO CoreAdminHome[2021-02-10 09:03:43 UTC] [c1ac6] Archived website id 13, period = year, date = 2021-01-01, segment = '', 338 visits found. Time elapsed: 0.533s
INFO CoreAdminHome[2021-02-10 09:03:43 UTC] [c1ac6] Finished archiving for site 13, 4 API requests, Time elapsed: 2.068s [1 / 3 done]
INFO CoreAdminHome[2021-02-10 09:03:48 UTC] [c1ac6] Start processing archives for site 14.
INFO CoreAdminHome[2021-02-10 09:03:48 UTC] [c1ac6] Finished archiving for site 14, 0 API requests, Time elapsed: 0.036s [2 / 3 done]
INFO CoreAdminHome[2021-02-10 09:03:53 UTC] [c1ac6] Start processing archives for site 15.
INFO CoreAdminHome[2021-02-10 09:03:53 UTC] [c1ac6] Finished archiving for site 15, 0 API requests, Time elapsed: 0.003s [3 / 3 done]
INFO CoreAdminHome[2021-02-10 09:03:58 UTC] [c1ac6] Done archiving!
INFO CoreAdminHome[2021-02-10 09:03:58 UTC] [c1ac6] ---------------------------
INFO CoreAdminHome[2021-02-10 09:03:58 UTC] [c1ac6] SUMMARY
INFO CoreAdminHome[2021-02-10 09:03:58 UTC] [c1ac6] Processed 4 archives.
INFO CoreAdminHome[2021-02-10 09:03:58 UTC] [c1ac6] Total API requests: 4
INFO CoreAdminHome[2021-02-10 09:03:58 UTC] [c1ac6] done: 4 req, 22011 ms, no error
INFO CoreAdminHome[2021-02-10 09:03:58 UTC] [c1ac6] Time elapsed: 22.011s
INFO CoreAdminHome[2021-02-10 09:03:58 UTC] [c1ac6] ---------------------------
INFO CoreAdminHome[2021-02-10 09:03:58 UTC] [c1ac6] SCHEDULED TASKS
INFO CoreAdminHome[2021-02-10 09:03:58 UTC] [c1ac6] Starting Scheduled tasks...
INFO CoreAdminHome[2021-02-10 09:03:58 UTC] [c1ac6] done
INFO CoreAdminHome[2021-02-10 09:03:58 UTC] [c1ac6] ---------------------------
Success:ok

Matomo ist aktuell auf 4.1.1.
MySQL version: 10.5.6-MariaDB-1:10.5.6+maria~focal-log
PHP version: 7.4.14

Es wurde nichts geändert meiner Seite. Es ist ein shared hoster. Deswegen weiß ich das natürlich nicht 100%ig.

Hier das Visitis Log mit einem aktuellen Eintrag:

Hier der Graph auf dem Dashboard
Screen Shot 2021-02-10 at 09.18.27

Hallo,

Das klingt ziemlich nach der Ursache des Fehlers. Dein MySQL nutzer hat nicht die Rechte um LOAD DATA INFILE zu verwenden.

Es ist aber seltsam, dass Matomo versucht es zu verwenden, da Matomo eigentlich erkennen sollte, wenn es nicht erlaubt ist und dann eine andere langsamere Möglichkeit verwenden sollte.

Kannst du einmal den System Check öffnen und schauen, ob da etwas zu LOAD DATA INFILE steht

Das wurde noch nie von meinem Server Setup unterstützt, soweit ich weiß.

Last Successful Archiving Completion: :heavy_check_mark: The archiving process completed successfully 00:05:04 ago.

Database abilities: :heavy_check_mark: UTF8mb4 charset :warning: Warning: LOAD DATA INFILE
Using LOAD DATA INFILE will greatly speed Matomo’s archiving process up. To make it available to Matomo, try updating your PHP & MySQL software and make sure your database user has the FILE privilege.
If your Matomo server tracks high traffic websites (eg. > 100,000 pages per month), we recommend trying to fix this problem.
Error: LOAD DATA INFILE failed… Error was:
Try #1: LOAD DATA INFILE : SQLSTATE[28000]: Invalid authorization specification: 1045 Access denied for user ‘d026d7ba’@’%’ (using password: YES)[28000],
Try #2: LOAD DATA LOCAL INFILE : SQLSTATE[HY000]: General error: 4166 The used command is not allowed because the MariaDB server or client has disabled the local infile capability
Troubleshooting: FAQ on matomo.org :heavy_check_mark: CREATE TEMPORARY TABLES :heavy_check_mark: Changing transaction isolation level

Wie stelle ich es ab? Vielleicht gab es ein Update letzte nach von mysql und nun denkt Matomo “Toll, dann nutze ich das mal. Oh geht ja gar nicht!”

Hallo,

Es gibt eine Option, womit man das komplett deaktivieren kann.

Einfach enable_load_data_infile = 0 in den [General] Abschnitt der config/config.ini.php geben.
Das sollte aber eigentlich nie notwendig sein, aber ich habe ehrlich gesagt keine Erklärung, warum es nicht richtig erkannt wird.

1 Like

Danke. Die Meldung ist nun weg. Ich behaupte mal, die war aber schon immer da. Nun sieht es so aus:

INFO CoreAdminHome[2021-02-10 09:45:32 UTC] [0374d] ---------------------------
INFO CoreAdminHome[2021-02-10 09:45:32 UTC] [0374d] INIT
INFO CoreAdminHome[2021-02-10 09:45:32 UTC] [0374d] Running Matomo 4.1.1 as Super User
INFO CoreAdminHome[2021-02-10 09:45:32 UTC] [0374d] ---------------------------
INFO CoreAdminHome[2021-02-10 09:45:32 UTC] [0374d] NOTES
INFO CoreAdminHome[2021-02-10 09:45:32 UTC] [0374d] - Async process archiving not supported, using curl requests.
INFO CoreAdminHome[2021-02-10 09:45:32 UTC] [0374d] - Reports for today will be processed at most every 150 seconds. You can change this value in Matomo UI > Settings > General Settings.
INFO CoreAdminHome[2021-02-10 09:45:32 UTC] [0374d] - Archiving was last executed without error 4 min 9s ago
INFO CoreAdminHome[2021-02-10 09:45:36 UTC] [0374d] - Continuing ongoing archiving run by pulling from shared idSite queue.
INFO CoreAdminHome[2021-02-10 09:45:36 UTC] [0374d] ---------------------------
INFO CoreAdminHome[2021-02-10 09:45:36 UTC] [0374d] START
INFO CoreAdminHome[2021-02-10 09:45:36 UTC] [0374d] Starting Matomo reports archiving...
INFO CoreAdminHome[2021-02-10 09:45:41 UTC] [0374d] Start processing archives for site 8.
INFO CoreAdminHome[2021-02-10 09:45:41 UTC] [0374d] Finished archiving for site 8, 0 API requests, Time elapsed: 0.008s [1 / 7 done]
INFO CoreAdminHome[2021-02-10 09:45:46 UTC] [0374d] Start processing archives for site 12.
INFO CoreAdminHome[2021-02-10 09:45:46 UTC] [0374d] Will invalidate archived reports for today in site ID = 12's timezone (2021-02-10 00:00:00).
INFO CoreAdminHome[2021-02-10 09:45:46 UTC] [0374d] Will invalidate archived reports for yesterday in site ID = 12's timezone (2021-02-09 00:00:00).
INFO CoreAdminHome[2021-02-10 09:45:46 UTC] [0374d] Archived website id 12, period = day, date = 2021-02-10, segment = '', 2 visits found. Time elapsed: 0.445s
INFO CoreAdminHome[2021-02-10 09:45:46 UTC] [0374d] Archived website id 12, period = week, date = 2021-02-08, segment = '', 15 visits found. Time elapsed: 0.490s
INFO CoreAdminHome[2021-02-10 09:45:47 UTC] [0374d] Archived website id 12, period = month, date = 2021-02-01, segment = '', 69 visits found. Time elapsed: 0.467s
INFO CoreAdminHome[2021-02-10 09:45:47 UTC] [0374d] Archived website id 12, period = year, date = 2021-01-01, segment = '', 310 visits found. Time elapsed: 0.477s
INFO CoreAdminHome[2021-02-10 09:45:47 UTC] [0374d] Finished archiving for site 12, 4 API requests, Time elapsed: 1.954s [2 / 7 done]
INFO CoreAdminHome[2021-02-10 09:45:51 UTC] [0374d] Start processing archives for site 14.
INFO CoreAdminHome[2021-02-10 09:45:51 UTC] [0374d] Finished archiving for site 14, 0 API requests, Time elapsed: 0.004s [3 / 7 done]
INFO CoreAdminHome[2021-02-10 09:45:56 UTC] [0374d] Start processing archives for site 15.
INFO CoreAdminHome[2021-02-10 09:45:56 UTC] [0374d] Finished archiving for site 15, 0 API requests, Time elapsed: 0.002s [4 / 7 done]
INFO CoreAdminHome[2021-02-10 09:46:01 UTC] [0374d] Done archiving!
INFO CoreAdminHome[2021-02-10 09:46:01 UTC] [0374d] ---------------------------
INFO CoreAdminHome[2021-02-10 09:46:01 UTC] [0374d] SUMMARY
INFO CoreAdminHome[2021-02-10 09:46:01 UTC] [0374d] Processed 4 archives.
INFO CoreAdminHome[2021-02-10 09:46:01 UTC] [0374d] Total API requests: 4
INFO CoreAdminHome[2021-02-10 09:46:01 UTC] [0374d] done: 4 req, 24963 ms, no error
INFO CoreAdminHome[2021-02-10 09:46:01 UTC] [0374d] Time elapsed: 24.963s
INFO CoreAdminHome[2021-02-10 09:46:01 UTC] [0374d] ---------------------------
INFO CoreAdminHome[2021-02-10 09:46:01 UTC] [0374d] SCHEDULED TASKS
INFO CoreAdminHome[2021-02-10 09:46:01 UTC] [0374d] Starting Scheduled tasks...
INFO CoreAdminHome[2021-02-10 09:46:01 UTC] [0374d] done
INFO CoreAdminHome[2021-02-10 09:46:01 UTC] [0374d] ---------------------------
Success:ok

Allerdings sind selbst nach einigen Reloads die Visits immernoch nicht zu sehen. Also heute ist bei “0”.

Was sagt denn das hier:

INFO CoreAdminHome[2021-02-10 09:48:45 UTC] [5f1d1] Will invalidate archived reports for today in site ID = 3's timezone (2021-02-10 00:00:00).
INFO CoreAdminHome[2021-02-10 09:48:45 UTC] [5f1d1] Will invalidate archived reports for yesterday in site ID = 3's timezone (2021-02-09 00:00:00).

Site id 3 ist meine Hauptseite. Heißt das nicht, dass er gestern und heute ignoriert? Das ist ja genau das Problem.

Ich habe nun nochmal den Check druchlaufen lassen:

Huzzah! There are no problems with your Matomo setup. Give yourself a pat on the back.

Trotzdem wird dort nichts angezeigt. User logs ist aber funktionsfähig. Deswegen bin ich noch recht entspannt.

Hinweis vom Hoster was sich geändert hat:

Was neu ist, ist eben Maria DB, das haben wir auf allen Servern drauf,
macht aber normalerweise keine Probleme, auch der Wechsel nicht.

Niemand? Bin ich der einzige mit dem Problem? Mein Hoster war auch schon so nett und hat “load_data_infile” auch mal aktiviert und ich habe es dann auch mal aktiviert in Matomo. Keine Besserung. Es ist doch sehr komisch, dass die Visits getrackt aber nicht dargstellt werden. Jedenfalls nicht in den Graphen. @Lukas ne Idee?

Eine Frage noch: Siehst du bei allen Seiten keine Daten oder sehen die für idsite=12 richtig aus?

bei siteid 12 läuft kaum was auf aber sie sind zumindest nicht 0, sondern realistisch, ja. Das ist alles nur meine private Webseite http://marc.tv aber trotzdem würde ich gerne wieder meine Zahlen sehen. =)

Aktuelles log:


INFO CoreAdminHome[2021-02-10 17:37:29 UTC] [fffd1] ---------------------------
INFO CoreAdminHome[2021-02-10 17:37:29 UTC] [fffd1] INIT
INFO CoreAdminHome[2021-02-10 17:37:29 UTC] [fffd1] Running Matomo 4.1.1 as Super User
INFO CoreAdminHome[2021-02-10 17:37:29 UTC] [fffd1] ---------------------------
INFO CoreAdminHome[2021-02-10 17:37:29 UTC] [fffd1] NOTES
INFO CoreAdminHome[2021-02-10 17:37:29 UTC] [fffd1] - Async process archiving not supported, using curl requests.
INFO CoreAdminHome[2021-02-10 17:37:29 UTC] [fffd1] - Reports for today will be processed at most every 900 seconds. You can change this value in Matomo UI > Settings > General Settings.
INFO CoreAdminHome[2021-02-10 17:37:29 UTC] [fffd1] - Archiving was last executed without error 1 min 22s ago
INFO CoreAdminHome[2021-02-10 17:37:34 UTC] [fffd1] ---------------------------
INFO CoreAdminHome[2021-02-10 17:37:34 UTC] [fffd1] START
INFO CoreAdminHome[2021-02-10 17:37:34 UTC] [fffd1] Starting Matomo reports archiving...
INFO CoreAdminHome[2021-02-10 17:37:39 UTC] [fffd1] Start processing archives for site 2.
INFO CoreAdminHome[2021-02-10 17:37:39 UTC] [fffd1] Will invalidate archived reports for today in site ID = 2's timezone (2021-02-10 00:00:00).
INFO CoreAdminHome[2021-02-10 17:37:39 UTC] [fffd1] Will invalidate archived reports for yesterday in site ID = 2's timezone (2021-02-09 00:00:00).
INFO CoreAdminHome[2021-02-10 17:37:39 UTC] [fffd1] Finished archiving for site 2, 0 API requests, Time elapsed: 0.014s [1 / 11 done]
INFO CoreAdminHome[2021-02-10 17:37:44 UTC] [fffd1] Start processing archives for site 3.
INFO CoreAdminHome[2021-02-10 17:37:44 UTC] [fffd1] Will invalidate archived reports for today in site ID = 3's timezone (2021-02-10 00:00:00).
INFO CoreAdminHome[2021-02-10 17:37:44 UTC] [fffd1] Will invalidate archived reports for yesterday in site ID = 3's timezone (2021-02-09 00:00:00).
INFO CoreAdminHome[2021-02-10 17:37:44 UTC] [fffd1] Finished archiving for site 3, 0 API requests, Time elapsed: 0.015s [2 / 11 done]
INFO CoreAdminHome[2021-02-10 17:37:49 UTC] [fffd1] Start processing archives for site 4.
INFO CoreAdminHome[2021-02-10 17:37:49 UTC] [fffd1] Will invalidate archived reports for today in site ID = 4's timezone (2021-02-10 00:00:00).
INFO CoreAdminHome[2021-02-10 17:37:49 UTC] [fffd1] Will invalidate archived reports for yesterday in site ID = 4's timezone (2021-02-09 00:00:00).
INFO CoreAdminHome[2021-02-10 17:37:49 UTC] [fffd1] Finished archiving for site 4, 0 API requests, Time elapsed: 0.003s [3 / 11 done]
INFO CoreAdminHome[2021-02-10 17:37:54 UTC] [fffd1] Start processing archives for site 5.
INFO CoreAdminHome[2021-02-10 17:37:54 UTC] [fffd1] Will invalidate archived reports for today in site ID = 5's timezone (2021-02-10 00:00:00).
INFO CoreAdminHome[2021-02-10 17:37:54 UTC] [fffd1] Will invalidate archived reports for yesterday in site ID = 5's timezone (2021-02-09 00:00:00).
INFO CoreAdminHome[2021-02-10 17:37:54 UTC] [fffd1] Finished archiving for site 5, 0 API requests, Time elapsed: 0.002s [4 / 11 done]
INFO CoreAdminHome[2021-02-10 17:37:59 UTC] [fffd1] Start processing archives for site 6.
INFO CoreAdminHome[2021-02-10 17:37:59 UTC] [fffd1] Will invalidate archived reports for today in site ID = 6's timezone (2021-02-10 00:00:00).
INFO CoreAdminHome[2021-02-10 17:37:59 UTC] [fffd1] Will invalidate archived reports for yesterday in site ID = 6's timezone (2021-02-09 00:00:00).
INFO CoreAdminHome[2021-02-10 17:37:59 UTC] [fffd1] Finished archiving for site 6, 0 API requests, Time elapsed: 0.005s [5 / 11 done]
INFO CoreAdminHome[2021-02-10 17:38:04 UTC] [fffd1] Start processing archives for site 8.
INFO CoreAdminHome[2021-02-10 17:38:04 UTC] [fffd1] Finished archiving for site 8, 0 API requests, Time elapsed: 0.002s [6 / 11 done]
INFO CoreAdminHome[2021-02-10 17:38:09 UTC] [fffd1] Start processing archives for site 9.
INFO CoreAdminHome[2021-02-10 17:38:09 UTC] [fffd1] Will invalidate archived reports for today in site ID = 9's timezone (2021-02-10 00:00:00).
INFO CoreAdminHome[2021-02-10 17:38:09 UTC] [fffd1] Will invalidate archived reports for yesterday in site ID = 9's timezone (2021-02-09 00:00:00).
INFO CoreAdminHome[2021-02-10 17:38:09 UTC] [fffd1] Finished archiving for site 9, 0 API requests, Time elapsed: 0.003s [7 / 11 done]
INFO CoreAdminHome[2021-02-10 17:38:14 UTC] [fffd1] Start processing archives for site 12.
INFO CoreAdminHome[2021-02-10 17:38:14 UTC] [fffd1] Will invalidate archived reports for today in site ID = 12's timezone (2021-02-10 00:00:00).
INFO CoreAdminHome[2021-02-10 17:38:14 UTC] [fffd1] Will invalidate archived reports for yesterday in site ID = 12's timezone (2021-02-09 00:00:00).
INFO CoreAdminHome[2021-02-10 17:38:14 UTC] [fffd1] Finished archiving for site 12, 0 API requests, Time elapsed: 0.002s [8 / 11 done]
INFO CoreAdminHome[2021-02-10 17:38:19 UTC] [fffd1] Start processing archives for site 13.
INFO CoreAdminHome[2021-02-10 17:38:19 UTC] [fffd1] Will invalidate archived reports for today in site ID = 13's timezone (2021-02-10 00:00:00).
INFO CoreAdminHome[2021-02-10 17:38:19 UTC] [fffd1] Will invalidate archived reports for yesterday in site ID = 13's timezone (2021-02-09 00:00:00).
INFO CoreAdminHome[2021-02-10 17:38:19 UTC] [fffd1] Finished archiving for site 13, 0 API requests, Time elapsed: 0.003s [9 / 11 done]
INFO CoreAdminHome[2021-02-10 17:38:24 UTC] [fffd1] Start processing archives for site 14.
INFO CoreAdminHome[2021-02-10 17:38:24 UTC] [fffd1] Finished archiving for site 14, 0 API requests, Time elapsed: 0.002s [10 / 11 done]
INFO CoreAdminHome[2021-02-10 17:38:29 UTC] [fffd1] Start processing archives for site 15.
INFO CoreAdminHome[2021-02-10 17:38:29 UTC] [fffd1] Finished archiving for site 15, 0 API requests, Time elapsed: 0.002s [11 / 11 done]
INFO CoreAdminHome[2021-02-10 17:38:34 UTC] [fffd1] Done archiving!
INFO CoreAdminHome[2021-02-10 17:38:34 UTC] [fffd1] ---------------------------
INFO CoreAdminHome[2021-02-10 17:38:34 UTC] [fffd1] SUMMARY
INFO CoreAdminHome[2021-02-10 17:38:34 UTC] [fffd1] Processed 0 archives.
INFO CoreAdminHome[2021-02-10 17:38:34 UTC] [fffd1] Total API requests: 0
INFO CoreAdminHome[2021-02-10 17:38:34 UTC] [fffd1] done: 0 req, 59998 ms, no error
INFO CoreAdminHome[2021-02-10 17:38:34 UTC] [fffd1] Time elapsed: 59.998s
INFO CoreAdminHome[2021-02-10 17:38:34 UTC] [fffd1] ---------------------------
INFO CoreAdminHome[2021-02-10 17:38:34 UTC] [fffd1] SCHEDULED TASKS
INFO CoreAdminHome[2021-02-10 17:38:34 UTC] [fffd1] Starting Scheduled tasks...
INFO CoreAdminHome[2021-02-10 17:38:34 UTC] [fffd1] done
INFO CoreAdminHome[2021-02-10 17:38:34 UTC] [fffd1] ---------------------------
Success:ok

Hi MarcDK.
Ich habe das Problem auch. Hatte ein paar Tage nich drauf geschaut, aber als ich eben refreshed habe, sind die letzten Tage auf 0 (obwohl sie das vorher nicht waren).

@pfm

Und du hast auch visitors im visitor log?

@MarcDK
Ja. Und habe sie bis Montag auch in der Verdichtung gesehen. Nach einem Browser Refresh fehlen die Tageswerte für in Teilen ab dem 02.02. und komplett vom 03.-09.02.

Und hast du das Problem nach wie vor noch?

Oder anders gefragt: gibt es denn nun einen Lösungsansatz?

Niemand? Also ich bin schon etwas enttäuscht von der Resonanz in dieser Community. Offensichtlich gibt es noch eine Person mit dem Problem. Und im Netz findet man auch Hinweise auf das Problem. Allerdings immer mit der Lösung „warten“. Gibt es denn keine Stelle wo man ein log einsehen kann bezüglich. Fehlern?

Hallo,

Ich empfehle einmal den cronjob mit -vvv aufzurufen. Dann sollte man deutlich mehr Informationen bekommen.

Der cron ruft doch nur diese URL auf:

https://xxxx/misc/cron/archive.php?token_auth=xxx

Ich sehe auch, dass er diese URL erfolgreich aufruft, weil Matomo mir sagt, dass der cron erfolgreich durchläuft. Das sieht man auch, wenn man die archive.php manuell aufruft.

Ja @MarcDK ich habe das Problem noch. Habe versucht die blob und numeric zu löschen. Sind zwar neu aufgebaut worden, aber ohne die entsprechenden Tage.

Hallo Marc

Ich denke, ich habe dasselbe Problem:

Gibt es deinerseits schon eine Lösung?
Wie kann ich das Visitor Log ansehen?

Gruss,

Benno

…komischerweise funktioniert seit gestern Nacht alles wieder!