-
Notifications
You must be signed in to change notification settings - Fork 961
Replies: 1 comment · 5 replies
-
Hey! Could you provide the logs? How soon after connection do you send a message? |
Beta Was this translation helpful? Give feedback.
All reactions
-
Hi @dariusc93 - thanks for getting back. So the logs from the example are quite basic:
I'm sending a message relatively quickly after the two terminals are opened, perhaps just a few seconds. I've continued messing with it, and it seems almost like every other time I run it it works and the other half reports that error. Let me know if there's anything I can log out or try that may be helpful. |
Beta Was this translation helpful? Give feedback.
All reactions
-
Okay I've kept messing with it: If I am running it successfully, close all instances and then re-initialize them all - it will fail. However, if I wait a minute after closing it seems to reliably work. So this leads me to believe that perhaps something is remaining open that is causing issues until it gets cleaned up somehow? |
Beta Was this translation helpful? Give feedback.
All reactions
-
Thanks! To get the logs can you use |
Beta Was this translation helpful? Give feedback.
All reactions
-
Okay here's some logs from attempting to send a message when it failed:
Well we have some errors here at least! It does look like it's failing to connect... There's a I also waited and was able to produce logs when it was working for comparison:
|
Beta Was this translation helpful? Give feedback.
All reactions
-
Hi @dariusc93 - sorry to bother, curious if you have any ideas here or anyone else we may be able to tag? Thanks so much. |
Beta Was this translation helpful? Give feedback.
-
I am working with the chat example locally: https://github.com/libp2p/rust-libp2p/tree/master/examples/chat
In the example, both TCP and QUIC are configured:
And the example works locally with these configurations.
However if I comment out the lines related to QUIC, and so rely only on TCP, I often get
InsufficientPeers
errors when I try to send a message. If I close all connections and wait and reopen, it will sometimes work again. The opposite, relying only on QUIC, reliably works. From research it seems thatInsufficientPeers
can refer to being connected to peers but not having subscribers to the topic, but if that were the issue I'd expect it to fail in all cases (given that part of the code is not changing here).Is this expected? Is there further implementation needed for only TCP for that to be more reliable? Might there be issues around ports remaining opening or something?
Thanks for any help.
Beta Was this translation helpful? Give feedback.
All reactions