- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
memcached related error after upgrade to 2.3 from 2.2.6
i had memcached session handling enabled on 2.2.6 after upgrade I ran into problem
[2018-11-30 01:07:57] main.CRITICAL: Warning: SessionHandler::read(): open(127.0.0.1:11211/sess_f56733b831d6321752b41db7382b9d08, O_RDWR) failed: No such file or directory (2) in../vendor/magento/framework/Session/SaveHandler/Native.php on line 22 {"exception":"[object] (Exception(code: 0): Warning: SessionHandler::read(): open(127.0.0.1:11211/sess_f56733b831d6321752b41db7382b9d08, O_RDWR) failed: No such file or directory (2) in ../vendor/magento/framework/Session/SaveHandler/Native.php on line 22 at ../vendor/magento/framework/App/ErrorHandler.php:61)"} []
disabling session by memcached resolved
how to enable it again?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: memcached related error after upgrade to 2.3 from 2.2.6
Hi @alexrus76g
You can enable memcache again by following the below steps :
- Using your preferred text editor, navigate to the directory where you installed Magento, and then open the app/etc/env.php file.
- Locate the following section in the env.php file:
'session' => [ 'save' => 'files' ],
- Modify this section as follows:
'session' => [ 'save' => 'memcached', 'save_path' => '127.0.0.1:11211' // your ip and port number of memcached installed ],
- Save your changes to the env.php file. Memcached is now enabled.
For more details refer this link - https://www.a2hosting.in/kb/installable-applications/optimization-and-configuration/magento1/configu...
Hope it helps !
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: memcached related error after upgrade to 2.3 from 2.2.6
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: memcached related error after upgrade to 2.3 from 2.2.6
Hi @alexrus76g
For this issue , i would suggest you to look into this link - https://devdocs.magento.com/guides/v2.2/install-gde/trouble/php/tshoot_session.html
Explained well to work around on the same issue !
Hope it helps !
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: memcached related error after upgrade to 2.3 from 2.2.6
workaround, rather this is reverting to default magento behavour. What im
trying to get soution for is how to start using memcached again
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: memcached related error after upgrade to 2.3 from 2.2.6
I'm also experiencing the same problem. Does anyone have a solution?
I can confirm the site is working when switched back to saving sessions via files.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: memcached related error after upgrade to 2.3 from 2.2.6
I tested and memcached is working (with a standalone php script.)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: memcached related error after upgrade to 2.3 from 2.2.6
Hi, the support for memcache was dropped in magento 2.3.0.
I have created plugin which allows use of memcache for session.
Documentation is available here: https://connect20.aveo-trade.cz/docs/user-guide-memcached-2.3.0.pdf
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: memcached related error after upgrade to 2.3 from 2.2.6
Consider switching to the Magento recommended session storage Redis ->
https://devdocs.magento.com/guides/v2.3/config-guide/redis/redis-session.html
Very simple to setup and works just as good if not better than Memcache.
Problem solved? Click Accept as Solution!
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: memcached related error after upgrade to 2.3 from 2.2.6
Confirm. I have same error in 2.3.1