Closed xtremevision closed 8 months ago
Hi @xtremevision. Thank you for your report. To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:
@magento give me 2.4-develop instance
- upcoming 2.4.x release@magento I am working on this
Join Magento Community Engineering Slack and ask your questions in #github channel. :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting. :clock10: You can find the schedule on the Magento Community Calendar page. :telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.
Hi @engcom-Bravo. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:
Area: XXXXX
label to the ticket, indicating the functional areas it may be related to.2.4-develop
branch@magento give me 2.4-develop instance
to deploy test instance on Magento infrastructure. 2.4-develop
branch, please, add the label Reproduced on 2.4.x
.Issue: Confirmed
once verification is complete. @magento give me 2.4-develop instance
Hi @TheRealHunzik. Thank you for your request. I'm working on Magento instance for you.
Hi @TheRealHunzik, here is your Magento Instance: https://13419714cb153513679fd5669e6724c3.instances-prod.magento-community.engineering Admin access: https://13419714cb153513679fd5669e6724c3.instances-prod.magento-community.engineering/admin_4de8 Login: 1559d545 Password: cdd1a062be42
Hi @xtremevision,
Thank you for reporting and collaboration.
Verified the issue on Magento 2.4-develop instance and the issue is not reproducible.Kindly refer the screenshots.
Steps to reproduce
We are able to see the shipping methods and able to place the order.
Kindly recheck the issue in Magento 2.4-develop instance and check if any third party modules causing the issue.
Thanks.
Ok, I will test with Luma theme instead of the 3rd party theme, as well as by switching off custom modules / 3rd party modules.
Hi i Have Same issue when i open multi products in one time Exception #0 (Exception): Warning: Undefined array key 0 in /vendor/colinmollenhour/php-redis-session-abstract/src/Cm/RedisSession/Handler.php on line 515
Good evening, I see this issue also on Magento 2.4.6-p3, redis_version:7.2.4
[2024-02-01T19:10:19.046017+00:00] main.ERROR: Warning: Undefined array key 0 in /home/amadeco/public_html/vendor/colinmollenhour/php-redis-session-abstract/src/Cm/RedisSession/Handler.php on line 515 [] [] [2024-02-01T19:10:19.046802+00:00] main.CRITICAL: Warning: Undefined array key 0 in /home/amadeco/public_html/vendor/colinmollenhour/php-redis-session-abstract/src/Cm/RedisSession/Handler.php on line 515 [] []
I noticed these messages today in var/log/system.log:
[2024-02-02T19:35:17.139662+00:00] main.WARNING: localhost|2475: Did not write session for ID b3f7mpdhrg0dmgkg8tlnb2uq8r: another process took the lock. /themelayoutpro/ajax/cmsblock/?blockidentifier=unlimited-furniture-newsletter-popup [] [] [2024-02-02T19:35:18.689020+00:00] main.WARNING: localhost|2478: Did not write session for ID b3f7mpdhrg0dmgkg8tlnb2uq8r: another process took the lock. /customer/section/load/?sections=&=1706902508672 [] []
Found this article: https://magento.stackexchange.com/questions/296730/redis-session-error-successfully-broke-lock-for-id-sess-ebfc12b22fa8c8e1fb81dca
I updated the values as per the accepted answer, but to be 100% safe I also created a dedicated redis instance for this site on port 6378.
So far, the checkout error has gone away, and the write session messages as well.
Could it be that I have too many sites accessing the same redis instance, albeit with different redis databases? Could it be another site is accessing the same database as this one effectively corrupting data?
Hi @xtremevision
The bug should only trigger when the setting max_concurrency
gets exceeded if I understand it correctly.
According to the comments on https://github.com/colinmollenhour/php-redis-session-abstract/commit/47a1df331c16b8ed3387102933eaeac2fd52f0e8, this seems to be a bug that existed in versions 1.5.3 and 1.5.4 of the colinmollenhour/php-redis-session-abstract
package.
It should be fixed in version 1.5.5, could you try to update this package to the latest version and see if that solves it for you?
@hostep Thanks for your contribution and collaboration here.
Hi @xtremevision,
Thanks for your update.
Kindly refer this comment https://github.com/magento/magento2/issues/38399#issuecomment-1925339677 and please let us know if you are still facing any issue.
Thanks.
I updated colinmollenhour/php-redis-session-abstract to 1.5.5 and it seems to have fixed the issue, but I'll do a bit more testing to make sure. Thanks.
Hi @xtremevision,
Thanks for your update.
As per this comment https://github.com/magento/magento2/issues/38399#issuecomment-1932107224 We are Closing this issue Please feel free to reopen the issue if you are still facing any issue.
Thanks.
Preconditions and environment
PHP 8.1.27 (cli) (built: Dec 19 2023 20:35:55) (NTS gcc x86_64) Copyright (c) The PHP Group Zend Engine v4.1.27, Copyright (c) Zend Technologies with Zend OPcache v8.1.27, Copyright (c), by Zend Technologies with Xdebug v3.3.1, Copyright (c) 2002-2023, by Derick Rethans
Steps to reproduce
Expected result
No error message
Actual result
1 exception(s): Exception #0 (Exception): Warning: Undefined array key 0 in /home/michael/www/xxxxxxxxxx/xxxxxxxxxx/vendor/colinmollenhour/php-redis-session-abstract/src/Cm/RedisSession/Handler.php on line 515
Exception #0 (Exception): Warning: Undefined array key 0 in /home/michael/www/xxxxxxxxx/xxxxxxxxx/vendor/colinmollenhour/php-redis-session-abstract/src/Cm/RedisSession/Handler.php on line 515
Additional information
No response
Release note
No response
Triage and priority