Replies: 1 comment · 3 replies
-
You have 3 connections in over 2 hours. Not sure that counts as frequent. Brokern-pipe can mean anything from network issues to some ZooKeeper restarts. But that is not clear from only a single small log file snippet. PS: The TLS sidecar is not used by the Kafka containers for a very long time. So you should probably upgrade to osme newer Strimzi version. |
Beta Was this translation helpful? Give feedback.
All reactions
-
Please find the below log, if you can find anything [root@d2lg507612 ~]# kubectl logs -c tls-sidecar dev-demosight-kafka-7 2022.06.27 11:16:22 LOG5[1:140292044568640]: stunnel 4.56 on x86_64-redhat-linux-gnu platform |
Beta Was this translation helpful? Give feedback.
All reactions
-
That is still only one log. You need to correlate it with your Kafka logs and ZooKeeper logs which are the applications connecting through the sidecar. And as I said, this could be related even to your networking ot other things in your environment. In any case - as I said - the simplest solution is to upgrade to a newer version which does not use the sidecars in Kafka anymore. |
Beta Was this translation helpful? Give feedback.
All reactions
-
Thanks |
Beta Was this translation helpful? Give feedback.
All reactions
This discussion was converted from issue #6992 on June 28, 2022 08:04.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi Folks,
We are seeing below ssl erros so frequently on kafka tls-sidecar containers, sometimes tls-sidecar able to connect imeediately, but sometimes, it's wait for more than hours to establish connectivity
2022.06.28 04:40:41 LOG5[1:140292044564224]: Service [zookeeper-2181] accepted connection from 127.0.0.1:38180
2022.06.28 04:40:41 LOG5[1:140292044564224]: connect_blocking: connected 10.233.31.67:2181
2022.06.28 04:40:41 LOG5[1:140292044564224]: Service [zookeeper-2181] connected remote server from 10.233.111.27:46120
2022.06.28 04:40:41 LOG5[1:140292044564224]: Certificate accepted: depth=1, /O=io.strimzi/CN=cluster-ca v0
2022.06.28 04:40:41 LOG5[1:140292044564224]: Certificate accepted: depth=0, /O=io.strimzi/CN=dev-demosight-zookeeper
2022.06.28 05:23:30 LOG5[1:140292044564224]: Read socket error: Broken pipe (32)
2022.06.28 05:23:30 LOG5[1:140292044564224]: Connection reset: 699821 byte(s) sent to SSL, 972472 byte(s) sent to socket
2022.06.28 05:23:31 LOG5[1:140292044564224]: Service [zookeeper-2181] accepted connection from 127.0.0.1:46024
2022.06.28 05:23:31 LOG5[1:140292044564224]: connect_blocking: connected 10.233.31.67:2181
2022.06.28 05:23:31 LOG5[1:140292044564224]: Service [zookeeper-2181] connected remote server from 10.233.111.27:53968
2022.06.28 05:23:32 LOG5[1:140292044564224]: Certificate accepted: depth=1, /O=io.strimzi/CN=cluster-ca v0
2022.06.28 05:23:32 LOG5[1:140292044564224]: Certificate accepted: depth=0, /O=io.strimzi/CN=dev-demosight-zookeeper
2022.06.28 06:55:30 LOG5[1:140292044494592]: Service [zookeeper-2181] accepted connection from 127.0.0.1:34510
2022.06.28 06:55:30 LOG5[1:140292044494592]: connect_blocking: connected 10.233.31.67:2181
2022.06.28 06:55:30 LOG5[1:140292044494592]: Service [zookeeper-2181] connected remote server from 10.233.111.27:42454
2022.06.28 06:55:30 LOG5[1:140292044494592]: Certificate accepted: depth=1, /O=io.strimzi/CN=cluster-ca v0
2022.06.28 06:55:30 LOG5[1:140292044494592]: Certificate accepted: depth=0, /O=io.strimzi/CN=dev-demosight-zookeeper
2022.06.28 06:55:31 LOG5[1:140292044564224]: Read socket error: Broken pipe (32)
2022.06.28 06:55:31 LOG5[1:140292044564224]: Connection reset: 1226429 byte(s) sent to SSL, 1689796 byte(s) sent to socket
Beta Was this translation helpful? Give feedback.
All reactions