gcoelho
(Gabriel Coelho)
August 1, 2021, 10:39pm
1
The problem I'm having
I am having a problem mounting google drive with rclone, but the connection to my google drive seems to be working (commands like rclone ls
are working properly).
I have also noticed that the rclone mount --daemon gdrive: ~/gdrive
command is causing the issue visible in the log, but it seems to work fine even after I cntrl-C out of it.
The only problem is the giant error that can be seem in the log and the non-ending mount command.
Rclone version
I am running the latest version.
rclone v1.56.0
- os/version: arch (64 bit)
- os/kernel: 5.13.6-arch1-1 (x86_64)
- os/type: linux
- os/arch: amd64
- go/version: go1.16.6
- go/linking: dynamic
- go/tags: none
The cloud storage system I use
I am using google drive (enterprise).
The command I am trying to run
$ rclone mount --daemon gdrive: ~/gdrive
Rclone config contents with secrets removed
[gdrive]
type = drive
scope = drive
token = {"token_type":"Bearer","expiry":"2021-08-01T16:25:46.489796939-03:00"}
I removed my access and refresh tokens.
Log from the command with the -vv
flag
2021/08/01 15:43:05 DEBUG : rclone: Version "v1.56.0" starting with parameters ["rclone" "-vv" "mount" "--daemon" "gdrive:" "/home/gc/gdrive"]
2021/08/01 15:43:05 DEBUG : Creating backend with remote "gdrive:"
2021/08/01 15:43:05 DEBUG : Using config file from "/home/gc/.config/rclone/rclone.conf"
2021/08/01 15:43:06 DEBUG : Google drive root '': 'root_folder_id = 0ALSXKThPoRBCUk9PVA' - save this in the config to speed up startup
^C2021/08/01 15:46:19 INFO : Signal received: interrupt
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x555ff244a971]
goroutine 67 [running]:
github.com/rclone/rclone/cmd/mountlib.(*MountPoint).Wait.func1.1()
github.com/rclone/rclone/cmd/mountlib/mount.go:256 +0x51
sync.(*Once).doSlow(0xc000d17270, 0xc000074e38)
sync/once.go:68 +0xee
sync.(*Once).Do(...)
sync/once.go:59
github.com/rclone/rclone/cmd/mountlib.(*MountPoint).Wait.func1()
github.com/rclone/rclone/cmd/mountlib/mount.go:254 +0x65
github.com/rclone/rclone/lib/atexit.Run.func1()
github.com/rclone/rclone/lib/atexit/atexit.go:104 +0x7f
sync.(*Once).doSlow(0x555ff3ae8080, 0x555ff2df2718)
sync/once.go:68 +0xee
sync.(*Once).Do(...)
sync/once.go:59
github.com/rclone/rclone/lib/atexit.Run()
github.com/rclone/rclone/lib/atexit/atexit.go:102 +0xb8
github.com/rclone/rclone/lib/atexit.Register.func1.1()
github.com/rclone/rclone/lib/atexit/atexit.go:52 +0xea
created by github.com/rclone/rclone/lib/atexit.Register.func1
github.com/rclone/rclone/lib/atexit/atexit.go:44 +0x96
________________________________________________________
Executed in 193.93 secs fish external
usr time 194.80 millis 5.74 millis 189.06 millis
sys time 57.87 millis 3.45 millis 54.42 millis
There is a bug with daemon and 1.56. You can upgrade to the beta or wait for the point release.
opened 09:57PM - 21 Jul 21 UTC
closed 10:35AM - 29 Jul 21 UTC
Point Release Candidate
VFS / mount
bug
<!--
We understand you are having a problem with rclone; we want to help you … with that!
**STOP and READ**
**YOUR POST WILL BE REMOVED IF IT IS LOW QUALITY**:
Please show the effort you've put in to solving the problem and please be specific.
People are volunteering their time to help! Low effort posts are not likely to get good answers!
If you think you might have found a bug, try to replicate it with the latest beta (or stable).
The update instructions are available at https://rclone.org/commands/rclone_selfupdate/
If you can still replicate it or just got a question then please use the rclone forum:
https://forum.rclone.org/
for a quick response instead of filing an issue on this repo.
If nothing else helps, then please fill in the info below which helps us help you.
**DO NOT REDACT** any information except passwords/keys/personal info.
You should use 3 backticks to begin and end your paste to make it readable.
Make sure to include a log obtained with '-vv'.
You can also use '-vv --log-file bug.log' and a service such as https://pastebin.com or https://gist.github.com/
Thank you
The Rclone Developers
-->
#### The associated forum post URL from `https://forum.rclone.org`
#### What is the problem you are having with rclone?
```
rclone mount --daemon -vvv b2crypt: b2crypt
2021/07/21 21:53:18 DEBUG : rclone: Version "v1.56.0" starting with parameters ["rclone" "mount" "--daemon" "-vvv" "b2crypt:" "b2crypt"]
2021/07/21 21:53:18 DEBUG : Creating backend with remote "b2crypt:"
2021/07/21 21:53:18 DEBUG : Using config file from "/home/pi/.config/rclone/rclone.conf"
2021/07/21 21:53:18 DEBUG : Creating backend with remote "b2:sedlund-rcrypt"
```
**DOES NOT FORK**
v1.55.1
```
rclone mount --daemon -vvv b2crypt: b2crypt
2021/07/21 21:58:16 DEBUG : Using config file from "/home/pi/.config/rclone/rclone.conf"
2021/07/21 21:58:16 DEBUG : rclone: Version "v1.55.1" starting with parameters ["rclone" "mount" "--daemon" "-vvv" "b2crypt:" "b2crypt"]
2021/07/21 21:58:16 DEBUG : Creating backend with remote "b2crypt:"
2021/07/21 21:58:16 DEBUG : Creating backend with remote "b2:sedlund-rcrypt"
2021/07/21 21:58:17 DEBUG : rclone: Version "v1.55.1" finishing with parameters ["rclone" "mount" "--daemon" "-vvv" "b2crypt:" "b2crypt"]
$
```
Forks and I get my prompt back.
#### What is your rclone version (output from `rclone version`)
v1.56
#### Which OS you are using and how many bits (e.g. Windows 7, 64 bit)
32bit Raspberry Pi OS Buster
#### Which cloud storage system are you using? (e.g. Google Drive)
Backblaze B2
#### The command you were trying to run (e.g. `rclone copy /tmp remote:tmp`)
see log above
#### A log from the command with the `-vv` flag (e.g. output from `rclone -vv copy /tmp remote:tmp`)
See Abve
#### How to use GitHub
* Please use the 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to show that you are affected by the same issue.
* Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
* Subscribe to receive notifications on status change and new comments.
gcoelho
(Gabriel Coelho)
August 2, 2021, 2:50pm
3
I'm sorry, I had not seen that!
Thanks for the fast response, I think I'll wait for the point release.
system
(system)
Closed
October 2, 2021, 10:51am
4
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.