Everything posted by Waseh
-
[Plugin] rclone
It doesn't. Your problem will only be solved if rclone gets patched by the maintainer or if you start mounting to an empty folder
-
[Plugin] rclone
@testdasi You are completely right. Pushed an update with a fix. I didn't even notice that i had hard coded paths for each branch in the rclone wrapper since the very first version 😅
-
[Plugin] rclone
I must admit that I don't use the mount feature anymore but a quick search results in the following TLDR: You can just remove the nonempty mount option, it is the default behaviour now. So this seems to be a problem with the way rclone handles non empty folders when combined with fusermount3 Here is the relevant issue on GitHub For more information check the changelog for libfuse specifically the entry regarding libfuse 3.0.0
-
[Plugin] rclone
Well i wish i saw your edit before getting to the above conclusion myself. Atleast we came to the same result Thanks
-
[Plugin] rclone
Considering how early that happens it seems to be something with the check for fusermount. What happens if you run fusermount -V ?
-
[Plugin] rclone
@Squid Now it does 😅 2019.10.13b Fusermount compatibility fix for future unRaid versions
-
[Plugin] rclone
Someone beat me to it. And probably explained it in a nicer way than i would have Reinstalling the plugin will also result in the newest version being pulled Take a look at the change log 2017.09.23 Always pull newest version on install I do concede that this could be stated somewhere more noticeable
-
[Plugin] rclone
You should install it through the community applications plugin. Also thanks for pointing out the link in the first post is outdated - I'll get that sorted
-
[Plugin] rclone
Is your plugin up to date? It seems to be trying to pull a pretty old version of rclone.
-
[Plugin] rclone
The binary is busy as the copy is failing. So something has the binary locked.
-
[Plugin] rclone
So was rclone running? I mean the error is pretty self explanatory.
-
[Plugin] rclone
Yea i'm still going with your pihole blocking the rclone download. For the record i also use a pihole instance as my local dns resolver which works without any problems. Reviewing the code that's pretty much the only way to get that exact error without any other errors.
-
[Plugin] rclone
Yea but reaching 8.8.8.8 is fine. The plugin checks 8.8.8.8 first and only tries 1.1.1.1 if 8.8.8.8 fails.
-
[Plugin] rclone
That doesn't really make sense though since that should result in the "No internet - Skipping download and using existing archives" error. Are you sure you can reach the rclone webpage?
-
[Plugin] rclone
If the curl command doesnt solve it then the fix probably won't work either though since that's the fix im doing 😅 I just updated the plugin with a longer timeout.
-
[Plugin] rclone
Yea i haven't had time to push the fix (simple as it is). I'll see if I can get it done tonight.
-
[Plugin] rclone
Humor me a bit and try running it again with 5. If that still gives you an error I'll update the plugin with a more lax timeout
-
[Plugin] rclone
Well the plugin is doing exactly what it's supposed to. For some reason you can't connect to the rclone website to download the zip. Seems that you can't resolve the domain. Perhaps try increasing the timeout value and try the command again.
-
[Plugin] rclone
@Heciruam What happens if you run: curl --connect-timeout 5 --retry 3 --retry-delay 2 --retry-max-time 30 -o /boot/config/plugins/rclone/install/rclone-current.zip https://downloads.rclone.org/rclone-current-linux-amd64.zip
-
[Plugin] rclone
The plugin installs the newest version on install so just remove the plugin and install it again.
-
[Plugin] rclone
Having your plugins update automatically won't do much good if rclone is running when the update is triggered. The install didn't succeed. Try rebooting again if you cannot reinstall and/or you don't get any errors when you install
-
[Plugin] rclone
Sounds like you didn't have the new version installed. Are you getting any errors when you reinstall?
-
[Plugin] rclone
You could use the build in way to encrypt the config file but that just means that you have to either enter the password every time you run a command or include the password in the command kinda defeating the purpose. If you want to do it just run rclone config and follow the instructions for password protecting the config.
-
[Plugin] rclone
This seems to be the case for atleast some of you guys. Do you get any errors during the update?
-
[Plugin] rclone
Nope working fine here