-
Notifications
You must be signed in to change notification settings - Fork 14
Description
Sometimes, every 1-3 days, a random bot access causes large number of such log entries:
| WARNING | API | 2021-06-20 23:20:02 UTC | 18606 | /var/www/matomo/core/DataTable/Row.php(772): Trying to add two strings in DataTable\Row::sumRowArray: GoogleBot + Google Instant for column botName in row # ['label' => -1, 'botId' => 9, 'idsite' => 2, 'botName' => 'GoogleBot', 'botKeyword' => 'Googlebot', 'botCount' => 5, 'botLastVisit' => '2021-05-20 16:36:44', 'extra_stats' => 1] [] [idsubtable = ] |
|---|
...
| WARNING | API | 2021-06-20 23:20:02 UTC | c3618 | /var/www/matomo/core/DataTable/Row.php(772): Trying to add two strings in DataTable\Row::sumRowArray: 0 + 2021-05-24 02:09:13 for column botLastVisit in row # ['label' => -1, 'botId' => 735, 'idsite' => 35, 'botName' => 0, 'botActive' => 35, 'botKeyword' => 0, 'botCount' => 501, 'botLastVisit' => 0, 'extra_stats' => 34] [] [idsubtable = ] |
|---|
Those are the first and the last of such entries, framing a three-digits number of such logs, like once for each bot and each column/field. As can be seen, somehow two neighbour field values are somehow tried to be added to a single field and another field may hence be empty (botActive in first log). And then values seem to be shifted, to get a 'botId' => 735 and 'idsite' => 35, which both do not exist (also not in the raw database), so even the logging itself seems to mix something up.
First I though it might happen when the BotTracker settings are saved, as then all those database entries are written, but neither could I find an issue in the related code, nor could I replicate it. The log error instead appears independently of settings changes and repeatedly without touching settings.
Most likely it has something to do with PHP8.0 and I'm not sure if the Matomo archive CLI/cron job may be involved, if it includes archiving the current BotTracker data and does something wrong there? The database itself btw looks pretty fine, no errors no suspicious entries. The extended stats table is not affected by this.