-
-
Notifications
You must be signed in to change notification settings - Fork 4.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
Upload to external swift storage fails #13448
Comments
GitMate.io thinks possibly related issues are nextcloud/android#2199 (Visualise external storages), nextcloud/android#537 (Cannot change storage path from default to external.), nextcloud/android#2198 (Duplicated images on external storage), nextcloud/android#2232 (External Storage Folder not Visible), and nextcloud/android#2840 (Upload fails with SSL error). |
@nextcloud/server-triage is this something for the server repo? |
cc @icewind1991 |
cc @rullzer |
Thank you for transferring the topic to the right place. If you need any additional information or log data - just let me know! Thank you! |
Hello, My logs are:
I can provide more data, simply let me know! :) |
Hi, are there any news concerning this topic? The problem still exists and the external storage is not useable. |
I notice this same issue using 15.0.4, using Swift as external volume. "The key provided "" has the wrong value type. You provided 1550707987 (integer) but was expecting string" This doesn't happen when using Swift as principal storage. When using principal storage another issue happens, but it is fixed by #14424 . This issue and #14424 seems to be related though, as the issue mentioned here only happens with files bigger than 10MB. Bigger files are uploaded but not completely, it corrupts the file. |
I was able to fix this issue modifying the file: /var/www/apps/files_external/lib/Lib/Storage/Swift.php line 454
To
|
Hi,
Actual behaviour
Uploading a file using the desktop client for Mac OSX (Version 2.5.1final (build 20181204)) fails with the following message:
The key provided "" has the wrong value type. You provided 1543265922 (integer) but was expecting string
After a while, the client retries the upload and succeeds. The file is then also visible at the Nextcloud web Application.
A similar behaviour occurs while uploading a file with the Android App (Version 3.4.1). The upload fails with the message Server not found. But looking at the web application shows the file correctly uploaded to the external swift storage.
Uploading to the main (internal) storage, which is just a folder in the webserver does work in both cases without any errors.
Android version: 8.0
Device model: Galaxy S7
Stock or customized system: Stock
Nextcloud app version: 3.4.1
Nextcloud server version: 15.0.0
Php version: 7.0.30-0+deb9u1
External Storage: OpenStack Swift hosted at OVH.net
Logs
[webdav] Fatal: Exception: The key provided "" has the wrong value type. You provided 1543265922 (integer) but was expecting string at <>
validateType(1543265922)
validate(1543265922)
validateObject({timestamp: 1543265922})
validate({timestamp: 1543265922})
validate({containerName: ... }})
sendRequest(OpenStack\Common\Api\Operation {}, {containerName: ... }})
execute({method: "POST", ... }}, {containerName: ... }})
mergeMetadata({timestamp: 1543265922})
touch("Upload/pdf.pdf", 1543265922)
touch("Upload/pdf.pdf", 1543265922)
touch("Upload/pdf.pdf", 1543265922)
touch("Upload/pdf.pdf", 1543265922)
basicOperation("touch", "/cloud_storage/Upload/pdf.pdf", ["touch"], 1543265922)
touch("/cloud_storage/Upload/pdf.pdf", 1543265922)
put(null)
createFile("pdf.pdf", null)
createFile("files/jos/cloud_storage/Upload/pdf.pdf", null, null)
httpPut(Sabre\HTTP\Reque ... "}, Sabre\HTTP\Response {})
call_user_func_array([Sabre\DAV\CorePlugin {},"httpPut"], [Sabre\HTTP\Requ ... }])
emit("method:PUT", [Sabre\HTTP\Requ ... }])
invokeMethod(Sabre\HTTP\Reque ... "}, Sabre\HTTP\Response {})
exec()
exec()
require_once("/var/www/html/c ... p")
PUT /remote.php/dav/files/x/cloud_storage/Upload/pdf.pdf
from x.x.x.x by x at 2018-12-28T21:42:57+00:00
The text was updated successfully, but these errors were encountered: