# Update to 28.0.5 - memcached error now

**URL:** <https://help.nextcloud.com/t/update-to-28-0-5-memcached-error-now/190125>\
**Category:** ℹ️ Support\
**Tags:** nc28\
**Created:** [May 2, 2024, 1:42am UTC](https://help.nextcloud.com/t/update-to-28-0-5-memcached-error-now/190125 "2024-05-02T01:42:14Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Pedulla](https://help.nextcloud.com/letter_avatar/pedulla/32/6_22734026db12803ebb3e059622ac3534.png) [@Pedulla](https://help.nextcloud.com/u/Pedulla)\
**Post date:** [May 2, 2024, 1:42am UTC](https://help.nextcloud.com/t/update-to-28-0-5-memcached-error-now/190125/1 "2024-05-02T01:42:14Z")

</div>

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 ↗](https://code.google.com/p/memcached/wiki/PHPClientComparison)."

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?

---

<div class="post-metadata">

**Author:** ![Abrikos](https://help.nextcloud.com/user_avatar/help.nextcloud.com/abrikos/32/19379_2.png) [@Abrikos](https://help.nextcloud.com/u/Abrikos)\
**Post date:** [May 2, 2024, 5:40am UTC](https://help.nextcloud.com/t/update-to-28-0-5-memcached-error-now/190125/2 "2024-05-02T05:40:53Z")

</div>

I have the same error after update to 28.0.5

---

<div class="post-metadata">

**Author:** ![m4xmr](https://help.nextcloud.com/user_avatar/help.nextcloud.com/m4xmr/32/61580_2.png) [@m4xmr](https://help.nextcloud.com/u/m4xmr)\
**Post date:** [May 9, 2024, 10:46am UTC](https://help.nextcloud.com/t/update-to-28-0-5-memcached-error-now/190125/3 "2024-05-09T10:46:50Z")

</div>

Same here! after the update to 28.0.5 🫡

---

<div class="post-metadata">

**Author:** ![jtr](https://help.nextcloud.com/letter_avatar/jtr/32/6_22734026db12803ebb3e059622ac3534.png) [@jtr](https://help.nextcloud.com/u/jtr)\
**Post date:** [May 9, 2024, 11:10am UTC](https://help.nextcloud.com/t/update-to-28-0-5-memcached-error-now/190125/4 "2024-05-09T11:10:03Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![jtr](https://help.nextcloud.com/letter_avatar/jtr/32/6_22734026db12803ebb3e059622ac3534.png) [@jtr](https://help.nextcloud.com/u/jtr)\
**Post date:** [May 9, 2024, 3:55pm UTC](https://help.nextcloud.com/t/update-to-28-0-5-memcached-error-now/190125/5 "2024-05-09T15:55:56Z")

</div>

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:

> <https://github.com/nextcloud/server/pull/45242>
>
> \<!--
> - 🚨 SECURITY INFO
> -
> - Before sending a pull request that fixes a s…ecurity issue please report it via our HackerOne page (https://hackerone.com/nextcloud) following our security policy (https://nextcloud.com/security/). This allows us to coordinate the fix and release without potentially exposing all Nextcloud servers and users in the meantime.
> \--\>
> 
> 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)

---

<div class="post-metadata">

**Author:** ![system](https://help.nextcloud.com/user_avatar/help.nextcloud.com/system/32/29333_2.png) [@system](https://help.nextcloud.com/u/system)\
**Post date:** [September 23, 2024, 1:31pm UTC](https://help.nextcloud.com/t/update-to-28-0-5-memcached-error-now/190125/6 "2024-09-23T13:31:49Z")

</div>

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.