You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
we are using the MQTT Sink Connector als MSK Connect and getting the following error in the log File:
Encountered error [Client is not connected] (com.datamountaineer.streamreactor.connect.mqtt.sink.MqttWriter:61) event if the Sink Connector is working properly by writing data from MSK to the MQTT.
We are seeing also som other Error in the log File which has to do with " Not authorized to access the group" and also warning which says Exceptions loading credentials: retry attempts: 0
The Konfiguration for the msk connect looks like as follows:
connector.class=com.datamountaineer.streamreactor.connect.mqtt.sink.MqttSinkConnector
connect.mqtt.clean=false
connect.mqtt.username=useer
tasks.max=10
topics=kafka-topic
connect.mqtt.service.quality=2
connect.progress.enabled=true
connect.mqtt.hosts=wss://xx:1910
connect.mqtt.converter.throw.on.error=false
name=xyxyxyxy
connect.mqtt.kcql=INSERT INTO mqqtTopic SELECT * FROM kafka-topic
connect.mqtt.password=pw
connect.mqtt.client.id=xyxy_xyxy
The version of KAfka used is 3.5.1 and plugin version: lenses-5.0.1-0.2.0
In addition to this we are seeing that in the log file that all the max number of Tasks are started.
Thanks for any help.
The text was updated successfully, but these errors were encountered:
Thank you for reaching out regarding the issue you’ve encountered with the MQTT Sink Connector.
The error message “Client is not connected” typically indicates a disconnect between the MQTT client and the broker. Additionally, the error “Not authorized to access the group” suggests there may be issues with authorization settings or permissions within your setup.
Given the nature of these errors, it’s possible that there could be a discrepancy between the configurations of the nodes within your MQTT broker cluster. In a clustered environment, ensuring uniform configuration across all nodes is crucial for seamless operation.
To troubleshoot these issues effectively, we recommend thoroughly reviewing the configuration settings for each node of the MQTT Sink Connector and the MSK Connect. Specifically, please double-check authentication, authorization, and networking settings to ensure consistency across all nodes.
If you need further assistance in identifying and resolving these discrepancies, we offer premium support services for our paying customers. Our dedicated support team can provide personalised assistance to address your specific needs and ensure the smooth operation of your systems.
For more information on our premium support services and to explore options for dedicated assistance, please feel free to reach out to our sales team. We prioritise the needs of our paying customers and are here to support you every step of the way.
we are using the MQTT Sink Connector als MSK Connect and getting the following error in the log File:
Encountered error [Client is not connected] (com.datamountaineer.streamreactor.connect.mqtt.sink.MqttWriter:61) event if the Sink Connector is working properly by writing data from MSK to the MQTT.
We are seeing also som other Error in the log File which has to do with " Not authorized to access the group" and also warning which says Exceptions loading credentials: retry attempts: 0
The Konfiguration for the msk connect looks like as follows:
connector.class=com.datamountaineer.streamreactor.connect.mqtt.sink.MqttSinkConnector
connect.mqtt.clean=false
connect.mqtt.username=useer
tasks.max=10
topics=kafka-topic
connect.mqtt.service.quality=2
connect.progress.enabled=true
connect.mqtt.hosts=wss://xx:1910
connect.mqtt.converter.throw.on.error=false
name=xyxyxyxy
connect.mqtt.kcql=INSERT INTO mqqtTopic SELECT * FROM kafka-topic
connect.mqtt.password=pw
connect.mqtt.client.id=xyxy_xyxy
The version of KAfka used is 3.5.1 and plugin version: lenses-5.0.1-0.2.0
In addition to this we are seeing that in the log file that all the max number of Tasks are started.
Thanks for any help.
The text was updated successfully, but these errors were encountered: