New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mutagen constantly resyncing, despite no actual file changes - how do I debug/troubleshoot this? #258
Comments
Update: I destroyed my entire Docker machine, changed my Dockerfile around to make it rebuild everything, and brought everything back up... and it's magically fixed. Really, really wish I could find a way to get Mutagen to show us what it was doing more / push out some debug info. |
The problem is either still here or there's another issue with mutagen causing it to randomly start burning through the CPU, causing entire MacBook to get hot. It's becoming a showstopper for me since it drains my battery and burns my lap on a regular basis. Is there any way we can help debugging this issue? |
To be honest, there's not really a trivial way to debug this at the moment, because Mutagen doesn't have debugging/tracing messages in all the places that it would need to in order to debug the issue. It does have the logging infrastructure to acquire and store that information, even from remote endpoints, but I just haven't managed to get logging statements in everywhere I'd like. If you want to do a custom build of Mutagen (which is actually fairly easy), you could use the existing logging infrastructure to print more granular information to the daemon log about what's triggering synchronization and what's being synchronized. This might end up being necessary anyway since it'll be hard to guess exactly what needs to be traced/logged. At the moment I'm focused on getting v0.12 out the door ASAP (ideally this week) and punting some of the features that aren't ready to ship into a concurrently released v0.13-beta. As soon as I'm done with that (or maybe even as part of that), I can try to get as much tracing information as possible into the v0.13 beta release. My best guess is that Mutagen is burning through CPU when rescanning the Linux filesystem. Mutagen can't use accelerated scans on Linux (like it can on macOS/Windows) because there's no recursive watching on Linux (other than If you'd like, I can probably spare a few minutes to screen share/video chat about the issue. It'll probably be easier to walk through debugging that way. |
More detailed tracing information is now available from the Mutagen daemon in v0.14 and later. To access this, terminate the Mutagen daemon using
This will print out a lot of information, so you may want to |
Which version of Mutagen are you using (
mutagen version
)?Which operating system (platform/version/architecture) are you using?
OS X
10.14.6
What is the issue that you're experiencing?
Mutagen is constantly re-syncing files, despite no files having changed. This causes very high CPU usage.
I see stuff like this if I keep hitting enter - it's just constantly rescanning and syncing changes. No changes are happening on the actual filesystem, and I've verified this with
fswatch
:What are the steps to reproduce the issue?
No idea. It just started happening. Rebooting the computer and restarting Docker does not help.
Config is very simple:
What is the expected result of these steps in the absence of the issue?
Don't peg the CPU with constant resyncs.
What is the actual result?
CPU is pegged by constantly resyncing.
Is there any other information that might be helpful?
How can I see what files are being synced?
Then maybe I could troubleshoot what the issue is, or see an error message, or something?
Or is there a way to get logs out of Mutagen? So I can see what it's doing?
The text was updated successfully, but these errors were encountered: