Skip to content
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

Jump to bottom

Upgrade from 3.7.0 to 3.8.0 broke all sorts of things #13990

Closed
ghost opened this issue Jan 22, 2019 · 3 comments
Closed

Upgrade from 3.7.0 to 3.8.0 broke all sorts of things #13990

ghost opened this issue Jan 22, 2019 · 3 comments
Labels
duplicate For issues that already existed in our issue tracker and were reported previously.

Comments

@ghost
Copy link

ghost commented Jan 22, 2019

Wow, somebody really messed it up this time. The upgrade from 3.7.0 to 3.8.0 came up with the following problems:

  1. The upgrade procedure produced this error:
SQLSTATE[42S02]: Base table or view not found: 1146 Table 'dbuser.matomo_brute_force_log' doesn't exist
  1. The upgrade procedure caused the following PHP error
Error in Matomo (tracker): Error query: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'dbuser.matomo_tracking_failure' doesn't exist In query: SELECT idsite FROM matomo_tracking_failure WHERE idsite = ? and idfailure = ? Parameters: array (   0 => 1,   1 => 2, )
  1. The integrity check now reports these two files need to be deleted:
File to delete: misc/internal-docs/content-tracking.md
File to delete: .lfsconfig
  1. Many Settings pages (like the new change admin password) generate this error:
Error in Matomo: Could not verify the security token on this form.
@pattyland pattyland mentioned this issue Jan 22, 2019
Closed
@caplod
Copy link

caplod commented Jan 22, 2019

I had the same errors.
Managed to get things working again with

  • delete the files mentioned in 3.
  • finish the database migrations with php /path/to/matomo/console core:update

@dev-101 dev-101 mentioned this issue Jan 22, 2019
Closed
@rudyzeinoun
Copy link

By running ./console core:update, I noticed that the database queries counted as 5 in total, but they are in fact 7, so I saw the queries running beyond 5/5 to 6/5 then 7/5. Maybe this is related, as the database upgrade was the failing step when updating from web.

@mattab
Copy link
Member

mattab commented Jan 22, 2019

thanks for the report. duplicates #13836

@mattab mattab closed this as completed Jan 22, 2019
@mattab mattab added the duplicate For issues that already existed in our issue tracker and were reported previously. label Jan 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
duplicate For issues that already existed in our issue tracker and were reported previously.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@rudyzeinoun @caplod @mattab