Skip to content

Unable to set native session handler that is different from the one define in php.ini after update to Magento 2.3 #24717

Closed
@mlindholm

Description

@mlindholm

Preconditions (*)

2.4-develop

Steps to reproduce (*)

  1. Configure env.php to use memcached as save_handler as instructed in the documentation.

Expected result (*)

  1. SessionManager should be setting memcached as used save handler in initOptions function.

Actual result (*)

  1. SessionManager is not setting the memcached as save_handler, but is instead using the files session_handler. The save_path is set though, which result error message below:

main.CRITICAL: Warning: SessionHandler::read(): open(127.0.0.1:11211/sess_0imeeaqmnvemdg4e3h57tat0ik, 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_0imeeaqmnvemdg4e3h57tat0ik, 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)"} []

Own foundings

New changes made in 2.3 for SessionManager are preventing the save_handler to be set as anything else than the one configured to php.ini for Native session handler.

Metadata

Metadata

Assignees

Labels

CDIssue recommended for the contribution dayComponent: CacheIssue: Clear DescriptionGate 2 Passed. Manual verification of the issue description passedIssue: ConfirmedGate 3 Passed. Manual verification of the issue completed. Issue is confirmedIssue: Format is validGate 1 Passed. Automatic verification of issue format passedIssue: Ready for WorkGate 4. Acknowledged. Issue is added to backlog and ready for developmentPriority: P1Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing.Progress: doneReproduced on 2.3.xThe issue has been reproduced on latest 2.3 releaseReproduced on 2.4.xThe issue has been reproduced on latest 2.4-develop branchSeverity: S1Affects critical data or functionality and forces users to employ a workaround.Triage: Dev.ExperienceIssue related to Developer Experience and needs help with Triage to Confirm or Reject it

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions