Closed theeggdev closed 1 month ago
@theeggdev Unfortunately where things are at in development of v2.5.x this will not be looked at.
Additionally, Ubuntu 18.x is EOL|EOS - now I know Ubuntu has this LTS program where it will be supported out to 2028, but you should strongly consider upgrading to a newer version of Ubuntu. I do not even test on this platform any more. As far as this client is concerned, Ubuntu 18.x is unsupported.
Additionally when investigating this in the past, 'curl' has been seen to internally flipflop for zero reason for DNS resolution between IPv4 and IPv6 - which heavily contributes to this issue - thus that part is is technically a 'curl' bug. The client, because of it's single threaded use of 'curl' get's hung up on this - thus this is potentially causing your issue.
How 'curl' is used has been totally reworked in v2.5.x and the client has been 100% totally re-written.
Your options to resolve:
ip_protocol_version = "1"
force_http_11 = "true"
Thank you so much @abraunegg for your (as always) impressively prompt reply. We are already looking into upgrading our Ubuntu version. Will also implement your suggestions to have a try. Really appreciate your help! Have a great day :)
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Describe the bug
Operating System Details
Client Installation Method
From Source
OneDrive Account Type
SharePoint
What is your OneDrive Application Version
onedrive v2.4.25-13-g1a88d33
What is your OneDrive Application Configuration
What is your 'curl' version
Where is your 'sync_dir' located
Local
What are all your system 'mount points'
What are all your local file system partition types
How do you use 'onedrive'
We are syncing a SharePoint document library in our linux VM. The SharePoint document library is read and written by ~10 users using Windows OS laptops. Those users sync the SharePoint document library to their laptops using the official MS OneDrive syncing application. Our linux VM also reads and writes to the same SharePoint document library.
Steps to reproduce the behaviour
I understand it might be impossible for you to reproduce the error, so please let me know if there's anything I could provide to you further to assist the investigation.
Complete Verbose Log Output
Screenshots
No response
Other Log Information or Details
No response
Additional context
No response