Closed efirlus closed 2 months ago
@efirlus This issue relates to the single threading of v2.4.x and will not be fixed.
Please manually compile v2.5.0 RC3 and test that application version regarding your scenario.
There is a 'short' window here that if this is still an issue in v2.5.0 RC3 this can be fixed before it is released on 16th September.
Please URGENTLY test v2.5.0 RC3 in your environment.
@efirlus
I'll have to work on a way to automatically stop the service just before 4:05am.
Use 'crontab' .. a cron job to restart the service after your router reboot .. say 4.10am
@efirlus FYI I have tested v2.5.0 RC3 against this scenario:
- leave the computer with ubuntu server installed simply turned on.
- leave onedrive running in monitor mode.
- reboot the router.
- watch the errors spew out.
No such error occurs post rebooting the router.
Please can you test v2.5.0 RC3 in your environment URGENTLY as if there is an issue, I would rather have this fixed before next Monday.
@efirlus Please can you respond
@abraunegg
@efirlus Please can you respond
I apologize for taking so long to respond.
I've spent the last 3 days researching how to erase the existing packages and install 2.5.0 RC3, but I've been unable to figure it out at all. I'm unfortunately not a professional ubuntu user, just a guy who uses commands on the fly as gpt tells me to... Sorry.
Without thinking, I deleted the current onedrive and unpredictibly the contents of /home/user/OneDrive/*
were deleted, but it wasn't worth it since I didn't have anything important in there.
Next, I tried to install RC, but it wasn't as easy as just typing in a few opensuse package keywords.
Building via dmd, or ldc, is something I've never done before, so I was pretty intimidated, but I went ahead and pasted in the curl - fsS blah blah bash -s dmd
from the guide anyway, and got an error
I can't scrape the logs at the time because I'd already turned the SSH window off and on a few times, but it was basically saying that the OneDrive version was crashing.
After typing in a few keywords from GPT's advice that I couldn't understand, the crash went away, but the next thing I knew it was talking about permissions.
Well, I let go after that....
Luckily, crontabs are something I've always used, so it was relatively easy to adapt. Making systemctl
passwordless was a bit of a challenge, but I eventually succeeded in restricting it to onedrive@user
.
Unfortunately, this wasn't a very good approach, because when I first reported the bug and forced the router to shut down, it was obviously just a matter of stopping it, turning it off, turning it back on, and then starting the service.
But then I woke up last night and realized that the same problem was still happening. Crontab timer was set to stop at 4 o'clock and start at 5 o'clock, and timer was working, but onedrive was giving me same errors from 5 o'clock.
So I came back to read this thread and saw that you had already written the RC story and the crontab story, and I tried to implement them, and it's been this long... Sorry again.
@efirlus Sorry that you could not work out how to uninstall your package and install RC3.
No matter, I have tested this scenario, evidence below:
Based on all of this evidence I am closing this issue.
@abraunegg
I don't know if you're being called out for tagging an ID in a closed thread, but I'm curious if I understand it correctly, that's why I comment here.
In short, if v2.5 comes out (or if I succeed in installing RC3), the problem will be solved?
Of course, I haven't solved the installation issue yet.... I'm looking forward to it being released as a package, even if it's not a homebrew or something more convenient.
@efirlus
In short, if v2.5 comes out (or if I succeed in installing RC3), the problem will be solved?
It should be ... but .. only doing some testing in your environment will validate. I am fairly confident that it should be fixed.
Of course, I haven't solved the installation issue yet....
Backtrack / back out everything you have done.
Given you are using Ubuntu, follow these instructions: https://github.com/abraunegg/onedrive/blob/onedrive-v2.5.0-release-candidate-3/docs/ubuntu-package-install.md
Once you do that, you will get the current client version installed.
When the release is done on Monday, and the packages are updated, you should be able to update your Ubuntu package without an issue.
@abraunegg
Hi! I'm here to tell you that I'm over the hump thanks to v2.5.
And I would definitely recommend adding one thing to the usage. Add a warning that the 1-thread issue is only fixed by creating a new systemservice or running daemon-reload.
If you just sudo apt update && upgrade and leave the v2.4-service alone, you still have the problem the next morning lol.
This morning I saw a bunch of timeout errors again, so I tried to error report again, and in the process gpt told me to try reload-daemon.
So I did it, and the onedrive connection was fine, even though I turned it off and on several times. I may come back in a few days, but thanks for making v2.5 so awesome. Being able to use the --verbose option even in monitor mode has allowed gpt to be more proactive in helping me.
@efirlus Thanks for the feedback that v2.5.0 is working without issue in your scenario
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
Literally, I have my connected router set to reboot at 4:05am, and from that time until I reboot my PC, no matter what I do, onedrive will not connect and will repeat the error below ad infinitum.
Operating System Details
Client Installation Method
From 3rd Party Source (PPA, OpenSuSE Build Service etc)
OneDrive Account Type
Business | Office365
What is your OneDrive Application Version
onedrive v2.4.25-1+np3+5.1
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'
For Windows 11
For Android Devices
For Ubuntu Server
Steps to reproduce the behaviour
Complete Verbose Log Output
Screenshots
No response
Other Log Information or Details
No response
Additional context
Well, it occurred to me while taking logs that if you stop the service, rebooting the router doesn't seem to matter. I'll have to work on a way to automatically stop the service just before 4:05am.