hey, a little question about PackMl simulator. in Lens I see that it's functional and is publishing messages to mqtt, but connected to my mqtt server (via external ip) I don't see its messages there. Can anyone point at what I'm missing? thanks UPD: I looks like it's something to do with the hivemq broker and packml sim. it's in a constant loop of connecting-disconnecting. I've tried to run the simulator on my local machine and it works well with

test.mosquitto.org

server but runs into infinite connect-disconnect loop when connected to umh's mqtt server https://cdn.discordapp.com/attachments/984083100520808478/1342121695963517031/image.png?ex=67b87bbb&is=67b72a3b&hm=1c7949c2106de4590b921a6afb66edf5483ec572323e00e05da55728b4fa18ec& https://cdn.discordapp.com/attachments/984083100520808478/1342121696215437355/image.png?ex=67b87bbb&is=67b72a3b&hm=baaaff49a0e7f765c40fad5b4d06fa040169caed28d3b97dde32318385f57c07&

@Athavan kanapuli can you look at this as well?]

Hi @AlexH May be try to run the benthos Protocol converter with verbose logging and the logs would reveal the real problem. Here is the link on how to add the logging component https://docs.redpanda.com/redpanda-connect/components/logger/about/

@Athavan kanapuli I'm currently looking into this issue and think i'm a little closer to finding out the reason. The issue reproduces when the PackML simulator publishes retained messages. In that case the simulator enters infinite connect-disconnect loop. If I change

retain

to false than the simulator starts working as expected. https://github.com/libremfg/PackML-MQTT-Simulator/blob/d8fd030dd551ed59fae46064603d1bd6c39635be/src/index.js#L68 I think it's something to do with HiveMQ retained settings maybe? I'm trying to access broker's debug logs but I lack experience with k8s and struggling here. Maybe you can give me an advice how to set broker's logging level to debug/verbose? Right now it has nothing interesting https://cdn.discordapp.com/attachments/1342121696479543396/1342433651433934901/image.png?ex=67b99e43&is=67b84cc3&hm=8cf78478e079ccbfb3e39857e4b5ea7d7eec848c138df8cfa57c79686eb988e1&

@AlexH very good findings! giving some background here, as @Ferdinand is on vacation today: yes, retained messages are disabled to save memory. otherwise, hivemq would balloon very quickly. We had a similar discussion here: https://discord.com/channels/700613971941785680/984083100520808478/1329806640840441888 Maybe @Athavan kanapuli we need to change the simulator then?

@Jermuk thanks for giving more context. Here's relevant commit. After it the simulator was broken https://github.com/united-manufacturing-hub/united-manufacturing-hub/commit/c8e790b5b7b8b11258e22a963ce87c33619e27f8#diff-896740da297b9fce0f08dee5fc34d24748f70d45e9f3e08637e73dfab1ee64afR167 Maybe it's also worth considering to update broker's logging settings? I'm sure the message about rejecting retained message should have been there. Also are those broker warnings regarding logging settings - ok? https://cdn.discordapp.com/attachments/1342121696479543396/1342439395197980693/image.png?ex=67b9a39d&is=67b8521d&hm=1763642bb7c4e46db14d4352fbdfc01fe7aa83883b4133eedcdc33d033af0e8e&