Update to 28.0.5 - memcached error now

Pedulla · May 2, 2024, 1:42am

Installed on Ubuntu 22.04.4LTS - LEMP stack
Working 28.04 install updated to 28.05
Now the Admin Overview reports:
" * Memcached is configured as distributed cache, but the wrong PHP module “memcache” is installed. \OC\Memcache\Memcached only supports “memcached” and not “memcache”. For more details see the documentation ."

The documentation link errors out.

memcached is already the newest version (1.6.14-1ubuntu0.1).
php-memcached is already the newest version (3.1.5+2.2.0-14.1).

Is this a false flag or did something change between 28.04 & 5?

Abrikos · May 2, 2024, 5:40am

I have the same error after update to 28.0.5

m4xmr · May 9, 2024, 10:46am

Same here! after the update to 28.0.5

jtr · May 9, 2024, 11:10am

Remove the PHP memcache module. Keep the PHP memcacheD module.

Is this a false flag or did something change between 28.04 & 5?

The setup checks are constantly evolving.

jtr · May 9, 2024, 3:55pm

Technically the check logic changed a little and may trigger in environments where memcache (the wrong PHP module) is present even if the other (correct) module (memcacheD) is also present.

Fix pending:

github.com/nextcloud/server

fix(setupCheck): Only warn when memcache present w/o memcached

nextcloud:master ← nextcloud:check-memcache-memcached

opened 03:54PM - 09 May 24 UTC

joshtrichards

+5 -4

Fixes: https://help.nextcloud.com/t/update-to-28-0-5-memcached-error-now/190125 ## Summary Prior to #42812 the check for the common mistake of installing PHP modules `memcache` rather than `memcached` only warned if `memcached` was missing while `memcache` was installed. When the setup checks were moved to the new API, the logic was changed (probably accidentally) so that it warned *anytime* `memcache` was present. This means existing environments started getting a warning about a problem that really isn't a problem. Restores the old logic. Also removes the old ancient third-party doc link that isn't relevant and only creates confusion. Also tries to make the next step *super* obvious when this warning is triggered legitimately. ## TODO - [x] Trigger backport to v29 & v28 ## Checklist - Code is [properly formatted](https://docs.nextcloud.com/server/latest/developer_manual/digging_deeper/continuous_integration.html#linting) - [Sign-off message](https://github.com/src-d/guide/blob/master/developer-community/fix-DCO.md) is added to all commits - [x] Tests ([unit](https://docs.nextcloud.com/server/latest/developer_manual/app_development/tutorial.html#unit-tests), [integration](https://docs.nextcloud.com/server/latest/developer_manual/app_development/tutorial.html#integration-tests), api and/or acceptance) are included - [x] Screenshots before/after for front-end changes - [x] Documentation ([manuals](https://github.com/nextcloud/documentation/) or wiki) has been updated or is not required - [x] [Backports requested](https://github.com/nextcloud/backportbot/#usage) where applicable (ex: critical bugfixes)