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

Installation broken with "Uncaught exception: Call to undefined method DI\ContainerBuilder::setDefinitionCache()" after update to 4.0.4 #16907

Closed
tuxmaster5000 opened this issue Dec 8, 2020 · 9 comments
Closed

Installation broken with "Uncaught exception: Call to undefined method DI\ContainerBuilder::setDefinitionCache()" after update to 4.0.4 #16907

tuxmaster5000 opened this issue Dec 8, 2020 · 9 comments
Labels
Can't reproduce (yet) For issues that are reported by several people, but can't be reproduced reliably and need more data wontfix If you can reproduce this issue, please reopen the issue or create a new one describing it.

Comments

@tuxmaster5000
Copy link

After update to 4.0.4 from 3.14.1

On the console only this will logged:

Uncaught exception: Call to undefined method DI\ContainerBuilder::setDefinitionCache()
in /var/www/matomo/core/Container/ContainerFactory.php line 69
#0 /var/www/matomo/core/Application/Environment.php(141): Piwik\Container\ContainerFactory->create()
#1 /var/www/matomo/core/Application/Environment.php(95): Piwik\Application\Environment->createContainer()
#2 /var/www/matomo/core/Console.php(250): Piwik\Application\Environment->init()
#3 /var/www/matomo/core/Console.php(112): Piwik\Console->initEnvironment(Object(Symfony\Component\Console\Output\ConsoleOutput))
#4 /var/www/matomo/core/Console.php(93): Piwik\Console->doRunImpl(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#5 /var/www/matomo/vendor/symfony/console/Symfony/Component/Console/Application.php(126): Piwik\Console->doRun(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#6 /var/www/matomo/console(32): Symfony\Component\Console\Application->run()
#7 {main}

The only solution was an rollback to 3.14.1
@sgiehl
Copy link
Member

sgiehl commented Dec 8, 2020

Maybe not all files were updated correctly. That method should actually not be called any longer.
How did you perform the update?

@tuxmaster5000
Copy link
Author

I simple click on the update button of the ui. After some time the message will shown in the browser.

@tsteur
Copy link
Member

tsteur commented Dec 9, 2020

Hi @tuxmaster5000 unfortunately, it looks like during the update one file was not correctly updated. Maybe the filesystem had some glitch. Any chance you could try the manual 3 step update see https://matomo.org/docs/update/#the-manual-three-step-update ?

It be important to backup the file config/config.ini.php. Sorry about that I know it's a pain and takes extra time.

@tsteur tsteur added Can't reproduce (yet) For issues that are reported by several people, but can't be reproduced reliably and need more data wontfix If you can reproduce this issue, please reopen the issue or create a new one describing it. labels Dec 9, 2020
@tuxmaster5000
Copy link
Author

It will fails also, but with another error.
After overwriting the files, matomo don't start anymore.
Screenshot_2020-12-09 Matomo › Error

@tuxmaster5000
Copy link
Author

We use the ldap plugin.

@sgiehl
Copy link
Member

sgiehl commented Dec 9, 2020

Did you replace the ldap plugin with the new version as well?

@tuxmaster5000
Copy link
Author

No, must I do this manual?

@tuxmaster5000
Copy link
Author

So after update it by using the zip file for the matomo itself and for the ldap plug, the updater starts.
But than I ran into an sql problem:

[X] Critical Error during the update process:

* /var/www/matomo/core/Updates/4.0.0-b1.php:
Error trying to execute the migration 'ALTER TABLE `piwik_log_visit` ADD COLUMN `visitor_seconds_since_first` INT(11) UNSIGNED NULL, ADD COLUMN `visitor_seconds_since_order` INT(11) UNSIGNED NULL, ADD COLUMN `visitor_seconds_since_last` INT(11) UNSIGNED NULL, ADD COLUMN `profilable` TINYINT(1) NULL;'.
The error was: SQLSTATE[42000]: Syntax error or access violation: 1118 Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs

But this have I fixed with:
https://mariadb.com/kb/en/troubleshooting-row-size-too-large-errors-with-innodb/

After that I can login again and update rest if the plug ins.
But I have never seen this problem before on any of my matomo installations.

@tsteur
Copy link
Member

tsteur commented Dec 11, 2020

Great, glad this works now @tuxmaster5000

Maybe there was some glitch in the filesystem during the update. We do try to update the files multiple times if needed but somehow it still didn't update this file correctly. Sorry about that. I'm glad you otherwise got things sorted now. I'll close this issue for now but feel free to comment in there's still something left to look at. Thanks for this.

@tsteur tsteur closed this as completed Dec 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Can't reproduce (yet) For issues that are reported by several people, but can't be reproduced reliably and need more data wontfix If you can reproduce this issue, please reopen the issue or create a new one describing it.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@tsteur @tuxmaster5000 @sgiehl