clusters connected to kafbat-ui keeps going offline

[fantastywusheng]

Issue submitter TODO list

• I've looked up my issue in FAQ
• I've searched for an already existing issues here
• I've tried running main-labeled docker image and the issue still persists there
• I'm running a supported version of the application which is listed here

Describe the bug (actual behavior)

The JDK version of my Kafbat-UI is "java version '21.0.6' 2025-01-21 LTS", and the Kafbat version is 4cf17a0 v1.1.0, the JDK version of my kafka broker is jdk11.

The configuration I'm using is as follows named ./api/src/main/resources/application.yml.
auth:
type: DISABLED

management:
endpoint:
info:
enabled: true
health:
enabled: true
endpoints:
web:
exposure:
include: "info,health,prometheus"

dynamic.config.enabled: true

logging:
level:
root: INFO
io.kafbat.ui: DEBUG
reactor.netty.http.server.AccessLog: INFO
org.hibernate.validator: WARN

The command I used to start it is java -Dspring.config.additional-location=./api/src/main/resources/application.yml --add-opens java.rmi/javax.rmi.ssl=ALL-UNNAMED -jar api-v1.1.0.jar

Expected behavior

The log shows that it started normally, and the page can also be opened normally. However, the "configure new cluster" button is grayed out and unavailable. By referring to the documentation, I learned that a cluster can be created through the URL /ui/clusters/create-new-cluster, and I successfully created one. The log already indicates that the collection of relevant cluster metrics has started, but there is still no cluster shown on the page.

Your installation details

java -Dspring.config.additional-location=./api/src/main/resources/application.yml --add-opens java.rmi/javax.rmi.ssl=ALL-UNNAMED -jar api-v1.1.0.jar

Steps to reproduce

none

Screenshots

Logs

DEBUG [boundedElastic-9] i.k.u.s.m.JmxMetricsRetriever: 1263 metrics collected for service:jmx:rmi:///jndi/rmi://192.168.10.117:9793/jmxrmi
2025-03-18 17:17:23,950 DEBUG [boundedElastic-4] i.k.u.s.m.JmxMetricsRetriever: 1263 metrics collected for service:jmx:rmi:///jndi/rmi://192.168.10.117:9793/jmxrmi
2025-03-18 17:17:23,979 DEBUG [boundedElastic-7] i.k.u.s.m.JmxMetricsRetriever: 1263 metrics collected for service:jmx:rmi:///jndi/rmi://192.168.10.117:9793/jmxrmi
2025-03-18 17:17:24,009 DEBUG [boundedElastic-14] i.k.u.s.m.JmxMetricsRetriever: 1263 metrics collected for service:jmx:rmi:///jndi/rmi://192.168.10.117:9793/jmxrmi
2025-03-18 17:17:24,013 DEBUG [boundedElastic-14] i.k.u.s.ClustersStatisticsScheduler: Metrics updated for cluster: local

Additional context

none

[github-actions]

Hi fantastywusheng! 👋

Welcome, and thank you for opening your first issue in the repo!

Please wait for triaging by our maintainers.

As development is carried out in our spare time, you can support us by sponsoring our activities or even funding the development of specific issues.
Sponsorship link

If you plan to raise a PR for this issue, please take a look at our contributing guide.

[germanosin]

Hi @fantastywusheng .

Don't you mind to check what your endpoint '/api/clusters' return?

[fantastywusheng]

Hi @fantastywusheng .

Don't you mind to check what your endpoint '/api/clusters' return?

curl http://192.168.12.133:8080/api/clusters
[]

[germanosin]

What is in the /etc/kafkaui/dynamic_config.yaml ?

[fantastywusheng]

/etc/kafkaui/dynamic_config.yaml

auth:
type: DISABLED
kafka:
clusters:

• bootstrapServers: 192.168.10.116:9013
  kafkaConnect: []
  masking: []
  metrics:
  port: 9793
  type: JMX
  name: local
  properties: {}
  readOnly: false
  serde: []
• bootstrapServers: 192.168.10.116:9013
  kafkaConnect: []
  masking: []
  metrics:
  port: 9992
  type: PROMETHEUS
  name: kafka
  properties: {}
  readOnly: false
  serde: []
  ssl:
  verifySsl: true
• bootstrapServers: 192.168.10.116:9013
  kafkaConnect: []
  masking: []
  metrics:
  port: 9793
  type: JMX
  name: kafka-3.5.1
  properties: {}
  readOnly: false
  serde: []
• bootstrapServers: 192.168.10.116:9013
  kafkaConnect: []
  masking: []
  metrics:
  port: 9992
  type: PROMETHEUS
  name: kafka-kraft
  properties: {}
  readOnly: false
  serde: []
• bootstrapServers: 192.168.12.133:9092
  kafkaConnect: []
  masking: []
  name: kafka-old
  properties: {}
  readOnly: false
  serde: []
  rbac:
  roles:
• clusters:
  • local
    name: memelords
    permissions:
  • actions:
    • ALL
      resource: APPLICATIONCONFIG
  • actions:
    • ALL
      resource: CLUSTERCONFIG
  • actions:
    • ALL
      resource: TOPIC
      value: .*
  • actions:
    • ALL
      resource: CONSUMER
      value: .*
  • actions:
    • ALL
      resource: SCHEMA
      value: .*
  • actions:
    • ALL
      resource: CONNECT
      value: .*
  • actions:
    • ALL
      resource: KSQL
  • actions:
    • ALL
      resource: ACL
  • actions:
    • ALL
      resource: AUDIT
      subjects:
  • provider: OAUTH_GOOGLE
    type: domain
    value: kafbat.dev
  • provider: OAUTH_GOOGLE
    type: user
    value: name@kafbat.dev
  • provider: OAUTH_GITHUB
    type: organization
    value: kafbat
  • provider: OAUTH_GITHUB
    type: user
    value: memelord
  • provider: OAUTH_COGNITO
    type: user
    value: username
  • provider: OAUTH_COGNITO
    type: group
    value: memelords
  • provider: LDAP
    type: group
    value: admin_staff
    webclient: {}

[fantastywusheng]

At first, I suspected that it might be a compatibility issue with the higher version of Kafka. So I set up another Kafka version, specifically kafka_2.11-2.1.1, and used a Kafka node with JDK 1.8. However, it still couldn't be displayed on the page. @germanosin

[fantastywusheng]

There are several warnings in the log, as shown below. However, I don't know how to solve them and I'm not sure if this is where the problem lies.
WARN [kafka-admin-client-thread | kafbat-ui-admin-1742290037-5] o.a.k.c.a.KafkaAdminClient: [AdminClient clientId=kafbat-ui-admin-1742290037-5] The DescribeTopicPartitions API is not supported, using Metadata API to describe topics.
2025-03-18 17:36:46,858 WARN [kafka-admin-client-thread | kafbat-ui-admin-1742290037-2] o.a.k.c.a.KafkaAdminClient: [AdminClient clientId=kafbat-ui-admin-1742290037-2] The DescribeTopicPartitions API is not supported, using Metadata API to describe topics. @germanosin

[germanosin]

What is the version of Kafka you are connecting?

[fantastywusheng]

What is the version of Kafka you are connecting?

There are those of version 3.5.1 using Kraft and those of version 2.1.1 using Zookeeper.