grive2
grive2 copied to clipboard
Constant HTTP 500 uploading modified file that was updated remotely by Backup And Sync program
trying to sync a file that has been updated locally and remotely gives the following error:
$ grive -s dir -d
...
sync "./dir/config.ini" changed in local. uploading
HTTP PUT "https://www.googleapis.com/upload/drive/v2/files/1Gjht3ee1-BABFMS81_bSy-cZxLOoAP66?uploadType=multipart&newRevision=false"
HTTP response 500
request failed due to temporary error: 500 (body: {
"error": {
"errors": [
{
"domain": "global",
"reason": "internalError",
"message": "Internal Error"
}
],
"code": 500,
"message": "Internal Error"
}
}
). retrying in 5 seconds
HTTP PUT "https://www.googleapis.com/upload/drive/v2/files/1Gjht3ee1-BABFMS81_bSy-cZxLOoAP66?uploadType=multipart&newRevision=false"
HTTP response 500
request failed due to temporary error: 500 (body: {
"error": {
"errors": [
{
"domain": "global",
"reason": "internalError",
"message": "Internal Error"
}
],
"code": 500,
"message": "Internal Error"
}
}
). retrying in 5 seconds
HTTP PUT "https://www.googleapis.com/upload/drive/v2/files/1Gjht3ee1-BABFMS81_bSy-cZxLOoAP66?uploadType=multipart&newRevision=false"
HTTP response 500
request failed due to temporary error: 500 (body: {
"error": {
"errors": [
{
"domain": "global",
"reason": "internalError",
"message": "Internal Error"
}
],
"code": 500,
"message": "Internal Error"
}
}
). retrying in 5 seconds
this happens for the same file after a day. The same error occurs if I edit the same file on a different system then grive sync there as well. The local copy of the file on my two systems are both different, but both fail constantly with HTTP 500.
If I edit a different file locally and sync, the newly edited file uploads correctly, but the original file still fails to sync.
If I move the failing file to a new name, it uploads the new name successfully, but then fails on another file.
I noticed that the group of files that all fail were all updated remotely using Google drive's Windows' "Backup and Sync" program. Has this possible changed some metadata about the files that stops grive from updating them?
I can confirm this issue on Ubuntu 18.04.2 LTS
Confirmed on Arch.