-
Notifications
You must be signed in to change notification settings - Fork 14
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
Unable to establish Mycroft Messagebus Connection on Mycroft's side #22
Comments
Hi There is a mycroft-core PR for updating to the latest mycroft-messagebus-client, MycroftAI/mycroft-core#2879 Is this what you was trying? And is the gui connection that's hanging or is it core itself? Also thanks for pointing this out. it seems that PR misses updating the gui bus, will point this out. |
I think it's the GUI that breaks but then that somehow makes everything else hang because Mycroft is completely not responsive. Actually, if I restart Mycroft services I can see the errors from the bus log finally coming through to the GUI before it hangs again. So I guess the bus just freezes everything. |
Mycroft-core will not work with the 0.9.2 version of the messagebus-client until MycroftAI/mycroft-core#2879 is updated and merged. the Dev branch of core will likely work a bit better but the gui will still fail I think. |
I see, is the 0.9.1 the latest supported version? |
yes exactly. The 0.9.2 requires the newer websocket-client and mycroft-core doesn't handle that yet |
The version in mycroft-core has been updated to v0.9.4 so this should work now. Closing the issue, if you still has problems feel free to reopen this issue. |
On a virtual machine running Ubuntu 20.04 (VirtualBox, and also Parallels Desktop), after installing the latest messagebus-client Mycroft hangs on "Establishing Mycroft Messagebus Connection".
I tried installing from source yet nothing seems to fix the issue. Even removing the messagebus module leaves Mycroft hanging unless I do a full reinstall. I also tried opening the socket port in firewall to no avail.
I checked the bus.log and it logs "message bus service started" but then has: 101 GET /core (127.0.0.1)
[Update] I found an error in the enclosure.log:
error from callback : on_message takes 2 positional arguments but 3 were given
also "on_open takes 1 but 2 were given"
The text was updated successfully, but these errors were encountered: