# Metadata version problems on same host/docker image **URL:** \ **Category:** Ops\ **Created:** [7 February 2025 07:42 UTC](https://forum.confluent.io/t/metadata-version-problems-on-same-host-docker-image/37137 "2025-02-07T07:42:10Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Rand](https://avatars.discourse-cdn.com/v4/letter/r/ebca7d/32.png) [@Rand](https://forum.confluent.io/u/Rand)\ **Post date:** [7 February 2025 07:42 UTC](https://forum.confluent.io/t/metadata-version-problems-on-same-host-docker-image/37137/1 "2025-02-07T07:42:10Z")
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 NONE since this is a de-novo KRaft cluster. (org.apache.kafka.controller.QuorumController) > [2025-02-03 11:05:12,157] WARN [QuorumController id=3] Broker 4 registered with feature metadata.version that is unknown to the controller (org.apache.kafka.controller.ClusterControlManager) > [2025-02-05 06:46:54,394] WARN [QuorumController id=3] Broker 6 registered with feature metadata.version that is unknown to the controller (org.apache.kafka.controller.ClusterControlManager) > [2025-02-05 11:22:07,155] WARN [QuorumController id=3] Broker 4 registered with feature metadata.version that is unknown to the controller (org.apache.kafka.controller.ClusterControlManager) Which I kind of ignored up until now since its a warning only. However, when trying to run a list topics command, it does not work since “the Broker does not support the metadata api”: ```auto ./kafka-topics --bootstrap-server localhost:9094 --list [2025-02-07 07:26:26,997] WARN [AdminClient clientId=adminclient-1] The remote node is not a BROKER that supports the METADATA api. (org.apache.kafka.clients.admin.internals.AdminMetadataManager) org.apache.kafka.common.errors.UnsupportedVersionException: The node does not support METADATA [2025-02-07 07:26:26,998] WARN [AdminClient clientId=adminclient-1] The remote node is not a BROKER that supports the METADATA api. (org.apache.kafka.clients.admin.internals.AdminMetadataManager) org.apache.kafka.common.errors.UnsupportedVersionException: The node does not support METADATA Error while executing topic command : The node does not support METADATA [2025-02-07 07:26:26,999] WARN [AdminClient clientId=adminclient-1] The remote node is not a BROKER that supports the METADATA api. (org.apache.kafka.clients.admin.internals.AdminMetadataManager) org.apache.kafka.common.errors.UnsupportedVersionException: The node does not support METADATA [2025-02-07 07:26:26,999] WARN [AdminClient clientId=adminclient-1] The remote node is not a BROKER that supports the METADATA api. (org.apache.kafka.clients.admin.internals.AdminMetadataManager) org.apache.kafka.common.errors.UnsupportedVersionException: The node does not support METADATA [2025-02-07 07:26:26,999] ERROR org.apache.kafka.common.errors.UnsupportedVersionException: The node does not support METADATA (org.apache.kafka.tools.TopicCommand) ``` Now the controller and broker are on the same physical host, they use the same docker image - how could one support a metadata version that the other does not? Or maybe this error message is not accurate and its trying to tell me that Metadata is not (configured, available)? Thanks 🙂 ---
**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 08:22 UTC](https://forum.confluent.io/t/metadata-version-problems-on-same-host-docker-image/37137/2 "2025-02-07T08:22:36Z")
hey @Rand mmh just to be sure: 9094 is your broker port? best, michael ---
**Author:** ![Rand](https://avatars.discourse-cdn.com/v4/letter/r/ebca7d/32.png) [@Rand](https://forum.confluent.io/u/Rand)\ **Post date:** [7 February 2025 08:25 UTC](https://forum.confluent.io/t/metadata-version-problems-on-same-host-docker-image/37137/3 "2025-02-07T08:25:15Z")
Its the plaintext listener port for the controller (which is how i understood I should connect to the cluster) ---
**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 08:25 UTC](https://forum.confluent.io/t/metadata-version-problems-on-same-host-docker-image/37137/4 "2025-02-07T08:25:58Z")
to use kafka-topics you should connect to the broker not to the listener ---
**Author:** ![Rand](https://avatars.discourse-cdn.com/v4/letter/r/ebca7d/32.png) [@Rand](https://forum.confluent.io/u/Rand)\ **Post date:** [7 February 2025 08:40 UTC](https://forum.confluent.io/t/metadata-version-problems-on-same-host-docker-image/37137/5 "2025-02-07T08:40:16Z")
I see - that explains Dave’s confusion 😛 I’ll give it a try - the metadata warning on controller startup is independent of this though, that happens all the time even with my SSL only setup - any idea what that is about?