-
Notifications
You must be signed in to change notification settings - Fork 150
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
Command hangs: mutagen sync terminate xxx #174
Comments
I believe this is the same issue as #71. The issue is that the filesystem scan operations can block. I'm hoping to address this in v0.11.x. If we get accelerated scanning in place for Linux (perhaps via fanotify), that should also help prevent this in the majority of cases, but making scans preemptable is the correct fix. |
This happens on windows host, which is also Alpha, sometimes when there is bad connection to Beta (which is Ubuntu). For example, currently it is hanging and I have no way to end session. I tried to run Is there other way to end session? P.S. I was able to end session by killing mutagen process on Beta (Ubuntu), but only one session. I cannot end the second session. |
State of session is I have two different sessions and I cannot end any of them without reboot. I could end third session though. |
I tried: Then I tried |
Same problem today: no way to terminate session. command hangs:
|
Do you think the problem is with scan? I get this issue everyday now. And sessions have status 'Waiting for changes'. |
Hey @rualark, I may have closed this prematurely. Can you try v0.11.2 and see if you’re still seeing these hangs? I’ve turned on |
Thanks, I'll try |
I removed folders from .mutagen profile folder except daemon/daemon.lock and restarted again. After restart I see that some folders were recreated in .mutagen profile folder. I cannot delete daemon/daemon.lock file, although mutagen.exe process is not listed in running processes or services. How can this be? |
Now I disabled mutagen.exe in Task manager/Startup, restarted and removed everything in .mutagen profile folder. Seems to work now. |
This command seems to help to kill mutagen.exe process, which is not visible in Task manager: Why is mutagen.exe is not visible in Task manager? |
I migrated from Windows 10 to Ubuntu 18.04 approximately at the same time as I migrated to mutagen 0.11.2 I also adapted MutagenMon to run on Ubuntu 18.04 and will push later. |
I'm experiencing a similar behavior with Mutagen v0.11.7 and Docker both v2.3.0.5 (48029) and v2.4.0.0 (48506) in Mac.
In wardenenv/warden#235 people reports that downgrading to Docker v2.3..0.4 fixes the issue. Anyone else experiencing the same issue? (I haven't tried downgrading Docker to v2.3.0.4) |
@havoc-io I can confirm 0.11.8 worked for me on docker 2.4.0.0 on mac 10.15.7. I did first have to remove each hung sync session manually, now everything works as expected. |
@havoc-io I can confirm too that Mutagen v0.11.8 is working well with docker v2.4.0.0, thanks! |
Example:
Sometimes there is even no output for 10-20 seconds and only then "Terminating session" line appears
The text was updated successfully, but these errors were encountered: