While upgrading through automatic update to Matomo 3.8.0-b4, from 3.8.0b3, I have got this message :
""Error in Matomo: Mysqli prepare error: Table 'piwik.piwik_brute_force_log' doesn't exist" while reading response header from upstream, client: xxx.xxx.xxx.xxx, server: domain.tld, request: "POST /index.php?module=CoreUpdater&action=oneClickResults HTTP/2.0", upstream: "fastcgi://unix:/var/php-nginx/xxxxxxxx.sock/socket:", host: "domain.tld", referrer: "https://domain.tld/index.php?module=CoreUpdater&action=oneClickUpdate"
Then the database upgrade screen appear as usual. Process.
All seems to have been well completed so Matomo is fonctional.
So, report it in case I missed something.
Seems like a regression from #13472
Interestingly the same update worked fine for me. (from 3.7.0)
I also experienced this issue a few times, to fix this problem please run the following SQL query:
CREATE TABLE `brute_force_log` ( `id_brute_force_log` bigint(11) NOT NULL, `ip_address` varchar(60) DEFAULT NULL, `attempted_at` datetime DEFAULT NULL ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4; ALTER TABLE `brute_force_log` ADD KEY `ip_address` (`ip_address`);
Note: you may need to replace
I don't think we'll be able to fix it so this manual workaround might be the best option
At now, through upgrade process, thus one error was displayed, I have the table created as this :
CREATE TABLE `piwik_brute_force_log` ( `id_brute_force_log` bigint(11) NOT NULL, `ip_address` varchar(60) DEFAULT NULL, `attempted_at` datetime DEFAULT NULL ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4; ALTER TABLE `piwik_brute_force_log` ADD KEY `ip_address` (`ip_address`);
This table is empty.
If I have understand, as my Matomo database is prefixed with piwik_, I just have to let it as it is ?
@eldk Sounds good. If someone enters an incorrect password it should show up in the table.
@mattab The question is if this is just the normal "update-failed-for-whatever-reason" or if something is special about this update. I was just suspicious because two people reported the same thing, but maybe that was just bad luck.
I think the problem is that we added a couple different updates in beta4, (there was no 3.8.0b3) so if people use Matomo from Git or so, they would have had a partial update for a few days. It should only have happened I think when Matomo used from Git? closing as I don't think it's a bug
For what it's worth, I ran into this when updating from 3.8.0b2 using autoupdate, not Git. Also another more pressing issue with being unable to login, but I think that's separate so I'll file it separately.