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

Cache cleanup not running #16397

Closed
jasonbayton opened this issue May 18, 2015 · 2 comments
Closed

Cache cleanup not running #16397

jasonbayton opened this issue May 18, 2015 · 2 comments
Labels

Comments

@jasonbayton
Copy link

Hi,

As I write this I have 1.9TB worth of cache files in the cache folder. These files have been accruing since installation (going back as far as the first few days) but most of the cache has built up in the last week whilst syncing PST/OST files between computers; a task that regularly errors out as they're in use most of the day.

As an aside as I don't know if it's related, I'm seeing many fatal errors

error oc

Version: 8.0.3
Ubuntu 14.04.2
Apache2: 2.4.7
PHP: 5.5.9
MySQL: 5.5.43

The cron settings are on the default AJAX.

It looks like this - #14500 - was created to address something like this, but I'm up to date on ownCloud so if it's supposed to "just work" it doesn't at the moment.

@jasonbayton
Copy link
Author

I've been playing around with the file scan command today after deleting some redundant folders.

This pops up in the terminal:

[Doctrine\DBAL\Exception\DriverException]
An exception occurred while executing 'DELETE FROM oc_filecache WHERE fileid = ?' with params [477345]
:
SQLSTATE[HY000]: General error: 1205 Lock wait timeout exceeded; try restarting transaction

[Doctrine\DBAL\Driver\PDOException]
SQLSTATE[HY000]: General error: 1205 Lock wait timeout exceeded; try restarting transaction

[PDOException]
SQLSTATE[HY000]: General error: 1205 Lock wait timeout exceeded; try restarting transaction

Given the reference to oc_cache I guess it could be related.

@PVince81
Copy link
Contributor

In OC <= 8.0 the cleanup routine runs in the login hook. Which means it happens only when the user logs in. It can be rare when using the "remember me cookie" or using an always running sync client that pings the server often.

In OC >= 8.1 it should happen in cron (still to be confirmed)
Marking as duplicate of #14646

@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.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants