Magento 2.0.7
@claudiumitreaa thank you for your report.
I was not able to reproduce this issue.
Could you please provide more information?
Hey,thanks for your support!
eav_attribute_group
SET attribute_group_name
= ? WHERE (a
ttribute_group_id
=10) ;@claudiumitreaa, thank you for your report.
We were not able to reproduce this issue by following the steps you provided. If you'd like to update it, please reopen the issue.
We tested the issue on 2.1.9
I am betting this is redis cache. Sometimes you have to clear it manually. I just ran into this and manually clearing redis fixed it.
echo flushall | redis-cli
^ Depends on your redis config of course. That is the command I ran to clear it with redis local on port 6379.
You can clear with plain telnet also:
telnet localhost 6379
flushall
]
quit
I am betting this is redis cache. Sometimes you have to clear it manually. I just ran into this and manually clearing redis fixed it.
echo flushall | redis-cli
^ Depends on your redis config of course. That is the command I ran to clear it with redis local on port 6379.
You can clear with plain telnet also:
telnet localhost 6379 flushall ] quit
redis-cli flushall
worked for me.
I am getting this issue on localhost, no redis is configured. Its simple filesystem caching. Any idea?
Version: 2.3.1
I am also getting this issue while trying to update from 2.2.7 to 2.3.1. Any insight would be much appreciated.
I managed to solve the problem after comparing my root composer.json file to a new Magento 2.3.1 project. I made sure I had the following:
"autoload": {
"psr-4": {
"Magento\\Framework\\": "lib/internal/Magento/Framework/",
"Magento\\Setup\\": "setup/src/Magento/Setup/",
"Magento\\": "app/code/Magento/",
"Zend\\Mvc\\Controller\\": "setup/src/Zend/Mvc/Controller/"
},
...
}
The last item was missing from the project I was updating. After adding it, I was able to run bin/magento again.
I still have the same issue. Fatal error: Uncaught Error: Cannot instantiate interface Magento\Framework\Cache\FrontendInterface in E:\wamp64\www\update\vendor\magento\framework\ObjectManager\Factory\Dynamic\Developer.php:50 Stack trace: #0
Most probably its because of missing classes or changes in the setup/ folder.
Make sure you have "magento-force": "override"
in your composer.json extra section and try:
$ rm -rf setup/
$ rm -rf vendor/magento/magento2-base/
$ composer install
I have got the same error message after updating to 2.3.3.
Tried every solotion but noting solved my problem.
Did someone manage to solve the issue for people without redis?
Try replacing app/etc/di.xml with the default M2.3.3 one.
The following worked for me:
index.php
put this at the start of the file die('maintenance');
to stop requests hitting the box and breaking things. (this can happen even if you are in maintenance mode)app/etc/env.php
make sure:developer
composer.json
extra contains "magento-force": "override"
bash
echo "flushall" | redis-cli \
&& mkdir vendor_backup \
&& mv vendor/magento vendor_backup/ \
&& composer install --no-dev \
&& rm -rf generated/* \
&& php bin/magento setup:upgrade \
&& php bin/magento deploy:mode:set production \
&& php bin/magento cache:enable \
&& php bin/magento cache:flush
site should be alive again
hope this helps someone
Most helpful comment
Try replacing app/etc/di.xml with the default M2.3.3 one.