Been seeing this in my log a lot lately (log is generated from my rclone mount system service.
2019/11/27 19:45:06 DEBUG : /: Lookup: name="container"
2019/11/27 19:45:06 DEBUG : /: >Lookup: node=<nil>, err=no such file or directory
What is this? It's making my log enormous.
It's when you do a dir or ls container and it doesn't exist. Something is doing that and creating the error.
any way to track it down? It happens every few seconds.
Hmm, maybe a file watch? Not sure as it literally could be anything. What OS again?
I'm running debian 9
Let me dig around.
I think you can use fswatch.
You might want to turn off the debug logs, so just use -v rather than -vv - the debug logs are quite extensive in rclone mount!
I'd guess you are running dockers or something along those lines that is perhaps hitting it.
fswatch only shows if a file was hit but not was process was doing it.
Since the file doesn't exist and doesn't ever stay open, you can't really catch it up with 'lsof' either.
I'd probably just turn off things and turn them back on until I found it.
The logs are benign messages though as it's just checking for a file that doesn't exist and doesn't really do much.
I don't normally run with debug mode unless I'm trouble shooting something.
I use rclone rc commands to toggle it on to debug (8) and back to info (6) by doing this:
rclone rc options/set --json '{"main": {"LogLevel": 6}}'
rclone rc options/set --json '{"main": {"LogLevel": 8}}'
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.