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
(core dumped) when upgrade to 4.3.0 #17613
Comments
Hi @lds-lds, that's strange that it would say it's already up to date since updating the internal version is only done after the update process is complete. If you'd like to re-run the updates, you can run the following SQL: |
hello @diosmosis when I execute your order I get Rows matched: 1 Changed: 1 Warnings: 0 Does that mean that the 151 operations of the maj were correctly executed?
|
@lds-lds Apologies, I should have mentioned, that SQL just makes matomo think its at an older version. So when you load Matomo or run the core:update command, it will run the updates from 4.2.1. You still need to load Matomo and go through the upgrade or run core:update. |
ok I understood that in the meantime I upgraded the version of php to 7.4 and the version of mariadb to 10.4 the problem remains the same |
@lds-lds we'll have to try and find out where the segfault is happening. Can you check the following for me?
And just to be clear, you are upgrading from Matomo 4.2, correct? |
@diosmosis Here is mariadb describe command for piwik_brute_force_log and piwik_segment for matomo 4.2
|
And after upgrade from 4.2.1 to 4.3.1
|
it's very strange if I |
@lds-lds That's odd... it looks like the updates were successfully run, and the failure occurs sometime afterwards. Perhaps the output is buffered and does not have a chance to be printed out. I'm not sure where the issue could be. Can you check if there are any plugins that are now deactivated after the update? And would you be able to set |
@diosmosis 1: with core: updatethere is a coredump on 183 Query SHOW COLUMNS FROM piwik_log_visit 2: only via webinstallerno errors all is good
210531 11:28:23 186 Query SHOW COLUMNS FROM piwik_log_visit
|
@lds-lds thanks for the extra information! My guess is the CLI php is either a different version than the web PHP version or they are configured differently. Perhaps the CLI php version is not allowed as much memory? Can you check the |
hello @diosmosis |
here is the diff diff /etc/php/7.2/apache2/php.ini /etc/php/7.2/cli/php.ini
|
strange if i run it twice in a row the update works O-o I will launch the update from the browser, since this way I have no problems |
Hi @lds-lds, ok good to know you have a workaround! I'll close this ticket for now, but if you notice any other cli commands segfaulting feel free to open this ticket again. If you want to try and figure out exactly what's causing the problem, we can, but it will take a while to isolate the cause.
Note: this makes sense if it's running the updates successfully and then erroring later. The version is updated in the database, so the next time you run it, it won't try to run any updates, since the database is already up-to-date. |
hello
i got this error when i updated matomo to version 4.3.0 by running php /home/matomo/www/matomo/console core:update
only one treatment appears on the 151 ...
I launched the command again and got this result:
Everything is already up to date.
did I corrupt my database ?
Your Environment
The text was updated successfully, but these errors were encountered: