Mounting a remote with the "--daemon" flag will fail, but it will look like it mounted successfully unless you use the -vv flag which shows you that the mount terminated instantly. This happens on all my remotes, including regular and crypt remotes.
Using the "--daemon" flag, if the mount is successful you end up back at the bash prompt with no error message. When I use the command below, this is result I get, except that the remote isn't actually being mounted. Checking the command with the -vv flag, it appears the mount ends instantly in a way that is being interpreted as a "clean" exit, but it never mounted in the first place.
The exact same command with the "--daemon" flag removed will mount the remote correctly.
What is your rclone version (output from rclone version)
1.55
Which OS you are using and how many bits (eg Windows 7, 64 bit)
Ubuntu 20.04.2 LTS 64-bit
Which cloud storage system are you using? (eg Google Drive)
Google Drive, Dropbox, and crypt
The command you were trying to run (eg rclone copy /tmp remote:tmp)
rclone mount remote: /path/to/mount --allow-non-empty --cache-db-purge --allow-other --vfs-cache-mode full --vfs-cache-max-age 5m --cache-dir /path/to/.cache/rclone --daemon
A log from the command with the -vv flag
2021/04/11 20:08:10 DEBUG : Using config file from "/home/user/.config/rclone/rclone.conf"
I just tried it with --log-file, which does give a bit more info - my rclone.conf file is encrypted, and trying to mount with --daemon gives the error "Couldn't decrypt configuration, most likely wrong password.", even though the password I'm providing is correct. That error only shows up in the log file, it doesn't appear when using the -vv flag.
So to summarise:
Mounting with --daemon fails
The reason it fails is "Couldn't decrypt configuration, most likely wrong password.", even when the correct password is used. This only becomes apparent when using the --log-file flag, otherwise it looks exactly like the mount was actually successful because rclone just spits you back out at the bash prompt the same way it does if the mount is successful
Mounting without --daemon works without any issues
Removing the "--allow-non-empty" flag has no effect either
The full output of the logfile is below - you can see it instantly fails and says the config password is incorrect, even though it is actually correct. If I try the same command with the "--daemon" flag removed, it mounts correctly.
2021/04/12 14:58:32 DEBUG : Using config file from "/home/username/.config/rclone/rclone.conf"
2021/04/12 14:58:32 DEBUG : rclone: Version "v1.55.0" starting with parameters ["rclone" "mount" "remote:" "/path/to/mount" "-vv" "--allow-non-empty" "--cache-db-purge" "--allow-other" "--vfs-cache-mode" "full" "--vfs-cache-max-age" "5m" "--cache-dir" "/path/to/.cache/rclone" "--daemon" "--log-file" "/path/to/rclonelog.txt"]
2021/04/12 14:58:32 DEBUG : Creating backend with remote "remote:"
2021/04/12 14:58:32 DEBUG : rclone: Version "v1.55.0" finishing with parameters ["rclone" "mount" "remote:" "/path/to/mount" "-vv" "--allow-non-empty" "--cache-db-purge" "--allow-other" "--vfs-cache-mode" "full" "--vfs-cache-max-age" "5m" "--cache-dir" "/path/to/.cache/rclone" "--daemon" "--log-file" "/path/to/rclonelog.txt"]
2021/04/12 14:58:32 ERROR : Couldn't decrypt configuration, most likely wrong password.
2021/04/12 14:58:32 Failed to read line: EOF
With the --daemon flag included, rclone prompts for your config password (as expected). You type it in and it spits you out at the bash prompt, as if it had worked, when it fact it failed.
From the log file you can see it fails instantly, and gives the "Couldn't decrypt configuration, most likely wrong password." error even though the supplied password was correct.
Using the same command but removing the --daemon flag, it all works as expected - rclone prompts you for the password as expected, you type it in and then everything is mounted as expected.