-
-
Notifications
You must be signed in to change notification settings - Fork 850
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
The parent item is not in the local database #121
Comments
You need to uninstall any prior 'onedrive' version which is the skilion codebase & reinstall using my branch. You also need to ensure you remove any The above message is totally indicative of the prior skilion compiled application being installed on your system and is being found through the default path. Refer to #98 for any additional help |
Updated the FAQ (https://github.com/abraunegg/onedrive/wiki/Frequently-Asked-Questions) with details on this error |
Hi, actually, there was no previous skilion installation since this onedrive was deployed on a brand new Leap 42.3... What is the purpose of the 2 service files (onedrive.service and ondrive@.service)? One is not sufficient ? In any case, you have to change the URL in your service files which is incorrect (still pointing to skilion) :
Thanks. |
OK .. thats a worry - everything should be added to the database correctly ..... this will need investigating
The best reference for this is skilion/onedrive#314 - have a look at the comments from @sbocquet ~ late March / April 2018.
Yes it does - thanks for pointing this out. |
Is there any reason why your specifying With this error:
Do you still get the error when you run this command line:
If you do - can you post the entire full debug log please |
Hi, I have deleted all the local db files, all the files in my onedrive storage and it seems to work fine now with the following service file :
Note: I have also deleted the onedrive@.service file which is not used in my case. Keep you posted if the issue occurs again. Thanks. |
OK .. it's weird then that it didn't work but now it is ... |
Sorry, but the error occurred again... With onedrive v2.1.1-3-gb98c938 onedrive --synchronize --upload-only --local-first --verbose (and same error with --resync)
|
Can you post the full log rather than just the last extract like you have? The full log shows me what the client was doing before the error occured |
Can you please rebuild and use this specific version of the client to collect diagnostic details on your issue:
When posting the log, I need the entire log from start to finish, not just the crash please. |
Hi, for onedrive v2.1.1-3-gb98c938, with which I have the initial error "The parent item is not in the local database", you can check the log fgauvrit.onedrive.log.old. for onedrive v2.1.1-4-ge215c1b, check the log fgauvrit.onedrive.log. I have added my config file, service file and db just in case. Thanks in advance for your help. |
Thanks the for log files. I have made added further logging into the PR. Please can you reclone the PR and retest:
However, when running this version please run via a separate terminal / SSH session, do NOT use monitor mode:
When the error occurs again, send me the entire 'console' output including the crash, not just the log file as the crash does not get written to the log file. |
Hi, onedrive v2.1.1-5-g6946808 I used onedrive --synchronize --upload-only --local-first --verbose > console_output.log 2>&1 and here are the 2 resulting files : The error occurs after 21 Gb of upload. Thanks. |
Same test on another computer with a crash after 45 Gb of upload. Not sure it is the same error but it crashes all the time just like the previous computer. Thanks. |
Thanks .. will have to also diagnose this locally using a OpenSuSE Leap 42.3 system to rule out any local environmental issue. |
So looking at the latest logs this is where the client appears to be breaking:
This narrows things down as to where to start looking for the problem |
From 'onedrive_2.zip' you have a bad file name with a weird white space character - this is why that crash occurred. Please can you archive and email "309 GLA-60809-51� lounge sofa.xls" without changing it's name or anything & email that to support@mynas.com.au |
Hi, I found the reason of the first crash : That stupid Microsoft onedrive can't make difference between "Photos" and "photos", so it makes the client crash. I renamed the directory and it seems to work fine now... Keep you posted if I see something weird like that. For the second crash, I can't send you the file since it is confidential data. I fixed the name and it is syncing fine now. Thanks. |
If you still have the file before you renamed it - please can you send it but delete all the data inside of it - that I don't need - just the file name.
I don't think this is the case, as using your logs to replicate your directory tree, I am able to create the entire path without issue - no error at all. |
Hi. Sorry, I didn't kept the strange file. I confirm that the fact to rename "photo" to "photo2" fixed the problem. Thanks. |
Can you email to support@mynas.com.au a full directory listing / path output so I can try and replicate somehow? Ive tried replicating but to no avail as yet |
For info, I was able to extract the commit version with the following command : |
The impacted tree was /home/data/Medias/Photos/A traiter/Photos and .../photos. The fact to rename "photos" to "photos2" fixed the problem. |
Is there any chance for you to test the following PR:
What it should do is clearly articulate that there is a similar named directory in the same folder path, thus skip syncing of the files with a warning message. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Bug Report Details
The parent item is not in the local database
Application and Operating System Details:
To Reproduce
onedrive --upload-only --synchronize --resync
Complete Verbose Log Output
The text was updated successfully, but these errors were encountered: