[Bug]: Nextcloud update may fail due to php-fpm cache
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
⚠️ This issue respects the following points: ⚠️
- This is a bug, not a question or a configuration/webserver/proxy issue.
- This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
- Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
- I agree to follow Nextcloud's Code of Conduct.
Bug description
see ==> NC Upgrade from version 30.0.11 to "30.0.12.2" failed due to music app
https://github.com/owncloud/music/issues/1231#issuecomment-2977036228
Steps to reproduce
- Trigger NC Upgrade
- From time to tome NC Upgrade will fail (see stack trace) due to an app, which makes troubles
- disable app
- Trigger NC upgrade again
- NC Upgrade will be successful
Expected behavior
Apps should not be able to disturb or lead to fail situation during a Nextcloud Ugrade process
Nextcloud Server version
30
Operating system
RHEL/CentOS
PHP engine version
PHP 8.3
Web server
Apache (supported)
Database engine version
MariaDB
Is this bug present after an update or on a fresh install?
Updated from a MINOR version (ex. 32.0.1 to 32.0.2)
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
What user-backends are you using?
- Default user-backend (database)
- LDAP/ Active Directory
- SSO - SAML
- Other
Configuration report
"system": {
"memcache.distributed": "\OC\Memcache\Redis",
"memcache.locking": "\OC\Memcache\Redis",
"memcache.local": "\OC\Memcache\APCu",
"filelocking.enabled": true,
"redis": {
"host": "REMOVED SENSITIVE VALUE",
"port": "REMOVED SENSITIVE VALUE"
"dbindex": "REMOVED SENSITIVE VALUE",
"timeout": "REMOVED SENSITIVE VALUE",
"password": "REMOVED SENSITIVE VALUE"
},
List of activated Apps
Nextcloud Signing status
no errors
Nextcloud Logs
Additional info
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No repository files, tests, logs, or application list are provided. Start by reviewing the linked ownCloud Music report and reproducing the upgrade from Nextcloud 30.0.11 to 30.0.12.2 with PHP 8.3; done means an enabled app cannot cause the upgrade to fail because of stale PHP-FPM cache state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend, release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 22/100