-
-
Notifications
You must be signed in to change notification settings - Fork 872
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
JSONValue is not an object - session uploads via HTTP/2 via curl 7.62.0 #224
Comments
@hjrdizwell
Need to understand what is being sent by OneDrive when the failure occurs to determine the cause behind 'JSONValue is not an object' |
Can you also advise what version of curl you are running |
Hello:
[hjr@britten onedrive]$ curl --version
curl 7.62.0 (x86_64-pc-linux-gnu) libcurl/7.62.0 OpenSSL/1.1.1
zlib/1.2.11 libidn2/2.0.5 libpsl/0.20.2 (+libidn2/2.0.4) libssh2/1.8.0
nghttp2/1.34.0
Release-Date: 2018-10-31
Protocols: dict file ftp ftps gopher http https imap imaps pop3 pop3s
rtsp scp sftp smb smbs smtp smtps telnet tftp
Features: AsynchDNS IDN IPv6 Largefile GSS-API Kerberos SPNEGO NTLM
NTLM_WB SSL libz TLS-SRP HTTP2 UnixSockets HTTPS-proxy PSL
Hope that helps... Let me know if I can provide any other information
for you.
Regards & Thanks again,
HJR
…On 10/11/2018 00:56, abraunegg wrote:
Can you also advise what version of curl you are running
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#224 (comment)>,
or mute the thread
</~https://github.com/notifications/unsubscribe-auth/Aq0r6dXy6xWHPdBMUqzN2e6c6VmjNWy4ks5utiQogaJpZM4YW3SJ>.
|
@hjrdizwell |
@hjrdizwell |
I've emailed an update twice now, but it would appear not to be getting through. So I'll type it again here directly. Hello:
As you can see, file uploads are working fine. |
Your version seems off
Would be worth rebuilding again to ensure you get the v2.1.5-* release & version |
OK. Sorry about that. Not sure what happened: possibly didn't delete the original directory created by my initial pull, thus ended up merely re-compiling the patched 2.1.4 version? But in anycase, I should probably not have tried to improve on perfection! See below:
So that's definitely v2.1.5.* ...and we're back to the three-tries-and-a-bomb-out behaviour from before. Sorry if I'm doing it wrong. |
No thats perfect .. Can you now run the exact same command you ran but add '--debug-https' at the end so i can see what is being sent and received by the client as to why it is now failing |
OK. I am now rather confused, because if I issue the command with the --debug-https switch, it does NOT terminate and keeps going fine, apparently managing to upload stuff. If I do it without that switch, it does the three-attempts-and-terminate as you saw above. Since the "With debug" version doesn't terminate, I can't tell what to upload or what's merely repetition. So I attach the first part of the output and hope that contains clues. Please let me know if the attachment is not legible or is missing stuff you need. |
Just by way of follow-up: I terminated the --debug-https version and re-launched the 'ordinary' command:
So, the fact that it is now trying to process BWV177 means the --debug-https switch run did successfully upload some files (because before, we were at BWV 175. So two Bach Canatas got uploaded during the debug run). Hope that's clear. |
OK .. I will have to generate a separate PR for you to test. There is 'zero' reason why, when using |
@hjrdizwell
When executing the application, please can you use the following:
This should generate something like the following:
|
Hello again.
And so on. |
And by way of follow-up, here's the command running without the verbose switch:
...just in case additional switches alters the code-path at all! |
@hjrdizwell |
PR #233 merged |
Sorry to re-open this (and if it's not actually related, I'm happy to open another ticket), but a freshly-installed onedrive is now misbehaving as follows. Versions:
And using the command: onedrive --synchronize --upload-only --verbose I get...
Not sure if it's clear from that, but basically it just kills the connection at the 25% of that file and dumps me back at the command line (without putting in a line break, so the terminal prompt ends up displaying at the end of the broken progress indicator). It 'broke' in exactly the same spot multiple times. So I manually uploaded the Viola Sonata in question, via the OneDrive website in Firefox, and tried again:
This time, it correctly notes that the Viola Sonata No. 1 is now present in the cloud, so updates the local database to reflect that and goes on to process Viola Sonata No. 2. It also correctly creates the directory... but then just stops, dropping me back to the command line. It never actually starts uploading files there. A third attempt:
So now it's doing the 'break at 25%' trick again, on a new file. Rinse and repeat, basically. I therefore did:
...but I'm afraid I can't see anything in that lot which might give me a clue as to what's going wrong, other than it appearing to think connections are dead (the Internet generally is fine here). Any chance of taking a look please? It was working fine before you merged the changes back into the main release :-( Happy to provide further info on request, of course. Regards |
@hjrdizwell |
@hjrdizwell Command 1:
Command 2:
All your other logs above are missing the |
@hjrdizwell |
I'm afraid not. With 900GB of files to upload, I can't afford yet more days of no reliable upload. So I've stopped trying to get my Manjaro desktop to upload and have instead installed the software on my CentOS 7.5 file server, where it is uploading happily (though, curiously, whereas on Manjaro files were being uploaded in alphabetical order, on CentOS, the order of upload is entirely random! Never mind: so long as the files get there eventually, I don't care what order they go in!) Thanks again for all you did to try getting it working on Manjaro, at least. |
@abraunegg I have same error with version v2.2.4-5-g1fa7e5f Here is output:
|
@Zaporozhec7 |
Bug Report Details
Using Manjaro (4.14.79-1-MANJARO #1 SMP PREEMPT Sun Nov 4 16:57:03 UTC 2018 x86_64)
Was uploading ~1TB of files using the manually-issued command:
All had been fine for about a week. I interrupted the upload to apply some O/S updates, rebooted, re-issued the upload command and then got this error:
It would try three times and then produced this output after the third attempt:
I have tried onedrive --resync --verbose, but that hasn't resolved the problem. I am at a loss to know what else to try. Got desperate enough to boot up a Win10 VM and use the native client to finish the upload... which made me sad :-(
Application and Operating System Details:
OS: Linux 4.14.79-1-MANJARO #1 SMP PREEMPT Sun Nov 4 16:57:03 UTC 2018 x86_64 GNU/Linux
dmd --version
orldmd2 --version
To Reproduce
Steps to reproduce the behavior if not causing an application crash:
Using the command
onedrive --synchronize --upload-only
, with the source folder described as follows:The issue happens regardless of what audio file is being uploaded. After the first error, for example, and thinking that maybe it was file-related, I uploaded the file mentioned in the error via the website. A new synchronisation attempt would then try a different file and would produce the same error as the previous one. This would keep happening, no matter how many files I manually uploaded via the website.
Complete Verbose Log Output
There are about 50,000 files to upload in all, so I won't bore you with the entire log! But after a lot of this sort of thing:
...the output eventually changes to:
(As I say, I've checked with mutliple different files having been uploaded by hand, so that the onedrive tool attempts to upload various different files, so it's not the presence of the umlaut in the file name that is the problem -it will happen on perfectly plain-English file names, too).
Application Log Output:
This is from the point where the upload had been working fine, there's an interruption to apply O/S updates, and then I try to resume the upload:
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
If it helps, OneDrive itself is reporting that I have used 339GB of 1TB, so it's not a matter of running out of disk space.
Bug Report Checklist
Appreciate any guidance/help: really value this tool and think it's a splendid thing for Linux folk!
The text was updated successfully, but these errors were encountered: