Closed axiopaladin closed 6 months ago
@axiopaladin
Firstly, a segfault on download is a very odd issue - even on AARCH64 .... no issue like this has ever been reported - even on AARCH64, so this is potentially something unique to how and where the client is trying to write the temporary files when downloading - this is just a theory as your output only shows Segmentation fault
and not any of the other additional output which would be generated.
Secondly - regardless, this issue, if a bug, will not be fixed in v2.4.25 - sorry.
My advice is that you change to start using v2.5.0-rc1 - please read https://github.com/abraunegg/onedrive/discussions/2662 on how to obtain, build and start using. In your instance, post compiling, you will need to run make install
to ensure you install the latest client.
I've compiled onedrive v2.5.0-rc1-12-ga6e2f77
and it runs into the same problem. I tried running it with the -vvv
switch enabled but it doesn't seem to give much more information; here is the last chunk of debug messages before it segfaults on this version:
DEBUG: ------------------------------------------------------------------
DEBUG: Number of JSON items to process is: 447
DEBUG: Number of JSON items processed was: 447
DEBUG: Updating completed deltaLink in DB to: https://graph.microsoft.com/v1.0/drives/[redacted]
DEBUG: Number of items to download from OneDrive: 6
DEBUG: Attempting to calculate local filesystem path for [redacted] and 01Q7ZUJ4TZPPB2GLRSFZDYLQZP7KAPLBUJ
DEBUG: Attempting to calculate local filesystem path for [redacted] and 01Q7ZUJ4TZPPB2GLRSFZDYLQZP7KAPLBUJ
DEBUG: Attempting to calculate local filesystem path for [redacted] and 01Q7ZUJ4SDSWTHRZQMIJCKKCU5D5IIRKYD
DEBUG: Attempting to calculate local filesystem path for [redacted] and 01Q7ZUJ4TZPPB2GLRSFZDYLQZP7KAPLBUJ
DEBUG: Attempting to calculate local filesystem path for [redacted] and 01Q7ZUJ4TZPPB2GLRSFZDYLQZP7KAPLBUJ
DEBUG: Attempting to calculate local filesystem path for [redacted] and 01Q7ZUJ4SDSWTHRZQMIJCKKCU5D5IIRKYD
DEBUG: JSON Item calculated full path for download is: [redacted]/test.txt
Segmentation fault
One odd thing I've noticed is that this v2.5.0-rc1 version seems to convince itself that it has synced successfully, even though it hasn't. (This doesn't happen on v2.4.25.) So after an initial (or --resync
) scan and segfault, invoking v2.5.0-rc1 again will report like this:
@ ./onedrive --sync
Using IPv4 and IPv6 (if configured) for all network operations
Configuring Global Azure AD Endpoints
Fetching items from the OneDrive API for Drive ID: [redacted] ..
No additional changes or items that can be applied were discovered while processing the data received from Microsoft OneDrive
Performing a database consistency and integrity check on locally stored data .
Scanning the local file system '~/OneDrive' for new data to upload .
Performing a last examination of the most recent online data within Microsoft OneDrive to complete the reconciliation process
Fetching items from the OneDrive API for Drive ID: [redacted] .
No additional changes or items that can be applied were discovered while processing the data received from Microsoft OneDrive
Sync with Microsoft OneDrive is complete
...despite the fact that it never downloaded any new files/changes.
I'm not sure what things I could try to interrogate next. Is it a problem with my cloud account? Some configuration problem on my local machine that affected both old and new versions?
@axiopaladin Please can you do the following:
--enable-debug
onedrive --resync --resync-auth --sync --verbose --verbose > debug_output.log 2>&1
If you are concerned about data sensitivity, please read:
Some configuration problem on my local machine that affected both old and new versions?
There is probably something wrong with your actual local system - the debug log with compiler debugging enabled should show what is going on. When was the last time you:
If you could do the above steps to recompile and generated a proper debug log that would be greatly appreciated.
...despite the fact that it never downloaded any new files/changes.
This is because the online 'change' was actually processed already. Microsoft only ever send this change once, and if the file fails to download (error or otherwise) - the only mechanism to get Microsoft to resend the data is to perform a --resync
@axiopaladin Any update or info regarding these 4 questions:
One odd thing I've noticed is that this v2.5.0-rc1 version seems to convince itself that it has synced successfully, even though it hasn't.
@abraunegg This is precisely what issues #2660 and #2637 were about, the behavior simply does not meet users' expectations. Although there exists a solution for this, it only works until a user explicitly identifies the inconsistency. There must be some ways to prevent this. At least I still don't understand why you claim these changes are only sent once as discussed in https://github.com/abraunegg/onedrive/pull/2637#issuecomment-1986568567.
@JC-comp
One odd thing I've noticed is that this v2.5.0-rc1 version seems to convince itself that it has synced successfully, even though it hasn't.
@abraunegg This is precisely what issues #2660 and #2637 were about, the behavior simply does not meet users' expectations. Although there exists a solution for this, it only works until a user explicitly identifies the inconsistency. There must be some ways to prevent this. At least I still don't understand why you claim these changes are only sent once as discussed in #2637 (comment).
And this is why it would be beneficial to you to communicate offline or via MS Teams , so I can show you want I mean by this statement - and how various elements are only ever sent once because of the design of the OneDrive API - however you are reluctant to do this.
Outside of this, I have been working on a proper solution - but not that you would be aware, as you do not wish to communicate offline.
@axiopaladin Please can you respond regarding the questions I have raised.
@axiopaladin Please can you respond regarding the questions I have raised.
@axiopaladin
One odd thing I've noticed is that this v2.5.0-rc1 version seems to convince itself that it has synced successfully, even though it hasn't.
This particular issue has been resolved in https://github.com/abraunegg/onedrive/pull/2661/commits/3d660921dd8273a73ecab687345e178489e053df
@axiopaladin Please can you respond regarding the questions I have raised:
This issue will be closed 5th April if no response is received.
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
When trying to synchronize, the program segfaults upon trying to download any files. Playing with the sync_list to exclude any given file does not prevent this, so it doesn't seem to be linked to any particular file.
Operating System Details
Client Installation Method
From Distribution Package
OneDrive Account Type
Business | Office365
What is your OneDrive Application Version
onedrive v2.4.25
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'
I use it as a cloud backup, synchronized to multiple systems but only one is in active use at a time.
Steps to reproduce the behaviour
I'm not sure exactly what caused it, but now any
onedrive --synchronize
command (unless it is--upload-only
) will segfault like so:Complete Verbose Log Output
Screenshots
No response
Other Log Information or Details
No response
Additional context
This first occurred after receiving
and then performing a
onedrive --synchronize --reauth
to renew the token. I'm not sure if this is related to the issue, or just both problems happened in the same period (the error only appeared when synchronizing for the first time after a fairly long break).