Waseh

Community Developer
  • Posts

    203
  • Joined

  • Last visited

  • Days Won

    2

Posts posted by Waseh

  1. 3 hours ago, Spoonsy1480 said:

    Running 2019.10.14 I can not update it says rclone not running. It is running and I can see my files fine.

    just would like to update

    Are you sure it doesn't say "is rclone running?"

  2. 13 hours ago, Waseh said:

    ncw, the maintainer of rclone, has already made a patch that i confirmed fixes the problem.
    Should get released soon.

    @theDrell The fix is now live in the latest beta and might get it's own point release as v1.50.2.
    If the beta fixes your problem please report back in this thread

    • Like 1
    • Thanks 1
  3. 7 hours ago, theDrell said:

    Okay, I downloaded the prebuilt rclone and overwrote the one installed by the plugin, but then had to add 

    
    --config=/boot/config/plugins/rclone/.rclone.conf 

    to my rclone mount command, and my drives are back now until this gets fixed.

    ncw, the maintainer of rclone, has already made a patch that i confirmed fixes the problem.
    Should get released soon.

    • Like 1
  4. On 11/5/2019 at 4:50 AM, theDrell said:

    So I tried reinstalling the plugin.  Nothing.. Even tried reinstalling the regular rclone one, nothing.  Same error  Failed to create file system for "gdrive:": couldn't find root directory ID: googleapi: Error 404: File not found: QWE12345A.....

     

    Tried to refresh the token, didn't work.  I also have a secure one that doesn't work, so neither of them work.  They worked great right after I initially set them up.  

    I downgraded the rclone version on my VPS to 1.49.5 and it's working again.
    I'm going to open a topic on the rclone forum.

  5. 2 hours ago, Kaizac said:

    Woke up this morning to a not functioning server. Running rclone-beta. Suddenly my whole rclone config is erased. So make sure you have your configs backed up.

    Have you looked on your flash drive to see if the config I still there or did you run rclone config to check?

  6. On 11/5/2019 at 4:50 AM, theDrell said:

    So I tried reinstalling the plugin.  Nothing.. Even tried reinstalling the regular rclone one, nothing.  Same error  Failed to create file system for "gdrive:": couldn't find root directory ID: googleapi: Error 404: File not found: QWE12345A.....

     

    Tried to refresh the token, didn't work.  I also have a secure one that doesn't work, so neither of them work.  They worked great right after I initially set them up.  

    Well this is very odd. Im seeing this problem on my VPS which runs straight up Debian but i have no problems on my unraid server.
    The difference is the VPS is connected to my private Google drive and my unraid server i connected to my gsuite account.

    According to my logs the VPS stopped working October 27, which coincides with the release of rclone v1.50.0

  7. 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

  8. 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

    • Like 2
  9. 2 minutes ago, Tortoise Knight said:

    Did you get this figured out? I've got the same error even though rclone isn't running.

    The binary is busy as the copy is failing. So something has the binary locked. 

  10. 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.