Skip to content
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

Group CHAT not found #141

Open
BananaNosh opened this issue Aug 10, 2019 · 17 comments
Open

Group CHAT not found #141

BananaNosh opened this issue Aug 10, 2019 · 17 comments

Comments

@BananaNosh
Copy link

Hey,
I started the example chat application as written in the README.
However, I always get the error message "Group CHAT not found" when sending a message, though the group should have been created and joined.

@sphaero
Copy link
Contributor

sphaero commented Aug 13, 2019

Works fine here:

using Python native module No module named 'zyre_pyzmq'
<pyre.zsocket.ZSocket object at 0x7f47f18d0730>
<pyre.zsocket.ZSocket object at 0x7f47f18d0730>
<pyre.zsocket.ZSocket object at 0x7f47f18d0730> {<pyre.zsocket.ZSocket object at 0x7f47f18d0730>: 1}
HMMM
HMMM [b'ENTER', b'\x0c}!\xe8\xc5\x08G\x7f\x9e \xe4e\xdb\xdb\xcc\xc5', b'CHAT', b'{"CHAT_Header1":"example header1","CHAT_Header2":"example header2"}', b'tcp://10.2.4.190:34645']
NODE_MSG TYPE: b'ENTER'
NODE_MSG PEER: 0c7d21e8-c508-477f-9e20-e465dbdbccc5
NODE_MSG NAME: b'CHAT'
NODE_MSG HEADERS: {'CHAT_Header1': 'example header1', 'CHAT_Header2': 'example header2'}
key = CHAT_Header1, value = example header1
key = CHAT_Header2, value = example header2
NODE_MSG CONT: [b'tcp://10.2.4.190:34645']
<pyre.zsocket.ZSocket object at 0x7f47f18d0730> {<pyre.zsocket.ZSocket object at 0x7f47f18d0730>: 1}
HMMM
HMMM [b'JOIN', b'\x0c}!\xe8\xc5\x08G\x7f\x9e \xe4e\xdb\xdb\xcc\xc5', b'CHAT', b'CHAT']
NODE_MSG TYPE: b'JOIN'
NODE_MSG PEER: 0c7d21e8-c508-477f-9e20-e465dbdbccc5
NODE_MSG NAME: b'CHAT'
NODE_MSG CONT: [b'CHAT']
hoi
<pyre.zsocket.ZSocket object at 0x7f47f18d0730> {<zmq.sugar.socket.Socket object at 0x7f47f22003f0>: 1}
CHAT_TASK: b'hoi'
using Python native module No module named 'zyre_pyzmq'
<pyre.zsocket.ZSocket object at 0x7fb1a6aea118>
<pyre.zsocket.ZSocket object at 0x7fb1a6aea118>
<pyre.zsocket.ZSocket object at 0x7fb1a6aea118> {<pyre.zsocket.ZSocket object at 0x7fb1a6aea118>: 1}
HMMM
HMMM [b'ENTER', b'/\xcbv\xa7\x8b\xe6F\xcb\xa8\x8c\xad\xd5\x82\xff\xa50', b'CHAT', b'{"CHAT_Header1":"example header1","CHAT_Header2":"example header2"}', b'tcp://10.2.4.190:46217']
NODE_MSG TYPE: b'ENTER'
NODE_MSG PEER: 2fcb76a7-8be6-46cb-a88c-add582ffa530
NODE_MSG NAME: b'CHAT'
NODE_MSG HEADERS: {'CHAT_Header1': 'example header1', 'CHAT_Header2': 'example header2'}
key = CHAT_Header1, value = example header1
key = CHAT_Header2, value = example header2
NODE_MSG CONT: [b'tcp://10.2.4.190:46217']
<pyre.zsocket.ZSocket object at 0x7fb1a6aea118> {<pyre.zsocket.ZSocket object at 0x7fb1a6aea118>: 1}
HMMM
HMMM [b'JOIN', b'/\xcbv\xa7\x8b\xe6F\xcb\xa8\x8c\xad\xd5\x82\xff\xa50', b'CHAT', b'CHAT']
NODE_MSG TYPE: b'JOIN'
NODE_MSG PEER: 2fcb76a7-8be6-46cb-a88c-add582ffa530
NODE_MSG NAME: b'CHAT'
NODE_MSG CONT: [b'CHAT']
<pyre.zsocket.ZSocket object at 0x7fb1a6aea118> {<pyre.zsocket.ZSocket object at 0x7fb1a6aea118>: 1}
HMMM
HMMM [b'SHOUT', b'/\xcbv\xa7\x8b\xe6F\xcb\xa8\x8c\xad\xd5\x82\xff\xa50', b'CHAT', b'CHAT', b'hoi']
NODE_MSG TYPE: b'SHOUT'
NODE_MSG PEER: 2fcb76a7-8be6-46cb-a88c-add582ffa530
NODE_MSG NAME: b'CHAT'
NODE_MSG GROUP: b'CHAT'
NODE_MSG CONT: [b'hoi']

@BananaNosh
Copy link
Author

BananaNosh commented Aug 13, 2019 via email

@sphaero
Copy link
Contributor

sphaero commented Aug 13, 2019

no idea, did you start 2 nodes before chatting? what platform are you on? you should see enter events if they see each other.

@BananaNosh
Copy link
Author

BananaNosh commented Aug 13, 2019 via email

@BananaNosh
Copy link
Author

BananaNosh commented Aug 13, 2019 via email

@sphaero
Copy link
Contributor

sphaero commented Aug 13, 2019

is this on physical machines or on virtual ones? If they don't see each other is must be something network related. Are you sure you can do broadcasts on these devices? It's hard to guess what's going on on your machines.

You could try the zyre library instead._

@BananaNosh
Copy link
Author

They are physical machines.
Thanks for your help so far. I will check if I can find out if there is something a problem within my network.

@BananaNosh
Copy link
Author

But for using zyre I would have to use C, right?

@sphaero
Copy link
Contributor

sphaero commented Aug 13, 2019

Yes, but it has bindings to python: https://github.com/zeromq/zyre/tree/master/bindings/python

@BananaNosh
Copy link
Author

BananaNosh commented Sep 6, 2019 via email

@sphaero
Copy link
Contributor

sphaero commented Sep 7, 2019

I was using the latest from the master branch. What was the output of the zyre bindings?

@tlowrimore
Copy link

I'm experiencing the same issue with Pyre. I'm starting two nodes on the same machine, but when I send a message to the group, I receive the "Group CHAT not found". I'm running on Pop_OS 19.04 / Python 3.7.

Cheers!

@sphaero
Copy link
Contributor

sphaero commented Sep 24, 2019

can you post your output of both nodes?

@tlowrimore
Copy link

@sphaero Thanks for the quick response. I'm just getting the initial logging output. No indication of discovery. That said, I have to abandon the use of this library due to the use of the LGPL licence.

@sphaero
Copy link
Contributor

sphaero commented Sep 25, 2019

So it means discovery is failing on your platform. Discovery is done through UDP broadcast. You should see udp broadcast packets on your network interface using tcpdump.
For example

tcpdump -i all -n port 5670

@tlowrimore
Copy link

@sphaero Well, I feel silly. Turns out, I have very a restrictive set of UFW rules. As such, the initial UDP broadcast is blocked. Adding a rule that allows this to pass solves my issue. Thank you for your help!

@BananaNosh
Copy link
Author

BananaNosh commented Sep 26, 2019 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants