Skip to content
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

Closed
PVince81 opened this issue Mar 12, 2015 · 6 comments · Fixed by #14844
Closed

cron.php must not run in maintenance mode is enabled #14843

PVince81 opened this issue Mar 12, 2015 · 6 comments · Fixed by #14844
Assignees
Milestone

Comments

@PVince81
Copy link
Contributor

Steps

  1. Setup OC with either ajax cron or CLI cron
  2. Switch on maintenance mode
  3. update oc_jobs set last_run=0
  4. Run php cron.php or curl http://userid:password/owncloud/cron.php
  5. Check "oc_jobs" table

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

@PVince81 PVince81 added this to the 8.1-current milestone Mar 12, 2015
@PVince81
Copy link
Contributor Author

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).

@karlitschek
Copy link
Contributor

wow,. This can be very bad.

@DeepDiver1975 DeepDiver1975 self-assigned this Mar 12, 2015
@DeepDiver1975
Copy link
Member

I'll take care of that ...

@MorrisJobke
Copy link
Contributor

wow,. This can be very bad.

It did very bad :(

@MorrisJobke
Copy link
Contributor

Is this file also used for the webcron? Otherwise we need to check for other possible places that could trigger this

@jvillafanez
Copy link
Member

Checked for stable7 👍

@lock lock bot locked as resolved and limited conversation to collaborators Aug 11, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants