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
S3 as primary storage : empty files are impossible to upload #7585
Comments
cc @icewind1991 |
This is a limitation of amazon and not something we can do much about |
Actually, i'm not using amazon's s3 but radosgw, not sure this makes a difference. But I also showed in the ticket that s3cmd does upload the empty files without any trouble so it doesn't looks the problem is on the storage side but indeed in nextcloud. |
It appears I've ran into the same issue with radosgw. It only happened after upgrading to Nextcloud 12.0.4 |
I have also run into this issue with S3 as my primary storage. Appears to be new since my upgrade to 12.0.4 |
I confirm that we have same issue after upgrade to 12.0.4. We use CEPH as primary S3 storage. |
Hi, |
Please see if #8033 fixes the problem for you |
It does indeed fix the problem! Thanks. Can we expect that commit to be backported into the next 12.0 version? |
Fix should be available in 12.0.6 and 13.0.1 |
Hi, from where I can download these versions? |
They are not released yet. Planned release is mid march. |
Fixed via #8033 (master) and there are also the backport to 12.0.6 and 13.0.1 linked. |
Steps to reproduce
Expected behaviour
the file should be uploaded to the nextcloud instance, on the s3 bucket.
Actual behaviour
in both case (upload from web or using the synchronization client), the upload will fail with the following errors
Adding just one letter in the file fixes the problem.
I first suspected our radosgw cluster, but it doesn't seem to be at fault since uploading the same empty file with s3cmd succeeds:
Server configuration
Operating system: Debian 9.1
Web server: apache 2.4
Database: mariadb 10.1 + galera 3
PHP version: 7.0
Nextcloud version: 12.0.4 and 13beta1
Updated from an older Nextcloud/ownCloud or fresh install: updated from
Where did you install Nextcloud from: nextcloud.com's download servers
Signing status:
Signing status
"No errors have been found."
List of activated apps:
App list
Enabled:
Disabled:
Nextcloud configuration:
Config report
...
"objectstore": {
"class": "OC\Files\ObjectStore\S3",
"arguments": {
"bucket": "cloudprod",
"autocreate": true,
"key": "XXXXXXXXXXXXXXXXXX",
"secret": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX",
"hostname": "cloudrgw.ha.univ-nantes.prive",
"port": 80,
"use_ssl": false,
"region": "optional",
"use_path_style": true
}
},
...
Are you using external storage, if yes which one: S3 as primary storage
Are you using encryption: no
Are you using an external user-backend, if yes which one: LDAP
The text was updated successfully, but these errors were encountered: