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
zerconf randomly stops working #1543
Comments
Related to #1424. |
After running some updates (on Ubuntu 14.04 LTS with Mopidy installed from the Mopidy apt repository) I hit the same issue. For me, the HTTP frontend times out completely. The MPD interface stays usable. I'd be glad to assist in gathering debugging info or trying out solutions. |
@sorvakko do you see the same traceback? Are you saying the http frontend doesn't work even in a browser or just the Mopidy-mobile app doesn't work? Also please provide |
The HTTP frontend doesn't work at all, even in a browser. The connection just times out (even though
mopidy deps:
|
Did some monkey debugging (read the signature in the stacktrace and noted there's a Any debug logging I could / should enable? |
I can now confirm that the web frontend not being visible was due to an unrelated issue (had some really screwy problem with the loopback interface of my host, affecting many other things beside Mopidy). The stacktrace issue still stands (and was fixed by setting self.name = "test" in zeroconf.py). |
I've been running mopidy version 2.0.0 on NixOS for a few days and experience these errors that I believe is the reason for zeroconf to stop working[1]:
The MPD part of mopidy still works though. I haven't figured out what triggers this issue, it seemingly happens "at random".
[1]:
avahi-browse -at | grep mopidy
no longer yields a result, "Mopidy Mobile" Android app doesn't find any servers.UPDATE: Fixed a clipped line from the log.
The text was updated successfully, but these errors were encountered: