# Metricbeat Kafka Module "error in connect: EOF" **URL:** \ **Category:** Beats\ **Tags:** metricbeat\ **Created:** [August 1, 2019, 6:40pm UTC](https://discuss.elastic.co/t/metricbeat-kafka-module-error-in-connect-eof/193392 "2019-08-01T18:40:32Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![broccoli](https://avatars.discourse-cdn.com/v4/letter/b/a183cd/32.png) [@broccoli](https://discuss.elastic.co/u/broccoli)\ **Post date:** [August 1, 2019, 6:40pm UTC](https://discuss.elastic.co/t/metricbeat-kafka-module-error-in-connect-eof/193392/1 "2019-08-01T18:40:32Z")
Using the Metricbeat Kafka module, I get the following errors: ```auto 2019-08-01T20:31:02.479+0200 INFO kafka/log.go:53 Connected to broker at localhost:9093 (unregistered) 2019-08-01T20:31:02.731+0200 INFO kafka/log.go:53 Closed connection to broker localhost:9093 2019-08-01T20:31:02.731+0200 INFO module/wrapper.go:244 Error fetching data for metricset kafka.consumergroup: error in connect: EOF 2019-08-01T20:31:10.539+0200 INFO kafka/log.go:53 Connected to broker at localhost:9093 (unregistered) 2019-08-01T20:31:10.791+0200 INFO kafka/log.go:53 Closed connection to broker localhost:9093 2019-08-01T20:31:10.791+0200 INFO module/wrapper.go:244 Error fetching data for metricset kafka.partition: error in connect: EOF 2019-08-01T20:31:11.971+0200 INFO kafka/log.go:53 Connected to broker at localhost:9093 (unregistered) ``` This keeps on repeating forever, even though Kafka is up and running . I don't see any metrics being forwarded to Elasticsearch, only documents containing the exact same error messages. I use Metricbeat version 7.2 with the following configuration : ```auto - module: kafka metricsets: ["consumergroup", "partition"] period: 10s hosts: ["localhost:9093"] enabled: true ``` Please let me know if you have any idea what might be the reason or how to fix it. ---
**Author:** ![Kaiyan\_Sheng](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kaiyan_sheng/32/38247_2.png) [@Kaiyan\_Sheng](https://discuss.elastic.co/u/Kaiyan_Sheng)\ **Post date:** [August 8, 2019, 3:43am UTC](https://discuss.elastic.co/t/metricbeat-kafka-module-error-in-connect-eof/193392/2 "2019-08-08T03:43:14Z")
Is your Kafka port 9092 or 9093? Maybe try ```auto - module: kafka metricsets: ["consumergroup", "partition"] period: 10s hosts: ["localhost:9092"] enabled: true ``` ---
**Author:** ![Salohy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/salohy/32/52349_2.png) [@Salohy](https://discuss.elastic.co/u/Salohy)\ **Post date:** [August 15, 2019, 7:21am UTC](https://discuss.elastic.co/t/metricbeat-kafka-module-error-in-connect-eof/193392/3 "2019-08-15T07:21:16Z")
Hi @Kaiyan_Sheng I am having the same problem. I do not think it is because of the kafka port, because the error will be `error in connect: No advertised broker with address kafka:9093 found` This is also telling us that the connection is set up, right? `2019-08-01T20:31:02.479+0200 INFO kafka/log.go:53 Connected to broker at localhost:9093 (unregistered)` Please correct me if I am wrong. Currently I am out of idea, how to fix this. Thank you already for your help ---
**Author:** ![Kaiyan\_Sheng](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kaiyan_sheng/32/38247_2.png) [@Kaiyan\_Sheng](https://discuss.elastic.co/u/Kaiyan_Sheng)\ **Post date:** [August 28, 2019, 4:30pm UTC](https://discuss.elastic.co/t/metricbeat-kafka-module-error-in-connect-eof/193392/4 "2019-08-28T16:30:23Z")
Yes you are right, thanks @Salohy! I tried to reproduce it on my side with kafka 2.1.0 and I only see ```auto 2019-08-28T09:08:07.285-0600 INFO kafka/log.go:53 Connected to broker at localhost:9092 (unregistered) 2019-08-28T09:08:07.303-0600 INFO kafka/log.go:53 Closed connection to broker localhost:9092 ``` I can't reproduce the EOF log though. Are you still seeing the same issue? By looking at the metricbeat code, seems like this error happens when trying to connect with a kafka broker or when querying metadata from broker. The error log is not clear enough where it happened exactly, so I will definitely create a PR to improve that. What version of Kafka are you using? On google I see some similar cases for Kafka like [https://github.com/Shopify/sarama/issues/1071](https://github.com/Shopify/sarama/issues/1071), maybe this will help? ---
**Author:** ![evalufran](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/evalufran/32/53286_2.png) [@evalufran](https://discuss.elastic.co/u/evalufran)\ **Post date:** [August 29, 2019, 2:07pm UTC](https://discuss.elastic.co/t/metricbeat-kafka-module-error-in-connect-eof/193392/5 "2019-08-29T14:07:31Z")
I have the same problem without kafka, but system module. The only common case is that I have opened a non standard port to communicate with logstash. Here my specs: metricbeat.yml ``` metricbeat.modules: - module: system metricsets: # - cpu # CPU usage #- load # CPU load averages #- memory # Memory usage #- network # Network IO - process # Per process metrics - process_summary # Process summary # - uptime # System Uptime # - socket_summary # Socket summary #- core # Per CPU core usage #- diskio # Disk IO #- filesystem # File system usage for each mountpoint #- fsstat # File system summary metrics #- raid # Raid #- socket # Sockets and connection info (linux only) enabled: true period: 10s processes: ['.*'] # Configure the metric types that are included by these metricsets. cpu.metrics: ["percentages"] # The other available options are normalized_percentages and ticks. core.metrics: ["percentages"] # The other available option is ticks. # A list of filesystem types to ignore. The filesystem metricset will not # collect data from filesystems matching any of the specified types, and # fsstats will not include data from these filesystems in its summary stats. # If not set, types associated to virtual filesystems are automatically # added when this information is available in the system (e.g. the list of # `nodev` types in `/proc/filesystem`). #filesystem.ignore_types: [] # These options allow you to filter out all processes that are not # in the top N by CPU or memory, in order to reduce the number of documents created. # If both the `by_cpu` and `by_memory` options are used, the union of the two sets # is included. #process.include_top_n: # Set to false to disable this feature and include all processes #enabled: true # How many processes to include from the top by CPU. The processes are sorted # by the `system.process.cpu.total.pct` field. #by_cpu: 0 # How many processes to include from the top by memory. The processes are sorted # by the `system.process.memory.rss.bytes` field. #by_memory: 0 # If false, cmdline of a process is not cached. #process.cmdline.cache.enabled: true # Enable collection of cgroup metrics from processes on Linux. process.cgroups.enabled: true # A list of regular expressions used to whitelist environment variables # reported with the process metricset's events. Defaults to empty. #process.env.whitelist: [] # Include the cumulative CPU tick values with the process metrics. Defaults # to false. #process.include_cpu_ticks: false # Raid mount point to monitor #raid.mount_point: '/' # Configure reverse DNS lookup on remote IP addresses in the socket metricset. #socket.reverse_lookup.enabled: false #socket.reverse_lookup.success_ttl: 60s #socket.reverse_lookup.failure_ttl: 60s # Diskio configurations #diskio.include_devices: [] setup.dashboards.enabled: true output.logstash: hosts: ['localhost:5044'] ssl.certificate_authorities: - ./cert/MyRootCA.pem ssl.certificate: "./cert/metricbeat.pem" ssl.key: "./cert/metricbeat-key.pem" ``` ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [September 26, 2019, 4:07pm UTC](https://discuss.elastic.co/t/metricbeat-kafka-module-error-in-connect-eof/193392/6 "2019-09-26T16:07:34Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.