-
Notifications
You must be signed in to change notification settings - Fork 2.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
cron.php must not run in maintenance mode is enabled #14843
Comments
I also noticed that CLI tools like "./occ files:scan --all" work in maintenance mode, but that should be fine since an admin might want to manually rescan in maintenance mode. However some admins might have setup their own cron jobs to rerun the scanner as a workaround for FS issues (ex: external storage update detection). |
wow,. This can be very bad. |
I'll take care of that ... |
cron shall not operate in case we are in maintenance mode - fixes #14843
cron shall not operate in case we are in maintenance mode - fixes #14843
It did very bad :( |
Is this file also used for the webcron? Otherwise we need to check for other possible places that could trigger this |
Checked for stable7 👍 |
Steps
update oc_jobs set last_run=0
php cron.php
orcurl http://userid:password/owncloud/cron.php
Expected result
Cron does NOT run, timestamps left as is
Actual result
Cron runs through the background jobs and updates the "last_run" field.
This can have nasty consequences especially when doing manual database repairs, there is a risk that the background file watcher kicks in and does some scanning.
Versions
Observed in OC 6.0.5, likely to exist in OC 7 and OC 8 too
@DeepDiver1975 @karlitschek @MorrisJobke @icewind1991
The text was updated successfully, but these errors were encountered: