Recently, I got this on the customers site, a completely new installation, basically install base 1.9.3.2
here is what i found:
The site uses the composer (of course) to install some basic packages.
One of them:
colinmollenhour/magento-redis-session": "^2.0"
This in turn affects dependencies.
- Installing magento/zendframework1 (1.12.16-patch3) Downloading: 100% Extracting archive REASON: colinmollenhour/php-redis-session-abstract v1.3.1 requires magento/zendframework1 ~1.12.0 -> satisfiable by magento/zendframework1[1.12.0, 1.12.1, 1.12.10, 1.12.13, 1.12.16, 1.12.16-patch1, 1.12.16-patch2, 1.12.16-patch3, 1.12.2, 1.12.3, 1.12.4, 1.12.5, 1.12.6, 1.12.7, 1.12.8, 1.12.9, 1.12.9-patch1]. Thus, the update for magento / zendframework1 is installed in the vendor. At this time, "magento / zendframework1: 1.12.16-patch3" is installed
As soon as I removed the redis-session composition packages that removed the zend update, everything became normal.
Removals: colinmollenhour/magento-redis-session, colinmollenhour/php-redis-session-abstract, magento/zendframework1, colinmollenhour/credis - Removing colinmollenhour/magento-redis-session (2.0.2) - Removing colinmollenhour/php-redis-session-abstract (v1.3.1) - Removing magento/zendframework1 (1.12.16-patch3) - Removing colinmollenhour/credis (1.7)
Version 2.0 was installed in the composer's record for installing the package> Looking at package releases ( https://github.com/colinmollenhour/Cm_RedisSession/releases )
v1.12 has been marked as: The latest version before switching to a Magento-compatible version.
Composer lock for this version: "colinmollenhour/magento-redis-session": "1.12"
solves the problem and saves the redis-session update in the purple codebase.
So basically the problem is that redis-session> 1.12 is not compatible with m1.