-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Maintenance:mode changes are not respected #38872
[Bug]: Maintenance:mode changes are not respected #38872
Comments
Check your FPM
That, or restart your PHP FPM as you've discovered. Optimizations have trade-offs. Just have to decide which ones you prefer. :) |
Suspected duplicate of #37557 |
…e and config.php Fixes nextcloud/server#37557 Fixes nextcloud/server#38872 Signed-off-by: Josh Richards <[email protected]>
This comment was marked as resolved.
This comment was marked as resolved.
Is it possible to clear or disable the opcache if the server detects that maintenance mode is active? I am OK restarting php81-fpm to get out of maintenance mode, but going into or being in maintenance mode should be a mandatory condition that is not subject to other configuration settings. |
I'd also be interested in triggering a redis update when the server is in maintenance mode, as I'm using redis for caching and have a similar issue. |
@mjmccarn Not in the way that would be helpful at present unfortunately. Consider that the PHP opcache isn't shared between the CLI and web-app server (mod_php/fpm) processes. So even though we actually do try to invalidate the opcache in our code, it's irrelevant since invalidating the CLI opcache doesn't change anything for the running web app... #37557 (comment) (and elsewhere). P.S. I'm going to close this issue and consolidate further tracking/discussion to: #37557 and #39079 in the interest of not spreading these discussions out everywhere. I encourage you to subscribe to those issues to track progress and anyone else that sees this issue to give those referenced issues a subscribe and/or 👍 if impacted. @jessebot Can you elaborate? The PHP opcache and the data/memcaches (such as Redis) don't have much to do with each other. If you're having a similar issue, it's due to the PHP opcache too (and your installation's PHP opcache settings such as |
Duplicate of #37557 |
Bug description
occ maintenance:mode --on
should force users to see the maintenance mode messageocc maintenance:mode --off
should disable the maintenance mode messageIn each case,
occ status
orgrep maintenance config.php
indicates that the status of the maintenance setting was changed as requested.On my server, I need to execute
systemctl restart php8.1-fpm
before these changes take effect.Steps to reproduce
systemctl restart php8.1-fpm
Expected behavior
Installation method
Community Manual installation with Archive
Nextcloud Server version
27
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.1
Web server
Apache (supported)
Database engine version
PostgreSQL
Is this bug present after an update or on a fresh install?
Upgraded to a MAJOR version (ex. 22 to 23)
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
No response
Additional info
I am seeing the same behavior on two servers.
Both servers use apache2 / PHP 8.1 / redis & postgresql
The text was updated successfully, but these errors were encountered: