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
Add new system check: Check all expected table & columns a plugin expects to exist actually exist #16865
Comments
I don't think that has something to do with the POST request method. Matomo tries to use Maybe try enabling the debugging for tracking by setting
in your config.ini.php After that a tracking request should have debugging details as response. Maybe that helps to identify the problem. |
@narfk you may want to try Meanwhile I have created a PR to automatically disable send beacon when forcing The POST URL by default includes all URL parameters so if there's a redirect then the parameters don't get lost. This is to avoid basically a regression as usually all webservers support POST. By forcing |
I got this error with in Debugmode (_Error query: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'last_idlink_va' in 'field list'). It doesn't matter if this is a GET or POST request
while I was viewing at the code, i found some references in the CustomDimension plugin. In my case this CustomDimenstion table looks like:
In my opinion the update script for 4.0.0 is wrong, not all tables/columns are created |
@narfk Try removing the CustomDimensions plugin from |
@sgiehl This works in my Testenvironment. But There should be a dbUpdate-Script. I have a multiserver environment and this is not how it work. I cannot do this steps on every host. |
Did you have the CustomDimensions plugin installed & activated before you did the update? |
Nope. But i can remember that this plugin cames with the 4.0.0 db update script. |
Ok. That might be the reason. Seems the update might not trigger the plugin install if the plugin was not there before maybe. |
Thanx! |
Just installed a 3.14.1 and did an update to 4.0.3 using the UI updater. Custom Dimensions did not exist before, but was created with the update. The plugin was installed correctly and everything looks fine afterwards. Did you do the update in the UI or using console command? |
I was using the console command. |
Ok. did you replace the files manually? |
i was download the zip file with wget. but i created a new /piwik folder (and moved my configs). |
Ok. Will try to reproduce it that way. |
No, it wasn't installed (in PluginDirectory). |
https://forum.matomo.org/t/error-1054-flooding-php-fpm-logs-after-upgrade-to-4-0-3/39619 seems to be having the same issue. |
@narfk I'm not able to reproduce that behavior. Did a clean install of 3.14. Reused only the config file with a clean extract of 4.0.3 and ran update on console. All columns are created correctly and everything seems to work. @tsteur Do you maybe have an idea? Would it maybe make sense to directly trigger installing the plugin maybe? |
@sgiehl i was checking the config files before 4.0.0. nothing about the custom dimension plugin. maybe something happend during the update. at least the workaround (remove plugin, reactive plugin) seems to work. hopefully this won't happen in the live environment. maybe something for the the system check? |
Thanks for all the troubleshooting work @narfk we'll probably not add something to the system check there for now as we'd need to put some new code into every plugin exposing what columns they expect to exist etc. I'll keep this open though for now as we might do it in the future. |
Hi, same error here from 3.13.x (3.13.3 if I remember correctly) to 4.0.5. First, just after the installation process (from the website, not from the console), I had errors on the dashboard, related to #16868. But after that PHP started to output a large amount of this error:
These errors are gone now by deactivating/reactivating the CustomDimensions plugin, thanks to this issue. After that, the following missing columns were added in
Honestly I could not say if this plugin was activated before. Before reactivation of CustomVariables:
After:
Hope this helps you... |
Thanks for creating the issue. Closing as duplicate of #11540 |
with the default Tracking Code (Backend) i got this error with the new 4.0.0 Version.
In 3.14.1 this works fine.
Header
Status400
Bad Request
VersionHTTP/1.1
Transferred1.13 KB (410 B size)
Referrer Policystrict-origin-when-cross-origin
While is was inspecting matomo.js i found setRequestMethod.
So i tried this.
without any results.
Its still a POST and i got a bad request.
The URL in the networkinspector looks weird for a POST
https://statistics.domain.dd/piwik/matomo.phhp?action_name=title&idsite=2&rec=1&r=944278&h=14&m=29&s=34&url=...
Any advices?
The text was updated successfully, but these errors were encountered: