My mac mini which was running mojave until yesterday and stable rclone mount has been upgraded to catalina (same as my work macbook pro) and even using the exact same setup as before and also tested to use the exact same rclone setup as macbook, the mac mini when using the launchd plist keeps retrying to mount the mount(it appears and disappears continuously on the machine). If I run the manual mount command it works fine, so somehow launchctl on this macmini is misbehaving? I have tried a complete fresh install..
Run the command 'rclone version' and share the full output of the command.
rclone v1.58.1
os/version: darwin 10.15.7 (64 bit)
os/kernel: 19.6.0 (x86_64)
os/type: darwin
os/arch: amd64
go/version: go1.17.9
go/linking: dynamic
go/tags: cmount
Which cloud storage system are you using? (eg Google Drive)
google drive
The command you were trying to run (eg rclone copy /tmp remote:tmp)
So, to be clear.
If I run the mount command in a terminal, it works, it mounts the mount fine and it is stable.
But I normally use it in a launchAgent script which is as follow:
when the launchd runs, it will mount and then unmount the folders in rapid succession.. in the rclone.err log it keeps showing the same as above (I modified the mount command to include -vv, only diff from original)
I have tried to use a launchd script that directly uses rclone as below, but it gives the same behaviour
using the same script and launchd on my main macbook pro works perfectly fine.
I don't see anything strange in the mac console either..
any help is very appreciated
I'll give it a try, would be very strange as it worked perfectly fine like this in the past and on my other machine as I mentioned..
hmm,well, yes, it seems to be working without --daemon..
But I'd love to know WHY? and why the exact same thing works on my mbp running same version,same os..
thanks, will monitor this for a while locally but would love if someone could chime in with details.
thansk
I think it probably shouldn't have worked with --daemon at all, as launchd will think the program had died when it demonizes itself and restart it. Maybe it works on one and not the other due to subtle timing differences between exactly how long the daemonized rclone took to start up.