# Timeout on executing kafka-topics

**URL:** <https://forum.confluent.io/t/timeout-on-executing-kafka-topics/37141>\
**Category:** Ops\
**Created:** [7 February 2025 08:55 UTC](https://forum.confluent.io/t/timeout-on-executing-kafka-topics/37141 "2025-02-07T08:55:09Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![mmuehlbeyer](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.confluent.io/mmuehlbeyer/32/1088_2.png) [@mmuehlbeyer](https://forum.confluent.io/u/mmuehlbeyer)\
**Post date:** [7 February 2025 14:34 UTC](https://forum.confluent.io/t/timeout-on-executing-kafka-topics/37141/2 "2025-02-07T14:34:13Z")

</div>

the version command does not connect to the cluster at all

you could try with:  
`kafka-topics --version`

probably the same as in your other one

> [@Metadata version problems on same host/docker image](https://forum.confluent.io/t/metadata-version-problems-on-same-host-docker-image/37137/1):
>
> Hi, as spin-off from my other topic I would like to trry to understand the metadata related errors we see. In the controller log on startup I find [2025-02-03 11:04:44,783] WARN [QuorumController id=3] Performing controller activation. The metadata log appears to be empty. Appending 1 bootstrap record(s) in metadata transaction at metadata.version 3.8-IV0 from bootstrap source ‘the binary bootstrap metadata file: /data/cpkafka-data/bootstrap.checkpoint’. Setting the ZK migration state to NON…

correct broker port chosen?

best,  
michael

---

_[View the full topic](https://forum.confluent.io/t/timeout-on-executing-kafka-topics/37141)._