New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Auto-archiving of reports broken since Matomo 3.12.0 #15123
Comments
Resolved by setting |
@khromov just to understand things better: any particular reason you were using @mattab wonder if we should recommend row (in case we haven't done this yet on an FAQ). In general: Matomo should already catch the error and workaround this for |
I think we got the problem, because our Matomo is connected to a MariaDB Galera Cluster and the binlog_format is ROW and we can't change: |
|
@manusfreedom MySQL server has gone away seems like a different issue? https://matomo.org/faq/troubleshooting/faq_183/ |
@tsteur The problem comes with 3.12.0 update and nothing has change on our infrastructure and all https://matomo.org/faq/troubleshooting/faq_183/ is already respected. |
Same issue here with Galera, 3.13 do not work 3.11 is ok. |
Can you please create a new issue with the full error message you're getting? There are a few different error messages in this issue already (which seem not related to Matomo?) so will be better to tackle them separately. Thanks! |
Seems to be some issue with MySQL:
The error is:
Full error:
The text was updated successfully, but these errors were encountered: