Fatal error: Uncaught Error: Call to a member function getLogger() on null in /customers/f/1/0/DOMAIN/httpd.www/cloud/cron.php:165
thrown in /customers/f/1/0/DOMAIN/httpd.www/cloud/cron.php on line 165
Cron issue was resolved - missing php module on the shared hosting.
And after spending (way to much) time on Github reading thru the different reports on S3 it honestly scares me - It seems to me that we have some rather big bugs.
Uploads can fail and leave alot of dead files on the S3… eg. on my test, my users have 11gb data… but it takes 19gb on the S3… logically i could go thru the DB manually and compare files - but i shouldent have to.
If you delete a user WITHOUT deleting the users data - the users data will just hang there… without no way of cleaning it.
occ commands does not help clean the S3 storage.
I think it would be wise to create some kind of script that looks in the db and compare it to the s3 storage to clean up the storage… and offcourse fix above bugs.
There is one catch though. File names etcetera only exist in the database when using S3. I have opted here and there, that it would be a good idea to use the file/folder capability of S3 for redundancy, but that has not happened.
Therefor, it is a good idea to have a mysql master/slave structure set up, for creating a live backup of your sql data… (betrter safe then sorry )
I’m using S3 for over a year now, and it is running smoothly.
Do keep in mind there are quite a few “extra files” out there, preview files and such. If all goes well, it should mean about the same amount (and size) of files should be in S3 as there would be on local storage.
That said, I must say I have very little uploading trouble. I have read that extremely large files have trouble uploading… and I do remember having done some tweaks there (sorry, but I don’t remember which ones). Is the S3 hoster you chose a bit slow? Have you tested an other?
I have tested this (inadvertantly). And the files did get removed (version 25). Some caching files weren’t removed though (do read on… )
@tarek asked me about the tool “local → S3”… and I decided to share the tool I built to perform a good migration with a bunch of checks. One of these checks that were needed to perform a “multi step migration” was to check for files on S3 that weren’t in the database (and vice versa)
So the “bonus” of my migration script is that it can be used to check for inconsistencies!
So in essence this script is that “occ files:cleanup” that does work on local, but not with S3 (at Nextcloud team: hint, hint )
When I deleted a user I saw the deletion of some cache files. When I have the time I’ll check for this
I have only recently published it on GitHub and no one else but me has used it (to my knowledge) so please read the readme.md !