Closed robertschulze closed 3 months ago
@robertschulze
Your RC2 version is onedrive v2.5.0-rc2-25-g71bce90
The latest correct RC2 version is onedrive v2.5.0-rc2-24-gfb77411
.. which branch are you actually running?
The correct branch has this commit: https://github.com/abraunegg/onedrive/pull/2709/commits/ac334e8860aefc0a424d596e2a684f81efe5ffe3 which changes the Curl handling for signalling which can be the cause of this.
As you are using RC2, I would also suggest you test PR #2728 - it has a significant amount of fixes in in and will probably become the base for RC3 (which then I will look at your other issue). When using #2728 your version will be onedrive v2.5.0-rc2-37-g3f7fb5a
at the moment.
The last thing here is memory on the system .. check that the application is not being killed by an OOM process.
I am constantly testing all of these versions with 125K files online. What I have also found is that memory usage, when using Ubuntu versions & the Ubuntu 'ldc' provided version, it is way higher than using the 'dmd' or 'ldc' package install using the install script - so something else to think about.
Actions for you:
@abraunegg
I used PR #2728 (onedrive v2.5.0-rc2-37-g3f7fb5a
) but unfortunately the problem still persists. I will send four log files from four subsequent runs that just stop at entirely different steps. For the last two it is after the processing of the last JSON item of the last JSON Item Batch.
The thing is that there is no error message or anything, they just stop. Is there anything I can do to better investigate it?
Memory appears to be no issue, usage according to top
is 0.3% during the whole time.
@robertschulze
The thing is that there is no error message or anything, they just stop. Is there anything I can do to better investigate it?
Do not use Ubuntu? Is that an option?
A couple of things for you to test:
ip_protocol_version = "1"
force_http_11 = "true"
curl 7.81.0
--verbose --verbose --debug-https
to whatever command is executing.Something upstream is potentially doing something ... but I am not ruling out some of the other Curl changes at this stage - but the HTTPS Debug Logs will show this. Please read: https://github.com/abraunegg/onedrive/wiki/Generate-https-debug-log-for-support
No other log other than the HTTPS Debug Log is going to assist here.
I have been doing >72Hr long runs with earlier code from #2728 on the following platforms using the default configuration:
Everything is rock solid .. nothing like this is being seen. So right now I have to point the finger at your environment / network path between you and Microsoft OneDrive. The HTTPS Debug Log will give more clues.
@robertschulze Any update here ?
@abraunegg Yes, I tested the ideas:
Release-Date: 2024-05-22
Protocols: dict file ftp ftps gopher gophers http https imap imaps ipfs ipns ldap ldaps mqtt pop3 pop3s rtsp smb smbs smtp smtps telnet tftp
Features: alt-svc AsynchDNS HSTS HTTP2 HTTPS-proxy IDN IPv6 Largefile libz NTLM SSL threadsafe TLS-SRP UnixSockets
the code continues past the old breaking point:
i.e. the line DEBUG: Number of JSON items processed was: 2759
appears. So the breaking point must have been between the two log entries:
DEBUG: Number of JSON items to process is: 2759
DEBUG: Number of JSON items processed was: 2759
@robertschulze
Force to IPv4 and HTTP/1.1: same result, the only thing that changed was that the log file stops one (simple separator) line before the last iteration
That is an odd one as this has nothing to do with that option being set. It could be console logging output just missing it due to volume of logging done .. as any separation line is a standard line output .. thats just an odd one an I am scratching my head on that.
With HTTP Debug Output Logging the separator line is back, and some additional lines
OK .. so the reason the Curl engine was stopping is that something upstream from you closed the active connection. That is the detail needed when using --debug-https
that helps understand why something is being killed.
As you are on Ubuntu the finger pointing starts at Ubuntu and its horrid ufw
and its settings there. From there you need to look at your router and how you connect to the Internet in general, then speak to your ISP as to what is closing connections. I would be starting with ufw
and get rid of that awful inclusion - or at least configure it so that it is not killing connections.
With curl having been upgraded to
What Curl version did you upgrade to ? By the date, it looks like you may be using 8.8.0 - this is a good thing, so at least all known issues post curl 7.81.0
will have been resolved
Post upgrading Curl - are things working or not working for you now - this is unclear from what you have posted
Older Curl versions might still be using internal code that does not adhere correctly to CURLOPT_NOSIGNAL - hopefully all Curl libraries and tools were correctly updated on your system when you did the upgrade.
Unfortunately, I cannot (yet) upgrade to Ubuntu 24 because I am on the LTS branch which I would greatly prefer to remain on.
Ubuntu 24.x is also an LTS Branch , but if you were going to rebuild - I would suggest in order:
@abraunegg I ran a few more tests and with the updated curl (8.8.0 indeed) it appears to work reliably now, no more sudden code stops. Thanks!
@abraunegg I ran a few more tests and with the updated curl (8.8.0 indeed) it appears to work reliably now, no more sudden code stops. Thanks!
Great .. so yet another Ubuntu special ... keeping users on old versions in the guise of stability actually causing stability issues .. who would have thought that ......
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
I use onedrive v2.5.0-rc2-25-g71bce90 and observe frequent crashes without any error message. The processing just stops, doesn't matter whether syncing or resyncing. Sometimes - without changing anything - it suddenly works.
Operating System Details
Client Installation Method
From Source
OneDrive Account Type
Personal
What is your OneDrive Application Version
onedrive v2.5.0-rc2-25-g71bce90
What is your OneDrive Application Configuration
What is your 'curl' version
Where is your 'sync_dir' located
Network
What are all your system 'mount points'
What are all your local file system partition types
How do you use 'onedrive'
./onedrive --confdir='/home/robert/.config/onedrive/accounts/robert@guitaronline.de' --sync --verbose --verbose --resync --resync-auth > debug_output.log 2>&1
or./onedrive --confdir='/home/robert/.config/onedrive/accounts/robert@guitaronline.de' --sync --verbose --verbose > debug_output.log 2>&1
Steps to reproduce the behaviour
run as above
Complete Verbose Log Output
Screenshots
No response
Other Log Information or Details
Additional context
No response