zmstone
zmstone
released in `3.16.5`
Hi @SukhikhN The challenge might be, if Kafka is not available, there is no way to know the number of partitions etc. So it cannot start the producers. The commit...
any merge plan ?
closed as it's fixed already
Found this fix (in the links @Rotario shared above): https://github.com/erlang/otp/pull/1870 but merged long ago, EMQX 5.4.1 should have the fix in place. maybe there are other call paths not covered.
Hi again @Rotario "Cannot get connection id" has happened before in ipv4 network too, but I never managed to find the cause. If you are open to run some debug...
Hi @Rotario Here is the beam file in a zipped dir: [net_kernel.zip](https://github.com/emqx/emqx/files/14336014/net_kernel.zip) Sha256sum of the beam file (not the zip): `44551fcb70c1d58a9e2ab8430a968d65de37552e1e5d7012dcf0cf6ddbefba0a` Code diff: https://github.com/zmstone/otp/commit/41dcd061758b8a7b148b997e659b1e3cd558a202 Extract the file `net_kernel.beam`, and mount...
Thank you @Rotario. The log narrowed it down a bit. Now we know that it's logged when accepting a new connection from Erlang distribution listener. We might need to trace/debug...
Some more information for you to troubleshoot the network: EMQX node resolves the peer's port from node name, in your case, both nodes should be listening on port `4370`. (For...
For reference. This is what happens if I self-connect with a different name: ``` v5.4.1([email protected])1> net_kernel:connect_node(node()). % self node is `[email protected]` so it should always return `true` -- as expected....