-
Notifications
You must be signed in to change notification settings - Fork 6
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
User Story issue #183
Comments
I'm from Germany, and I set up all my accounts there. Now I'm in US, last week it worked without any problems on my local machine when I was connected to eduroam. Today it started crashing, and just now I tried connecting to Germany via VPN and running it. It works. |
Can you test whether the network(s) you're using have anyone blocking outgoing connections on the Kafka default port (9092), as this is disappointingly common? For example, you can test with a command like
which should print |
Hi yes, indeed this returns |
Unfortunately, this is the type of thing that network admins change, sometimes in response to observing traffic. It may be possible to contact them and explain that there is a science use for having the port open. |
I was able to connect as long as I was using a VPN, however, today that also started rejecting my connection. %4|1659476487.055|TERMINATE|rdkafka#producer-1| [thrd:app]: Producer terminating with 1 message (293 bytes) still in
queue or transit: use flush() to wait for outstanding message delivery Then it raises I upgraded my |
Also, my collagues started getting same / similar errors today |
Here is my colleague's error SNEWS2/SNEWS_Publishing_Tools#48 (comment) |
Description
The hop version 0.5.0 started to raise Network errors for me since this morning. Here is an example;
[description and details]
Definition of Done
I tried creating new credentials, I also tried using 3 different networks (which I was using in the past and it was working) including eduroam. Everything seems to be working, I seem to have a network connection. I do not understand why it started to crash
The text was updated successfully, but these errors were encountered: